Explanation:
AWS Config is the primary service for assessing, auditing, and evaluating configurations. It has managed rules to check for IAM access key rotation (like access-keys-rotated). AWS Config integrates directly with AWS Systems Manager (SSM) Automation for automated remediation, allowing for the rotation of keys that violate the 30-day policy. Trusted Advisor provides recommendations but does not offer the same integrated, event-driven remediation framework as AWS Config for this specific use case.
Ultimate access to all questions.
Question 20: A company is using AWS to deploy a critical application on a fleet of Amazon EC2 instances. The company is rewriting the application because the application failed a security review. The application will take 12 months to rewrite. While this rewrite happens, the company needs to rotate IAM access keys that the application uses.
A SysOps administrator must implement an automated solution that finds and rotates IAM access keys that are at least 30 days old. The solution must then continue to rotate the IAM access keys every 30 days.
Which solution will meet this requirement with the MOST operational efficiency?
A
Use an AWS Config rule to identify IAM access keys that are at least 30 days old. Configure AWS Config to invoke an AWS Systems Manager Automation runbook to rotate the identified IAM access keys.
B
Use AWS Trusted Advisor to identify IAM access keys that are at least 30 days old. Configure Trusted Advisor to invoke an AWS Systems Manager Automation runbook to rotate the identified IAM access keys.
C
Create a script that checks the age of IAM access keys and rotates them if they are at least 30 days old. Launch an EC2 instance. Schedule the script to run as a cron expression on the EC2 instance every day.
D
Create an AWS Lambda function that checks the age of IAM access keys and rotates them if they are at least 30 days old. Use an Amazon EventBridge rule to invoke the Lambda function every time a new IAM access key is created.
No comments yet.