Q: 13
A company deploys its corporate infrastructure on AWS across multiple AWS Regions and Availability
Zones. The infrastructure is deployed on Amazon EC2 instances and connects with AWS loT
Greengrass devices. The company deploys additional resources on on-premises servers that are
located in the corporate headquarters.
The company wants to reduce the overhead involved in maintaining and updating its resources. The
company's DevOps team plans to use AWS Systems Manager to implement automated management
and application of patches. The DevOps team confirms that Systems Manager is available in the
Regions that the resources are deployed m Systems Manager also is available in a Region near the
corporate headquarters.
Which combination of steps must the DevOps team take to implement automated patch and
configuration management across the company's EC2 instances loT devices and on-premises
infrastructure? (Select THREE.)
Options
Discussion
CEF imo. Systems Manager Patch Manager (C) handles the patching automation itself, but you'll need the proper IAM setup (E) for SSM to access both EC2 and on-prem/IoT devices. F is crucial because hybrid/on-prem and Greengrass need SSM Agent activation codes, otherwise they won't register as managed instances. Tagging (A) isn't required for patching, and EventBridge (D) is more for event-driven responses not normal periodic patch management. Pretty sure that's the combo for multi-platform SSM automation, unless AWS changed something recently.
D imo, but does "automated management" mean periodic scheduling or just triggering patches when needed? That changes which to pick.
C/E/F? That's what I'd pick, fits the SSM patching flow for hybrid infra.
I don’t think it’s D, that feels like a trap-EventBridge isn't really needed for standard patch automation. The right combo is C, E, and F: Patch Manager with maintenance windows for automation (C), proper IAM instance profiles for Systems Manager access (E), and SSM Agent activation for on-prem and IoT Greengrass devices (F). Pretty sure that's what AWS recommends. Agree?
Be respectful. No spam.
