SAA-C03 · Question #614
A company uses AWS Systems Manager for routine management and patching of Amazon EC2 instances. The EC2 instances are in an IP address type target group behind an Application Load Balancer (ALB)…
The correct answer is C. Implement the AWSEC2-PatchLoadBalanacerInstance Systems Manager Automation document D. Use Systems Manager Maintenance Windows to automatically remove the instances from service. To resolve errors when removing EC2 instances from an ALB target group during patching using Systems Manager, the AWSEC2-PatchLoadBalancerInstance Automation document should be implemented within Systems Manager Maintenance Windows.
Question
A company uses AWS Systems Manager for routine management and patching of Amazon EC2 instances. The EC2 instances are in an IP address type target group behind an Application Load Balancer (ALB). New security protocols require the company to remove EC2 instances from service during a patch. When the company attempts to follow the security protocol during the next patch, the company receives errors during the patching window. Which combination of solutions will resolve the errors? (Choose two.)
Options
- AChange the target type of the target group from IP address type to instance type.
- BContinue to use the existing Systems Manager document without changes because it is already
- CImplement the AWSEC2-PatchLoadBalanacerInstance Systems Manager Automation document
- DUse Systems Manager Maintenance Windows to automatically remove the instances from service
- EConfigure Systems Manager State Manager to remove the instances from service and manage
How the community answered
(53 responses)- A26% (14)
- B11% (6)
- C57% (30)
- E6% (3)
Why each option
To resolve errors when removing EC2 instances from an ALB target group during patching using Systems Manager, the `AWSEC2-PatchLoadBalancerInstance` Automation document should be implemented within Systems Manager Maintenance Windows.
Changing the target type from IP address to instance type *might* be a prerequisite for some automation but is not the primary mechanism for gracefully managing instances in and out of a load balancer during patching; dedicated automation documents and maintenance windows serve this purpose.
Continuing to use the existing Systems Manager document that is causing errors will not resolve the problem.
The `AWSEC2-PatchLoadBalancerInstance` Systems Manager Automation document is specifically designed to safely remove an EC2 instance from a load balancer, perform maintenance (like patching), and then re-add it, directly addressing the requirement and resolving patching errors.
Systems Manager Maintenance Windows allow defining a recurring schedule for performing potentially disruptive operations like patching. By integrating the patching automation within a Maintenance Window, the process of removing instances from the load balancer can be scheduled and executed automatically and safely.
Systems Manager State Manager applies configuration to instances but does not provide the specific automation capabilities to gracefully remove instances from a load balancer, patch them, and then re-add them; that functionality is handled by Automation documents.
Concept tested: AWS Systems Manager Automation, Maintenance Windows, patching EC2 instances behind load balancers
Source: https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-patch-elb.html
Community Discussion
No community discussion yet for this question.