SOA-C02 · Question #740
A SysOps administrator runs the AWS Systems Manager Run Command AWS- RunPatchBaseline document on a group of 20 Amazon Linux 2023 based Amazon EC2 instances. After the Run Command document runs…
The correct answer is A. The instances that were not updated were added to the patch exception in the patch baseline. Patch Manager lets you specify patch exceptions in a baseline. Any instance listed there will skip those patches (e.g., the latest kernel), even though the Run Command succeeded and the baseline is default. That’s the most likely reason they weren’t updated.
Question
A SysOps administrator runs the AWS Systems Manager Run Command AWS- RunPatchBaseline document on a group of 20 Amazon Linux 2023 based Amazon EC2 instances. After the Run Command document runs successfully, the SysOps administrator finds that some of the EC2 instances were not patched. The SysOps administrator verifies that the desired Amazon Linux 2023 patch baseline is set as the default baseline. What is the MOST likely reason some instances were not updated to the latest kernel?
Options
- AThe instances that were not updated were added to the patch exception in the patch baseline.
- BThe instances that were not updated have the PatchGroup tag.
- CThe instances that were not updated have a custom ResourceGroup tag.
- DThe instances that were not updated are considered noncompliant in the patch baseline.
How the community answered
(53 responses)- A77% (41)
- B4% (2)
- C6% (3)
- D13% (7)
Explanation
Patch Manager lets you specify patch exceptions in a baseline. Any instance listed there will skip those patches (e.g., the latest kernel), even though the Run Command succeeded and the baseline is default. That’s the most likely reason they weren’t updated.
Topics
Community Discussion
No community discussion yet for this question.