SOA-C02 Deployment, Provisioning, and Automation Practice Question
A SysOps administrator manages a fleet of Amazon EC2 instances that run critical software. The administrator needs to automatically apply security patches every Tuesday at 2 AM. The instances are part of an Auto Scaling group and must be patched without downtime. Which AWS Systems Manager feature should be used?
⚠ Common exam trap
It's easy for candidates to confuse Patch Manager (the patching engine) with Maintenance Windows (the scheduler), assuming Patch Manager alone can handle recurring schedules, when in fact it requires Maintenance Windows or a separate cron-like trigger to run at a specific time.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Maintenance Windows
Maintenance Windows is the correct choice because it allows you to schedule a recurring window (every Tuesday at 2 AM) during which Systems Manager actions, such as patching, can be executed on EC2 instances. This feature is specifically designed to coordinate patching across Auto Scaling groups without downtime by ensuring instances are patched in a controlled manner, often using a patching rate or concurrency limit to maintain availability.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
State Manager
Why it's wrong here
AWS Systems Manager State Manager is designed to enforce and maintain a desired configuration state on managed instances through associations, such as ensuring a particular file exists or an agent remains in a specified state. While it can run on a schedule, its core purpose is compliance and drift correction, not orchestrating fleet-wide maintenance with capacity controls. It lacks the native ability to coordinate with Auto Scaling group capacity management, instance replacement, or zero-downtime patching workflows, so it is not the correct service for this scenario.
- ✗
Patch Manager
Why it's wrong here
AWS Systems Manager Patch Manager automates the process of scanning for and installing patches on EC2 instances using patch baselines. However, Patch Manager is merely a task engine—it can apply patches on a one-time or recurring schedule, but it does not provide the operational orchestration needed for a zero-downtime maintenance window. Specifically, it has no built-in capability to temporarily detach instances from an Auto Scaling group, adjust ASG minimum/maximum sizes to maintain capacity, or enforce concurrency limits and stop times across a fleet during patching. Without Maintenance Windows wrapping it, patching with Patch Manager alone would risk taking instances offline simultaneously, causing downtime.
- ✓
Maintenance Windows
Why this is correct
AWS Systems Manager Maintenance Windows is the purpose-built service for scheduling and executing administrative tasks during defined time windows while preserving availability. It allows you to register an Auto Scaling group as a target and assign tasks (such as Patch Manager or custom Automation) with rate control to limit concurrency and error thresholds, ensuring only a controlled subset of instances is patched at a time. Maintenance Windows supports stop times, task priorities, and integration with Run Command and Automation documents, which can be used to recycle instances, refresh launch templates, or place instances in Standby during the maintenance activity. This orchestration is precisely what enables zero-downtime patching across a fleet managed by Auto Scaling, making it the correct answer.
- ✗
Run Command
Why it's wrong here
AWS Systems Manager Run Command is intended for ad-hoc, on-demand execution of scripts or shell commands against a set of EC2 instances, typically initiated manually or via a single API call. It does not have a built-in schedule or recurring trigger, so it cannot independently ensure that maintenance happens within a specified window without an external scheduler like Amazon EventBridge. More importantly, Run Command does not understand Auto Scaling group capacity dynamics—it will not pause scale-in/scale-out processes, protect instances from termination, or wait for replacement instances to become healthy. While it can be used as a task inside a Maintenance Window, by itself it is not designed to orchestrate the zero-downtime patching workflow described in the question.
Go deeper
Related to this question
About these practice questions
This SOA-C02 question is part of Courseiva's 1,169-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SOA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SOA-C02 exam.