SOA-C03 practice question: Systems Manager for fleet operations (3 of 3)

Deployment, Provisioning, and Automation A free question from our original SOA-C03 practice exam. Try it, then open the answer to see why each option is right or wrong.

A logistics broker needs to run a one-time script that rotates a local log configuration on 500 EC2 instances tagged Role=Tracking. All instances are managed by AWS Systems Manager. To limit the impact of a mistake, the script should run on no more than 10 percent of the instances at a time, and the job should stop if it fails on more than five instances. Which approach should a CloudOps engineer use?

Choose one answer.

A. A State Manager association with the AWS-RunShellScript document that applies the script to the tagged instances every day.
B. Session Manager sessions opened by engineers to each instance in turn, running the script by hand in each shell.
C. Run Command with the AWS-RunShellScript document, targeting the tag, with a concurrency of 10 percent and an error threshold of 5.
D. A user data script added to the instances' launch template, followed by an instance refresh of every Auto Scaling group.

Show the answer and explanation

Answer: C

A. Wrong: State Manager is for keeping a configuration applied on a schedule. Running a one-time script every day is not what the broker needs. Learn more: AWS Systems Manager State Manager (opens in a new tab)
B. Wrong: This would take hundreds of manual sessions and has no automatic stop on errors. Run Command does the same work across the fleet in one operation. Learn more: AWS Systems Manager Session Manager (opens in a new tab)
C. Right: Correct. Run Command can target instances by tag and has built-in rate controls. Concurrency limits how many instances run at once, and the error threshold stops the command after too many failures. Learn more: Run commands at scale (opens in a new tab)
D. Wrong: User data runs at launch, so this replaces every instance just to run one script. It is slow and disruptive compared with Run Command. Learn more: Use an instance refresh to update instances in an Auto Scaling group (opens in a new tab)

Explanation

Run Command is the Systems Manager tool for running ad hoc commands across many managed instances. It targets by tag and offers rate controls, a concurrency limit and an error threshold, so a bad script affects only a small part of the fleet before it stops.

SOA-C03 practice question: Systems Manager for fleet operations (3 of 3)

Explanation

Study

Keep practicing