Exam AWS Certified SysOps Administrator - Associate topic 1 question 316 discussion

I don't know if S3 option works, but I do know AWS documents using Parameter Store to store a CloudWatch agent configuration file, and to start the agent using the config stored in Parameter Store, therefore I know C & D are valid. Here are references: "Uploading the CloudWatch agent configuration file to Systems Manager Parameter Store" https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-Configuration-File-Details.html Command to start CloudWatch agent by loading configuration file previously saved in Systems Manager Parameter store: sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -s -c ssm:configuration-parameter-store-name https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/install-CloudWatch-Agent-on-EC2-Instance-fleet.html

Why Option A is Correct: Storing the CloudWatch agent configuration file in Amazon S3 makes it easily accessible to the EC2 instances. The S3 bucket acts as a centralized storage location for the predefined configuration file, ensuring all instances use the same version when updating their agent settings. Why Option E is Correct: Using AWS Systems Manager State Manager associations allows the administrator to ensure that every tagged instance consistently applies the same CloudWatch configuration. The AmazonCloudWatch-ManageAgent Run Command document can pull the agent configuration file from the S3 bucket and apply it across all targeted instances. Targeting based on tags (e.g., OS: Windows) ensures that only the Windows EC2 instances are updated.

Assuming there the instances are deployed to different regions, then its better to store the configuration file in S3. Because storing it in Parameter store would require additional steps. "If you use multiple Regions, you must synchronize CloudWatch configuration updates in each Region's Parameter Store. Parameter Store is a Regional service and the same parameter must be updated in each Region that uses the CloudWatch agent." https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/create-store-cloudwatch-configurations.html

A&D Option B and Option C do not directly address the requirement to configure the CloudWatch agent with a consistent predefined configuration across all instances. Option E does not use the S3 bucket as the configuration source, which is typically the recommended way to manage CloudWatch agent configurations for consistency.

CD, used in prod already

https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/create-store-cloudwatch-configurations.html Single account in the scenario. Seems like central storage by way of S3 is not required.

Step A involves storing the CloudWatch agent configuration file in an Amazon S3 bucket. This allows for centralized storage of the configuration file, making it easily accessible. Step D involves creating a Systems Manager State Manager association to run the AmazonCloudWatch-ManageAgent Systems Manager Run Command document. By selecting Systems Manager as an optional configuration source and targeting the instances based on tag values, you can ensure that every instance with the specified tag (in this case, "OS" tag with a value of "Windows") will be reconfigured to use the predefined CloudWatch configuration. These steps ensure that the CloudWatch agent configuration is consistent across all Windows EC2 instances by leveraging Systems Manager and the predefined configuration stored in an S3 bucket. Therefore, the correct choices are A and D.