Q52 — AWS SAA-C03 Ch.14

Question 52 of 100 | ← Chapter 14

Q1052. 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.)

• A. Change the target type of the target group from IP address type to instance type.
• B. Continue to use the existing Systems Manager document without changes because it is already optimized to handle instances that are in an IP address type target group behind an ALB.
• C. Implement the AWSEC2-PatchLoadBalanacerInstance Systems Manager Automation document to manage the patching process. ✓
• D. Use Systems Manager Maintenance Windows to automatically remove the instances from service to patch the instances. ✓
• E. Configure Systems Manager State Manager to remove the instances from service and manage the patching schedule. Use ALB health checks to re-route traffic.

Correct Answer: C. Implement the AWSEC2-PatchLoadBalanacerInstance Systems Manager Automation document to manage the patching process., D. Use Systems Manager Maintenance Windows to automatically remove the instances from service to patch the instances.

Explanation

To resolve the errors encountered during the patching window for EC2 instances in an IP address type target group behind an Application Load Balancer (ALB), the best combination of solutions is:C. Implement the AWSEC2-PatchLoadBalancerInstance Systems Manager Automation document to manage the patching process.D. Use Systems Manager Maintenance Windows to automatically remove the instances from service to patch the instances.Explanation:\1. C. Implement the AWSEC2-PatchLoadBalancerInstance Systems Manager Automation document: - This Automation document is specifically designed to manage the patching of instances that are registered with a load balancer. It handles the process of deregistering instances from the target group, applying patches, and then re-registering them, which helps avoid errors during the patching process.\2. D. Use Systems Manager Maintenance Windows: - Maintenance Windows allow you to define a schedule for executing tasks, including removing instances from service before patching. This ensures that instances are taken out of service during the maintenance period, thus preventing any errors related to traffic handling while they are being patched.Evaluation of Other Options:A. Change the target type of the target group from IP address type to instance type: - While changing the target type could resolve some issues, it may not address the core problem of how the patching is managed. The existing configuration might still require a proper patching strategy.B. Continue to use the existing Systems Manager document without changes: - This option is not advisable because the existing document may not be optimized for the specific requirements of instances in an IP address type target group and may lead to errors.E. Configure Systems Manager State Manager to remove the instances from service and manage the patching schedule: - While State Manager could help in managing the patching schedule, it does not provide the same level of automation and integration with the load balancer as the AWSEC2-PatchLoadBalancerInstance document. It might also require additional configuration and management.Conclusion:Options C and D provide a comprehensive and effective strategy for managing the patching process while adhering to the new security protocols, ensuring smooth operations during the maintenance window.