AWS Config for compliance - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable AWS Config recording for all supported resource types.

AWS

aws configservice start-configuration-recorder --configuration-recorder-name [1]

Drag options to blanks, or click blank then click option'

Aconfig-recorder

Bdefault

Call-resources

Dresource-tracker

Attempts:

3 left

💡 Hint

Common Mistakes

Using a generic name like 'default' which may not exist.

Confusing resource types with recorder names.

The configuration recorder name must match the one created in AWS Config setup, commonly 'config-recorder'.

2fill in blank

medium

Complete the code to create an AWS Config rule that checks whether S3 buckets have versioning enabled.

AWS

aws configservice put-config-rule --config-rule file://[1]

Drag options to blanks, or click blank then click option'

As3-versioning-check.json

Bec2-instance-check.json

Ciam-password-policy.json

Dvpc-flow-logs-check.json

Attempts:

3 left

💡 Hint

Common Mistakes

Using a rule file unrelated to S3 buckets.

Mistyping the file name or path.

The JSON file 's3-versioning-check.json' contains the rule definition for checking S3 bucket versioning compliance.

3fill in blank

hard

Fix the error in the AWS Config delivery channel creation command by completing the missing parameter.

AWS

aws configservice put-delivery-channel --delivery-channel '{"name":"default","s3BucketName":"[1]"}'

Drag options to blanks, or click blank then click option'

Abucket-config

Bconfig-bucket-123

Caws-config-bucket

Dmy-config-bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using a bucket name that does not exist.

Using a generic or placeholder bucket name.

The S3 bucket name must be the exact bucket created for AWS Config delivery, here 'config-bucket-123'.

4fill in blank

hard

Fill both blanks to create a compliance summary command filtering by resource type and compliance status.

AWS

aws configservice get-compliance-summary --compliance-types [1] --resource-types [2]

Drag options to blanks, or click blank then click option'

ANON_COMPLIANT

BCOMPLIANT

CAWS::S3::Bucket

DAWS::EC2::Instance

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing compliance types or resource types incorrectly.

Using resource types not supported by AWS Config.

The command filters for non-compliant S3 buckets to check compliance status.

5fill in blank

hard

Fill all three blanks to create a command that lists all AWS Config rules with a specific tag key and value.

AWS

aws configservice describe-config-rules --filters Key=[1],Value=[2],Values=[3]

Drag options to blanks, or click blank then click option'

Atag-key

BEnvironment

CProduction

Drule-name

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect filter keys.

Mixing tag keys and rule names in filters.

The filter uses 'tag-key' with key 'Environment' and value 'Production' to list matching config rules.

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