Question 1 A bucket policy changed overnight. Which service tells Todo.io who changed it?
Choose one answer AWS CloudTrail. Correct. It records the PutBucketPolicy call: who made it, when and from where. AWS Config. Not this one. Config shows what the policy looked like before and after, not who made the call. Amazon CloudWatch Logs. Not this one. Logs hold what applications print. IAM Identity Center. Not this one. Identity Center handles sign-in; it doesn't record API calls.
Learn it: CloudTrail · AWS Config
Question 2 Todo.io wants to see how a security group's rules looked last Tuesday, and every change since. Which service shows that?
Choose one answer Learn it: AWS Config
Question 3 A Config rule checks that no S3 bucket is public. A teammate makes a bucket public. Does the rule stop it?
Choose one answer No. Config reports the bucket as noncompliant after the change; it doesn't block it. Correct. Config is detective. You can attach a remediation that fixes it afterwards, but blocking needs a preventive control such as an SCP. Yes. Config rules block changes that break them. Not this one. Config evaluates after the fact. Yes, by deleting the bucket. Not this one. Config never deletes resources on its own. Only if CloudTrail is turned off. Not this one. CloudTrail has nothing to do with it.
Learn it: AWS Config · Control Tower controls
Question 4 What does an AWS Config rule mark each resource it checks as?
Choose one answer Compliant or noncompliant. Correct. The result shows on the Config (and Control Tower) dashboards. Allowed or denied. Not this one. That is how IAM answers requests. Public or private. Not this one. That is one thing a rule might check, not what it marks. Healthy or unhealthy. Not this one. That is how load balancers describe targets (Level 2).
Learn it: AWS Config
Question 5 AWS Config shows that a bucket became public at 14:02. Where should Todo.io look to find out who did it?
Choose one answer CloudTrail, for the call that changed the bucket around 14:02. Correct. Config says what changed and when; CloudTrail says who made the call. AWS Config again; it records the caller. Not this one. Config records the resource's settings, not the caller. CloudWatch Logs. Not this one. App output won't show who called S3. The bucket's object list. Not this one. Objects don't record who changed the bucket's settings.
Learn it: AWS Config · CloudTrail
Question 6 What are Control Tower's detective controls built from?
Choose one answer AWS Config rules. Correct. They spot problems after they happen and report them. Service control policies. Not this one. SCPs are the preventive controls. CloudFormation hooks. Not this one. Hooks are the proactive controls. IAM policies in each account. Not this one. Controls are applied across OUs, not written into each account's IAM.
Learn it: AWS Config · Controls (guardrails)
Question 7 Todo.io's auditors want ongoing evidence that every EBS volume is encrypted. What provides it?
Choose one answer An AWS Config rule that checks volume encryption, with its compliance history. Correct. Config keeps checking and keeps the record auditors need. CloudTrail Event history. Not this one. It shows calls, not whether every volume is encrypted right now. An SCP. Not this one. An SCP could block unencrypted volumes, but it produces no evidence about existing ones. A spreadsheet updated by hand. Not this one. Out of date the moment anything changes.
Learn it: AWS Config
Question 8 What does AWS Config record?
Choose one answer Each resource's configuration, and how it changes over time. Correct. A timeline of what each resource looked like. Only who made each API call. Not this one. That is CloudTrail. Application log lines. Not this one. That is CloudWatch Logs. Every network packet. Not this one. Config doesn't see traffic.
Learn it: AWS Config
Question 9 Todo.io turned on AWS Config in us-east-1 only. Resources in eu-west-1 aren't being recorded. Why?
Choose one answer Config records per Region; it has to be turned on in every Region Todo.io uses. Correct. Control Tower does this for you in the Regions it governs. Config is global, so this must be a bug. Not this one. Config is regional. Config doesn't work in eu-west-1. Not this one. It works in every commercial Region. Config needs CloudTrail to be on first. Not this one. They are separate services.
Learn it: AWS Config · Region
Question 10 Todo.io wants one view of compliance across all its accounts and Regions. What gives that?
Choose one answer A Config aggregator (for example in the Audit account) that collects results from every account and Region. Correct. One place to see what is noncompliant anywhere. Signing in to each account and Region in turn. Not this one. It works, but it is slow and easy to miss something. CloudTrail Event history. Not this one. It shows API calls, not compliance. IAM Identity Center. Not this one. It handles sign-in, not compliance.
Learn it: AWS Config
Question 11 What does "AWS Config" mean?
Choose one answer Learn it: AWS Config
Question 12 Which term is this? "Records how your resources are configured over time and checks them against rules."
Choose one answer Learn it: AWS Config
Question 13 Which AWS term is described by this analogy? "A building inspector with a notebook and a camera."
Choose one answer Learn it: AWS Config