Examkin

Question

Difficulty: HardDeployment Strategies and Execution

A SysOps administrator needs to deploy a custom application update to a fleet of 2020 Amazon EC2 instances by using AWS Systems Manager Run Command. The administrator wants to execute the deployment in a rolling manner to maintain application availability, ensuring that at least 1515 instances remain online and healthy during the process. Additionally, the deployment must stop immediately if more than 22 instances fail the installation to prevent further errors across the fleet.

Which two configurations should the administrator specify when executing the Run Command? (Select TWO.)

  1. Set the Max Concurrency rate control parameter to 55 or 25%25\%.Answer
  2. Set the Max Errors rate control parameter to 22 or 10%10\%.Answer
  3. C
    Set the Max Concurrency rate control parameter to 1515 or 75%75\%.
  4. D
    Configure a target patch group with the tag key 'PatchGroup' and associate it with a custom patch baseline.
  5. E
    Configure an IAM role with the 'iam:AssumeRole' permission for the Systems Manager service role instead of 'iam:PassRole' permissions.

Answer

To configure the rolling deployment correctly using AWS Systems Manager Run Command, the administrator must set the Max Concurrency rate control parameter to 55 or 25%25\% and the Max Errors rate control parameter to 22 or 10%10\%.
The correct configurations are setting the Max Concurrency rate control parameter to 55 or 25%25\% and the Max Errors rate control parameter to 22 or 10%10\%. Setting Max Concurrency to 55 limits the active deployment target count to 55 instances at any time, leaving 1515 instances (75%75\%) active to serve traffic. Setting Max Errors to 22 halts the execution of the Run Command across the remaining fleet as soon as 22 instances report a failure, minimizing the impact of a faulty deployment.

Step-by-Step Solution

1
Calculate the allowed concurrency for the deployment fleet.
With a total of 2020 instances and a requirement that at least 1515 instances must remain online, the maximum number of instances that can be updated concurrently is 20−15=520 - 15 = 5 instances (which is 25%25\% of the fleet).
This ensures that the update is applied in a rolling manner without violating the minimum capacity requirement.
2
Determine the error threshold to stop the execution.
To stop the deployment immediately if more than 22 instances fail, set the failure limit to 22 instances (which is 10%10\% of the fleet).
Setting this limit prevents the command from being sent to the rest of the fleet once the threshold is met.
3
Apply these values to the Systems Manager Run Command rate control settings.
Specify a Max Concurrency of 55 (or 25%25\%) and Max Errors of 22 (or 10%10\%) in the Run Command configuration.
These parameters directly govern the execution rate and halt behavior of the deployment task.

Key Concept

AWS Systems Manager Run Command rate controls (Max Concurrency and Max Errors) allow SysOps administrators to manage rolling deployments and control fault tolerance across large fleets of instances.
Rate this question

Topics

Deployment Strategies and Execution

More questions from this topic