A technology startup launches fresh servers for each product rollout and discards them when new updates occur. The team wants any leftover session data to vanish between rollouts to reduce overhead and minimize potential risks. Which environment approach meets these goals best?
A design that centralizes logs but leaves session data in memory across multiple reboots
A model that retains container-level state for quicker rollbacks
A system that retains local data after each product update for user analytics
A non-persistent environment that reverts each server to a new baseline after each update
A non-persistent environment resets each server to a new baseline whenever updates happen. This approach removes temporary data that might remain from previous releases, aligning with the startup’s goal of avoiding residual session information. Choices that preserve data in memory or on local disks do not address the objective of clearing out session data. Keeping container-level state for rollbacks also retains data longer than desired, which undermines the team’s plan to remove overhead and lessen security risks.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a non-persistent environment?
Open an interactive chat with Bash
Why is data persistence a security risk?
Open an interactive chat with Bash
What are other use cases for a non-persistent environment?