A cloud administrator is configuring logging for a new financial application. According to industry regulations, all transaction logs must be preserved for seven years for auditing purposes and then permanently deleted to minimize data exposure. Which logging configuration will BEST satisfy this requirement?
Holding logs in memory for manual export whenever an administrator decides
Defining a location that refreshes logs periodically for optimization
Applying a schedule that keeps logs for a specific duration and then removes them
Forwarding all logs to an external service for processing and discarding local copies
Applying a scheduled retention policy is the correct method to ensure logs are kept for a specific duration (like the required seven years) and then automatically deleted to comply with regulations. Refreshing logs periodically for optimization would likely delete them too early, failing the seven-year requirement. Forwarding logs to an external service only moves the data; it does not in itself define or guarantee a specific retention period. Relying on manual exports from volatile memory is completely inadequate for long-term compliance and is highly prone to data loss.
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.
Why is applying a schedule better for preserving logs than refreshing them periodically?
Open an interactive chat with Bash
How does forwarding logs to an external service fall short in meeting log retention policies?
Open an interactive chat with Bash
What risks are involved in holding logs in memory for manual export?