SOA-C03 · Question #78
An environment consists of 100 Amazon EC2 Windows instances. The Amazon CloudWatch agent is deployed and running on all EC2 instances with a baseline configuration file to capture log files. There…
The correct answer is A. Create an additional CloudWatch agent configuration filo to capture the DHCP logs. Use the AWS. Explanation Option A is correct because creating a separate, supplemental CloudWatch agent configuration file for the DHCP logs and deploying it via AWS Systems Manager (SSM) Parameter Store or Run Command allows you to target only the 50 affected instances without disrupting…
Question
An environment consists of 100 Amazon EC2 Windows instances. The Amazon CloudWatch agent is deployed and running on all EC2 instances with a baseline configuration file to capture log files. There is a new requirement to capture the DHCP log files that exist on 50 of the instances. What is the MOST operationally efficient way to meet this new requirement?
Options
- ACreate an additional CloudWatch agent configuration filo to capture the DHCP logs. Use the AWS
- BLog in to each EC2 instance with administrator rights. Create a PowerShell script to push the
- CRun the CloudWatch agent configuration file wizard on each EC2 instance. Verify that the
- DRun the CloudWatch agent configuration file wizard on each EC2 instance and select the
How the community answered
(52 responses)- A71% (37)
- B17% (9)
- C4% (2)
- D8% (4)
Explanation
Explanation
Option A is correct because creating a separate, supplemental CloudWatch agent configuration file for the DHCP logs and deploying it via AWS Systems Manager (SSM) Parameter Store or Run Command allows you to target only the 50 affected instances without disrupting the existing baseline configuration - this is the "append" or layered configuration approach that CloudWatch agent natively supports, making it highly scalable and operationally efficient.
Why the distractors are wrong:
- Option B requires manually logging into each of the 50 instances to run a PowerShell script - this is time-consuming, error-prone, and the least operationally efficient approach.
- Option C running the configuration wizard on each EC2 instance individually is a manual, repetitive process that doesn't scale, even if the result is correct.
- Option D is essentially the same problem as C - running the wizard instance-by-instance is operationally inefficient at scale, regardless of what options are selected.
Memory Tip: Think "Layer, Don't Replace" - when you need to add monitoring to a subset of instances, create an additional config file and push it centrally via SSM rather than reconfiguring every machine. Any time an exam question mentions operational efficiency across multiple EC2 instances, SSM-based automation is almost always the right answer.
Topics
Community Discussion
No community discussion yet for this question.