A company has a workload that runs on several Amazon EC2 instances. The company must retain the workload's system logs and application logs for 13 months. The logs must be available for the entire…

Question

Options

• ACreate an Amazon S3 bucket. Apply a bucket policy to expire objects after 13 months.
• BCreate a log group in Amazon CloudWatch Logs. Specify an Expire Events After value of 13
• CCreate an Amazon S3 bucket. Apply a bucket policy to expire objects after 13 months. Deploy the
• DCreate a log group in Amazon CloudWatch Logs. Specify an Expire Events After value of 13

• A
  3% (1)
• B
  88% (35)
• C
  3% (1)
• D
  8% (3)

Explanation

Option B is correct because Amazon CloudWatch Logs decouples log storage from the EC2 instance lifecycle - logs are streamed off the instance in real time via the CloudWatch agent, so terminating an EC2 instance does not cause any log loss. Setting the log group retention to 13 months satisfies the availability requirement exactly.

Options A and C describe Amazon S3 with a 13-month expiration policy, which handles retention correctly but S3 alone does not automatically collect logs from EC2 instances - without an agent or mechanism to ship logs off the instance, logs stored locally on the EC2 filesystem are lost on termination. Option D appears identical to B in the truncated choices shown, but in the original exam it likely describes a CloudWatch Logs setup with an incorrect retention value (e.g., fewer months) or missing the agent configuration, making it non-compliant.

Memory tip: Think "logs must survive the instance" - whenever a question mentions EC2 instance termination + log preservation, your reflex should be CloudWatch Logs + agent (or S3 + agent). The agent is the critical piece that makes logs durable; retention settings alone don't matter if the logs never leave the instance.

No community discussion yet for this question.