- A
Add an Allow statement granting s3:PutObject to the developer role; rely on IAM conditions in the developer role to enforce TLS and SSE-KMS.
Why wrong: A bucket policy Allow does not directly enforce the requirement in a way that rejects noncompliant requests. IAM conditions on the developer role may not apply to every caller (for example, other principals) and are not centrally enforced at the bucket level. The most direct enforcement for a bucket-wide requirement is a policy that explicitly Denies noncompliant PutObject requests based on request attributes.
- B
Use Deny statements that reject PutObject when aws:SecureTransport is false and reject PutObject when s3:x-amz-server-side-encryption is not 'aws:kms' or when s3:x-amz-server-side-encryption-aws-kms-key-id does not equal 'abcd-1234'.
These Deny conditions directly block noncompliant requests regardless of the caller’s IAM permissions because explicit Deny in a resource policy overrides any Allow. aws:SecureTransport identifies whether the request used TLS. The SSE-KMS headers (s3:x-amz-server-side-encryption and s3:x-amz-server-side-encryption-aws-kms-key-id) identify whether SSE-KMS was requested and which CMK key id was used.
- C
Enable S3 default encryption to SSE-KMS and remove any bucket policy enforcement, since default encryption automatically rejects all noncompliant uploads.
Why wrong: S3 default encryption applies only when clients omit encryption headers. It does not reliably enforce that the client used a specific CMK key id when encryption headers are provided, and it does not guarantee rejection of explicit noncompliant encryption headers.
- D
Attach a WAF rule to the S3 website endpoint to block non-TLS requests, because bucket policies cannot evaluate aws:SecureTransport.
Why wrong: WAF generally applies to supported front-end integrations (such as CloudFront or API Gateway). S3 website endpoints are not the standard S3 API path for PutObject. In contrast, bucket policies can evaluate aws:SecureTransport for S3 API requests, so WAF is not the correct control here.
Quick Answer
The answer is to use Deny statements that reject PutObject when aws:SecureTransport is false and reject PutObject when s3:x-amz-server-side-encryption is not 'aws:kms' or when s3:x-amz-server-side-encryption-aws-kms-key-id does not equal 'abcd-1234'. This approach directly enforces both TLS and SSE-KMS with a specific CMK because bucket policies evaluate Deny statements before Allow statements, ensuring any request missing encryption or using the wrong key is blocked regardless of other permissions. On the SAA-C03 exam, this tests your understanding of S3 bucket policy condition keys for security controls, often appearing as a scenario where developers report uploads succeeding despite non-compliant requests—a common trap is assuming an Allow with conditions is sufficient, but Deny explicitly rejects non-compliant traffic. Remember the memory tip: "Deny to defy non-compliance"—use Deny, not Allow, to enforce mandatory encryption and TLS at the bucket policy level.
SAA-C03 Design Secure Architectures Practice Question
This SAA-C03 practice question tests your understanding of design secure architectures. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: explicit Deny in S3 bucket policies overrides Allow statements.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A security requirement states: all uploads to an S3 bucket must (1) use TLS in transit and (2) use server-side encryption with AWS KMS (SSE-KMS) using the CMK key id 'abcd-1234'; otherwise the upload should be rejected. A developer reports that uploads are succeeding even though clients are sometimes using non-encrypted requests. Which bucket policy approach most directly enforces both controls?
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
Use Deny statements that reject PutObject when aws:SecureTransport is false and reject PutObject when s3:x-amz-server-side-encryption is not 'aws:kms' or when s3:x-amz-server-side-encryption-aws-kms-key-id does not equal 'abcd-1234'.
Option B is correct because bucket policies can use the `aws:SecureTransport` condition key to enforce TLS and the `s3:x-amz-server-side-encryption` and `s3:x-amz-server-side-encryption-aws-kms-key-id` condition keys to enforce SSE-KMS with the specific CMK key ID. By using Deny statements, any request that does not meet both conditions is explicitly rejected, regardless of any Allow statements that might otherwise grant access. This directly enforces the security requirement at the bucket level.
Key principle: Explicit Deny in S3 bucket policies overrides Allow statements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add an Allow statement granting s3:PutObject to the developer role; rely on IAM conditions in the developer role to enforce TLS and SSE-KMS.
Why it's wrong here
A bucket policy Allow does not directly enforce the requirement in a way that rejects noncompliant requests. IAM conditions on the developer role may not apply to every caller (for example, other principals) and are not centrally enforced at the bucket level. The most direct enforcement for a bucket-wide requirement is a policy that explicitly Denies noncompliant PutObject requests based on request attributes.
- ✓
Use Deny statements that reject PutObject when aws:SecureTransport is false and reject PutObject when s3:x-amz-server-side-encryption is not 'aws:kms' or when s3:x-amz-server-side-encryption-aws-kms-key-id does not equal 'abcd-1234'.
Why this is correct
These Deny conditions directly block noncompliant requests regardless of the caller’s IAM permissions because explicit Deny in a resource policy overrides any Allow. aws:SecureTransport identifies whether the request used TLS. The SSE-KMS headers (s3:x-amz-server-side-encryption and s3:x-amz-server-side-encryption-aws-kms-key-id) identify whether SSE-KMS was requested and which CMK key id was used.
Related concept
Explicit Deny in S3 bucket policies overrides Allow statements.
- ✗
Enable S3 default encryption to SSE-KMS and remove any bucket policy enforcement, since default encryption automatically rejects all noncompliant uploads.
Why it's wrong here
S3 default encryption applies only when clients omit encryption headers. It does not reliably enforce that the client used a specific CMK key id when encryption headers are provided, and it does not guarantee rejection of explicit noncompliant encryption headers.
- ✗
Attach a WAF rule to the S3 website endpoint to block non-TLS requests, because bucket policies cannot evaluate aws:SecureTransport.
Why it's wrong here
WAF generally applies to supported front-end integrations (such as CloudFront or API Gateway). S3 website endpoints are not the standard S3 API path for PutObject. In contrast, bucket policies can evaluate aws:SecureTransport for S3 API requests, so WAF is not the correct control here.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse S3 default encryption with enforcement—default encryption only applies encryption to objects that lack it, but does not reject non-compliant uploads, so it cannot replace a bucket policy Deny statement for rejecting requests that violate encryption or TLS requirements.
Detailed technical explanation
How to think about this question
The `aws:SecureTransport` condition key checks whether the request was sent over HTTPS (TLS), while the `s3:x-amz-server-side-encryption` and `s3:x-amz-server-side-encryption-aws-kms-key-id` condition keys inspect the corresponding request headers. A common subtlety is that if you use an Allow statement with these conditions, a request that fails the condition might still be allowed by a broader Allow statement; using Deny statements with `Null` checks ensures that missing headers or non-compliant values cause explicit denial. In real-world scenarios, this pattern is critical for compliance frameworks like PCI-DSS or HIPAA that mandate encryption in transit and at rest.
KKey Concepts to Remember
- Explicit Deny in S3 bucket policies overrides Allow statements.
- The `aws:SecureTransport` condition enforces TLS for S3 requests.
- S3 bucket policies can inspect request headers for encryption details.
- Condition keys `s3:x-amz-server-side-encryption` and `s3:x-amz-server-side-encryption-aws-kms-key-id` enforce SSE-KMS specifics.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Explicit Deny in S3 bucket policies overrides Allow statements.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review explicit Deny in S3 bucket policies overrides Allow statements., then practise related SAA-C03 questions on the same topic to reinforce the concept.
- →
Design Secure Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Secure Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SAA-C03 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
Design Secure Architectures — This question tests Design Secure Architectures — Explicit Deny in S3 bucket policies overrides Allow statements..
What is the correct answer to this question?
The correct answer is: Use Deny statements that reject PutObject when aws:SecureTransport is false and reject PutObject when s3:x-amz-server-side-encryption is not 'aws:kms' or when s3:x-amz-server-side-encryption-aws-kms-key-id does not equal 'abcd-1234'. — Option B is correct because bucket policies can use the `aws:SecureTransport` condition key to enforce TLS and the `s3:x-amz-server-side-encryption` and `s3:x-amz-server-side-encryption-aws-kms-key-id` condition keys to enforce SSE-KMS with the specific CMK key ID. By using Deny statements, any request that does not meet both conditions is explicitly rejected, regardless of any Allow statements that might otherwise grant access. This directly enforces the security requirement at the bucket level.
What should I do if I get this SAA-C03 question wrong?
Review explicit Deny in S3 bucket policies overrides Allow statements., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Explicit Deny in S3 bucket policies overrides Allow statements.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.