ANS-C01 Network Security, Compliance and Governance Practice Question

Exhibit

Refer to the exhibit.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Deny",
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::example-bucket/*",
      "Condition": {
        "StringNotEquals": {
          "s3:x-amz-server-side-encryption": "aws:kms"
        }
      }
    }
  ]
}

Refer to the exhibit. A security engineer applies this S3 bucket policy. What is the result of this policy?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

All PutObject requests must use SSE-KMS encryption.

The S3 bucket policy denies s3:PutObject unless the request uses SSE-KMS encryption (condition StringNotEquals 'aws:kms'). This forces all PutObject requests to use SSE-KMS. Option A is incorrect because the policy does not allow SSE-S3; only SSE-KMS is permitted. Option C is incorrect because the policy does not require a specific KMS key; it only checks that encryption is SSE-KMS. Option D is incorrect because the policy explicitly denies requests without SSE-KMS, not allows all.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
All objects must be encrypted with SSE-S3 or SSE-KMS.
Why it's wrong here
The condition requires aws:kms, not SSE-S3.
✓
All PutObject requests must use SSE-KMS encryption.
Why this is correct
The policy denies if encryption is not aws:kms.
✗
All objects must be encrypted with a specific KMS key.
Why it's wrong here
The policy does not specify a key ID, only the encryption type.
✗
All PutObject requests are allowed regardless of encryption.
Why it's wrong here
The policy denies if condition not met.

Quick reference

AWS S3 Storage Class Comparison

Storage Class	Min Duration	Retrieval	Use Case
S3 Standard	None	Immediate	Frequently accessed data
S3 Standard-IA	30 days	Immediate	Infrequent access, rapid retrieval
S3 One Zone-IA	30 days	Immediate	Non-critical infrequent data
S3 Intelligent-Tiering	None	Immediate–hours	Unknown or changing access patterns
S3 Glacier Instant	90 days	Milliseconds	Archive with instant retrieval
S3 Glacier Flexible	90 days	Minutes–hours	Archive, flexible retrieval
S3 Glacier Deep Archive	180 days	Hours	Long-term compliance archive

Go deeper

ANS-C01 Network Security, Compliance and Governance Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

AWS S3 Storage Class Comparison

Related to this question