Amazon Web Services DOP-C02 Exam With Confidence Using Practice Dumps

To archive CloudWatch Logs to S3 with long-term retention, you need:

a streaming mechanism to move data from CloudWatch Logs to S3, and

an S3 Lifecycle policy to handle tiering and expiration.

Option B uses a CloudWatch Logs subscription filter that targets Amazon Data Firehose . Firehose provides managed, scalable streaming from CloudWatch Logs to S3 with optional buffering and transformation. This is the AWS-recommended pattern for exporting continuous log streams with minimal operational overhead. Option C is not valid because CloudWatch Logs subscription filters cannot directly target S3; they must target Kinesis, Firehose, or Lambda.

Once logs are in S3, the company wants to keep them rarely accessed after 90 days and retained for 10 years. Option D configures an S3 lifecycle policy to transition logs to S3 Glacier Instant Retrieval after 90 days, which is a low-cost archival tier with relatively fast access, and to expire (delete) logs after 3,650 days (10 years). This precisely matches the retention requirement.

Option E uses Reduced Redundancy, which is a legacy storage class and not optimized for long-term archival. Therefore, the correct combination is B and D .

The most operationally efficient answer is to use Systems Manager Default Host Management Configuration. This feature is designed specifically to make EC2 instances become Systems Manager managed instances automatically without manually attaching an IAM instance profile to every instance. AWS states that Default Host Management Configuration manages EC2 instances automatically as managed instances and uses a default IAM role for the account and Region. It also requires IMDSv2, which the scenario already satisfies. Option A correctly creates the Systems Manager trusted role, attaches AmazonSSMManagedEC2InstanceDefaultPolicy, and configures the SSM service setting. Options B and D add AWS Config remediation complexity, and C uses Patch Manager incorrectly because SSM Agent is already installed and the requirement is automatic Systems Manager management.

================

Step 1: Using AWS CloudFormation with ECS Blue/Green Deployments

The requirement is to implement an ECS blue/green deployment where traffic is shifted gradually. AWS CodeDeploy supports such blue/green deployments with predefined configurations, like ECSLinear10PercentEvery1Minute, which shifts 10% of traffic every minute.

Action: Use the AWS::CodeDeployBlueGreen transform and the appropriate hooks in the CloudFormation template. The ECSLinear10PercentEvery1Minute deployment configuration meets the requirement of shifting 10% of traffic every minute.

Why: The transform and hook parameters in CloudFormation are essential for configuring the blue/green deployment with the desired traffic-shifting behavior.