AWS DevOps Engineer Professional Practice Test

What configuration is necessary to allow a custom patch repository in Systems Manager?

1. Adjust instance roles for access

2. Change S3 bucket permissions

3. Set a custom Patch Baseline

4. Enable versioning in the repository

The correct answer is: Set a custom Patch Baseline

The correct answer involves setting a custom Patch Baseline, as this is essential for configuring a custom patch repository in AWS Systems Manager. A custom Patch Baseline allows you to define your own patching policies and specify which patches are approved for installation on your managed instances. This baseline can include rules regarding which patches should be applied based on specific criteria, such as severity or classification, thus giving you more control over the patch management process. When working with Systems Manager, the ability to specify a custom Patch Baseline is particularly important for ensuring that your instances are updated according to your organization's requirements. It helps maintain consistency across your environment and aligns with your operational policies regarding security and compliance. The other options consider various aspects of AWS permissions and configurations but do not directly relate to the establishment of a custom patch repository. Adjusting instance roles pertains to permissions but does not specifically configure a patch repository. Changing S3 bucket permissions is related to the storage aspect but doesn't influence patch management directly. Enabling versioning in the repository addresses data management rather than the patching mechanism itself. Overall, the establishment of a custom Patch Baseline remains central to managing patches effectively in AWS Systems Manager.