AWS Config for compliance - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How AWS Config evaluates compliance

When AWS Config evaluates a resource against a rule, what determines if the resource is marked as compliant?

A The resource is in the same AWS region as the Config service.

B The resource is tagged with 'compliant' by the user manually.

C The resource matches the rule's criteria and passes all evaluations.

D The resource has no changes recorded in the last 24 hours.

💡 Hint

Think about how AWS Config rules check resource settings automatically.

AWS Config marks a resource as compliant only if it meets the conditions defined in the rule during evaluation. Manual tagging or region alone does not affect compliance status.

❓ Architecture

intermediate

Designing AWS Config for multi-account compliance

You want to monitor compliance across multiple AWS accounts in your organization. Which AWS Config setup allows centralized compliance management?

A Use AWS Config aggregator in a designated account to collect compliance data from all member accounts.

B Enable AWS Config separately in each account without aggregation.

C Use CloudTrail to monitor compliance events across accounts.

D Create IAM roles in each account and manually check compliance.

💡 Hint

Think about a way to see all compliance data in one place.

AWS Config aggregator collects compliance and configuration data from multiple accounts and regions into one account for centralized viewing and analysis.

❓ security

advanced

Securing AWS Config data access

Which IAM policy condition best restricts AWS Config data access to only users connecting from your corporate network's IP range?

A "Condition": {"StringEquals": {"aws:username": "corp-user"}}

B "Condition": {"DateGreaterThan": {"aws:CurrentTime": "2024-01-01T00:00:00Z"}}

C "Condition": {"Bool": {"aws:MultiFactorAuthPresent": "true"}}

D "Condition": {"IpAddress": {"aws:SourceIp": ["203.0.113.0/24"]}}

💡 Hint

Restrict access based on IP addresses.

The IpAddress condition with aws:SourceIp limits access to requests coming from specified IP ranges, such as your corporate network.

✅ Best Practice

advanced

Optimizing AWS Config rule evaluations

You notice AWS Config rule evaluations are causing high costs. Which approach best reduces unnecessary evaluations?

A Disable AWS Config in all regions except one.

B Configure rules to trigger evaluations only on configuration changes instead of periodic checks.

C Increase the frequency of periodic evaluations to catch issues faster.

D Delete all custom rules and use only AWS managed rules.

💡 Hint

Think about when rules run evaluations.

Triggering evaluations only on configuration changes reduces the number of rule runs and lowers costs compared to frequent periodic evaluations.

🧠 Conceptual

expert

Understanding AWS Config compliance timeline

After enabling AWS Config and a custom rule, you notice some resources show non-compliant immediately, even though they meet the rule criteria. What is the most likely reason?

A AWS Config has not completed the initial full evaluation of all resources yet.

B The resources are in a different AWS region than the rule.

C The rule is disabled but still showing old compliance data.

D The resources are tagged incorrectly.

💡 Hint

Think about how AWS Config processes initial data.

When AWS Config and rules are first enabled, it takes time to evaluate all resources. Until then, some resources may temporarily show non-compliant.

Practice

1. What is the primary purpose of AWS Config in cloud management?

easy

A. To deploy applications automatically

B. To track changes in AWS resource configurations and check compliance

C. To monitor network traffic in real-time

D. To manage user permissions and roles

Solution

1. Step 1: Understand AWS Config's role

   AWS Config records configuration changes and evaluates compliance of AWS resources.

2. Step 2: Compare with other options

   Other options describe different AWS services like deployment, monitoring, or IAM, not AWS Config.

3. Final Answer:

   To track changes in AWS resource configurations and check compliance -> Option B

4. Quick Check:

   AWS Config = Compliance tracking [OK]

Hint: AWS Config = resource change tracking + compliance [OK]

Common Mistakes:

• Confusing AWS Config with deployment services
• Thinking AWS Config manages user permissions
• Mixing AWS Config with network monitoring tools

2. Which AWS Config component is responsible for recording resource configuration changes?

easy

A. Delivery Channel

B. Config Rule

C. Configuration Recorder

D. Compliance Pack

Solution

1. Step 1: Identify the component that records changes

   The Configuration Recorder captures resource configuration changes in AWS Config.

2. Step 2: Understand other components

   Config Rules evaluate compliance, Delivery Channel sends data to storage, Compliance Packs group rules.

3. Final Answer:

   Configuration Recorder -> Option C

4. Quick Check:

   Recorder = records changes [OK]

Hint: Recorder records changes; rules check compliance [OK]

Common Mistakes:

• Confusing Delivery Channel with recording
• Thinking Config Rule records changes
• Mixing Compliance Pack with recording function

3. Given this AWS Config rule JSON snippet, what does it check?

{
  "ConfigRuleName": "s3-bucket-public-read-prohibited",
  "Source": {
    "Owner": "AWS",
    "SourceIdentifier": "S3_BUCKET_PUBLIC_READ_PROHIBITED"
  }
}

medium

A. Checks if S3 buckets allow public read access

B. Checks if S3 buckets have versioning enabled

C. Checks if S3 buckets are encrypted

D. Checks if S3 buckets have lifecycle policies

Solution

1. Step 1: Analyze the SourceIdentifier

   The SourceIdentifier "S3_BUCKET_PUBLIC_READ_PROHIBITED" indicates the rule checks for public read access on S3 buckets.

2. Step 2: Match with options

   Checks if S3 buckets allow public read access matches the rule's purpose; others relate to different bucket settings.

3. Final Answer:

   Checks if S3 buckets allow public read access -> Option A

4. Quick Check:

   Rule name = public read check [OK]

Hint: Rule names often describe their check clearly [OK]

Common Mistakes:

• Assuming it checks encryption or versioning
• Ignoring the SourceIdentifier meaning
• Confusing lifecycle policies with access controls

4. You configured AWS Config but notice no compliance data is delivered. What is the most likely issue?

medium

A. Configuration Recorder is not started

B. Config Rules are disabled

C. IAM user lacks EC2 permissions

D. Delivery Channel is missing or misconfigured

Solution

1. Step 1: Understand data flow in AWS Config

   Configuration Recorder records changes; Delivery Channel sends data to S3 or SNS.

2. Step 2: Identify cause of no data delivery

   If no compliance data arrives, Delivery Channel is likely missing or misconfigured.

3. Final Answer:

   Delivery Channel is missing or misconfigured -> Option D

4. Quick Check:

   Delivery Channel = data delivery [OK]

Hint: Check Delivery Channel if no data arrives [OK]

Common Mistakes:

• Assuming Recorder is off without checking
• Confusing Config Rules with data delivery
• Blaming IAM permissions unrelated to Config

5. You want to enforce that all EC2 instances have a specific tag for cost center. Which AWS Config setup achieves this best?

hard

A. Create a Config Rule that checks EC2 instances for the required tag and alerts non-compliance

B. Use Configuration Recorder to record EC2 instance tags only

C. Set up Delivery Channel to send EC2 instance data to CloudTrail

D. Manually review EC2 instances weekly for tag compliance

Solution

1. Step 1: Identify enforcement method

   A Config Rule can automatically check EC2 instances for required tags and report compliance.

2. Step 2: Evaluate other options

   Recorder only records data, Delivery Channel sends data but doesn't enforce, manual review is inefficient.

3. Final Answer:

   Create a Config Rule that checks EC2 instances for the required tag and alerts non-compliance -> Option A

4. Quick Check:

   Config Rule = automatic compliance check [OK]

Hint: Use Config Rules to enforce resource settings automatically [OK]

Common Mistakes:

• Thinking Recorder enforces compliance
• Confusing Delivery Channel with enforcement
• Relying on manual checks instead of automation