Systems Manager Patching Maintenance Window with Cron
A company uses AWS Systems Manager to automate patching of EC2 instances. The instances are in an Auto Scaling group. The company wants to ensure that patching does not affect application availability. Which feature should be used?
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
Systems Manager Maintenance Windows allow scheduling patching during specific time windows, and can be configured to work with Auto Scaling to maintain availability by ensuring instances are patched without affecting the overall application availability. Option A is wrong because State Manager is used for maintaining consistent configuration of instances, not for scheduling patching. Option C is wrong because Patch Manager is the service that applies patches, but it is typically run within a Maintenance Window to control timing and availability. Option D is wrong because Run Command is for executing ad-hoc commands and scripts, not for scheduled patching with availability considerations.
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
State Manager is used to define and maintain a desired configuration state on managed instances through associations that run on a schedule. While an association can invoke a Patch Manager runbook, State Manager is not a purpose-built patching scheduler; it focuses on enforcing consistent configuration, not on coordinating patching activities with rate limits and start/stop windows. For scheduled patching, Maintenance Windows are the appropriate feature.
- ✓
Maintenance Windows
Why this is correct
Maintenance Windows are the Systems Manager feature designed to schedule time-bounded administrative actions, such as patching, during approved maintenance periods. They let you register Patch Manager tasks, Run Command commands, or Automation workflows, and control execution with rate limits and concurrency thresholds. This scheduling capability directly answers the need for automated patching with minimal business impact.
- ✗
Patch Manager
Why it's wrong here
Patch Manager is the component that performs the actual patch scanning and installation on EC2 instances and on-premises servers using patch baselines. However, Patch Manager itself has no built-in scheduling engine; it only executes when invoked on demand or by another service. To automate patching on a recurring schedule, you must assign Patch Manager tasks to a Maintenance Window, which provides the temporal and rate controls.
- ✗
Run Command
Why it's wrong here
Run Command enables you to execute Systems Manager documents, including those that invoke Patch Manager, against one or more managed nodes in real time. It is designed for interactive, on-demand operations and does not provide native scheduling or recurring maintenance capabilities. For automated, scheduled patching, you should attach a Run Command (or Patch Manager) task to a Maintenance Window rather than using Run Command by itself.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SOA-C02 question from scratch — 1,169 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.