A SysOps Administrator is setting up AWS Systems Manager Patch Manager to automate operating system updates for a fleet of Amazon Linux 2 instances. The administrator has created a custom patch baseline for development environments. However, during testing, the administrator notices that the development instances are still being patched using the default AWS-managed patch baseline instead of the custom one. Which action must the administrator take to ensure the development instances are associated with the custom patch baseline?
- Apply a tag to the development instances with the key 'Patch Group' and a custom group value, then register this patch group with the custom patch baseline.Cevap
- BApply a tag to the development instances with the key 'patch-group' and a custom group value, then register this patch group with the custom patch baseline.
- CApply a tag to the development instances with the key 'PatchBaseline' and the ARN of the custom patch baseline as the value.
- DConfigure an IAM instance profile on the development instances that includes the iam:PassRole permission allowed for the custom patch baseline.
Cevap
Apply a tag to the development instances with the key 'Patch Group' and a custom group value, then register this patch group with the custom patch baseline.
The correct action is to apply a tag to the development instances using the key 'Patch Group' and the designated group name as the value, and then register that patch group name with the custom patch baseline. Patch Manager automatically evaluates this tag to redirect the instances from the default baseline to the custom baseline.
Adım Adım Çözüm
Anahtar Kavram
AWS Systems Manager Patch Manager uses the case-sensitive tag key 'Patch Group' to map managed instances to custom patch baselines.
Tahmini Süre:1m 0s