← DEA-C01·Amazon Web Services

Question 460 of 1,786

Data Security and Governance →mediumMultiple SelectObjective-mapped

Quick Answer

The answer is a combination of an Allow statement for s3:PutObject and a Deny statement for all other actions, both scoped to the partner’s account and the specific prefix. This cross-account S3 write-only policy works by first granting the partner permission to write objects via the Allow on s3:PutObject, then explicitly denying any action that is not s3:PutObject, which effectively blocks reads, deletes, and overwrites. On the AWS Certified Data Engineer Associate DEA-C01 exam, this scenario tests your understanding of the principle of least privilege combined with explicit Deny to override any implicit or future permissions—a common trap is thinking a single Allow statement is enough, but without the Deny, the partner could still read or delete if other policies grant those rights. Remember the memory tip: “Allow the write, Deny the rest” to lock down cross-account access to a single action.

DEA-C01 Data Security and Governance Practice Question

This DEA-C01 practice question tests your understanding of data security and governance. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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 data engineer is configuring an S3 bucket policy to allow cross-account access for a partner organization to write data to a specific prefix. The partner's AWS account ID is 111111111111. The engineer wants to ensure that only the partner can write, and that the partner cannot read or delete objects. Which policy statements should be included? (Choose TWO.)

Question 1mediummulti select

Full question →

A
{"Effect":"Allow","Principal":{"AWS":"arn:aws:iam::111111111111:user/PartnerUser"},"Action":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*"}
Why wrong: Specifies a user ARN, not account; not scalable.
B
{"Effect":"Allow","Principal":"*","Action":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*","Condition":{"StringEquals":{"aws:SourceAccount":"111111111111"}}}
Why wrong: Principal '*' allows anyone, condition may not be sufficient.
C
{"Effect":"Allow","Principal":{"AWS":"111111111111"},"Action":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*"}
Grants write access to the prefix.
D
{"Effect":"Allow","Principal":{"AWS":"111111111111"},"Action":["s3:GetObject","s3:DeleteObject"],"Resource":"arn:aws:s3:::mybucket/partner/*"}
Why wrong: Grants read and delete, which are not allowed.
E
{"Effect":"Deny","Principal":{"AWS":"111111111111"},"NotAction":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*"}
Denies all actions except PutObject.

Full breakdown with real-world context →

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

✓

{"Effect":"Allow","Principal":{"AWS":"111111111111"},"Action":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*"}

Options A and C are correct. Option A grants s3:PutObject for the prefix. Option C explicitly denies all other actions. Option B is wrong because it grants read and delete. Option D is wrong because the principal should be the partner's account root. Option E is wrong because using a condition without explicit deny may not block all actions.

Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.

Answer analysis

Option-by-option breakdown

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

✗
{"Effect":"Allow","Principal":{"AWS":"arn:aws:iam::111111111111:user/PartnerUser"},"Action":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*"}
Why it's wrong here
Specifies a user ARN, not account; not scalable.
✗
{"Effect":"Allow","Principal":"*","Action":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*","Condition":{"StringEquals":{"aws:SourceAccount":"111111111111"}}}
Why it's wrong here
Principal '*' allows anyone, condition may not be sufficient.
✓
{"Effect":"Allow","Principal":{"AWS":"111111111111"},"Action":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*"}
Why this is correct
Grants write access to the prefix.
Related concept
Standard ACLs match source addresses.
✗
{"Effect":"Allow","Principal":{"AWS":"111111111111"},"Action":["s3:GetObject","s3:DeleteObject"],"Resource":"arn:aws:s3:::mybucket/partner/*"}
Why it's wrong here
Grants read and delete, which are not allowed.
✓
{"Effect":"Deny","Principal":{"AWS":"111111111111"},"NotAction":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*"}
Why this is correct
Denies all actions except PutObject.
Related concept
Standard ACLs match source addresses.

Common exam traps

Common exam trap: ACLs stop at the first match

ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.

Detailed technical explanation

How to think about this question

ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.

KKey Concepts to Remember

Standard ACLs match source addresses.
Extended ACLs can match source, destination, protocol and ports.
The first matching ACL entry is used.
There is usually an implicit deny at the end.

TExam Day Tips

Check inbound versus outbound direction.
Read the ACL from top to bottom.
Look for a broader permit or deny above the intended line.

Key takeaway

ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.

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 ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related DEA-C01 ACL questions on filtering logic and placement.

Related DEA-C01 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Data Ingestion and Transformation practice questions

Practise DEA-C01 questions linked to Data Ingestion and Transformation.

Data Operations and Support practice questions

Practise DEA-C01 questions linked to Data Operations and Support.

Data Security and Governance practice questions

Practise DEA-C01 questions linked to Data Security and Governance.

Data Store Management practice questions

Practise DEA-C01 questions linked to Data Store Management.

DEA-C01 fundamentals practice questions

Practise DEA-C01 questions linked to DEA-C01 fundamentals.

DEA-C01 scenario practice questions

Practise DEA-C01 questions linked to DEA-C01 scenario.

DEA-C01 troubleshooting practice questions

Practise DEA-C01 questions linked to DEA-C01 troubleshooting.

Practice this exam

Start a free DEA-C01 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

DEA-C01 practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this DEA-C01 question test?

Data Security and Governance — This question tests Data Security and Governance — Standard ACLs match source addresses..

What is the correct answer to this question?

The correct answer is: {"Effect":"Allow","Principal":{"AWS":"111111111111"},"Action":"s3:PutObject","Resource":"arn:aws:s3:::mybucket/partner/*"} — Options A and C are correct. Option A grants s3:PutObject for the prefix. Option C explicitly denies all other actions. Option B is wrong because it grants read and delete. Option D is wrong because the principal should be the partner's account root. Option E is wrong because using a condition without explicit deny may not block all actions.

What should I do if I get this DEA-C01 question wrong?

What is the key concept behind this question?

Standard ACLs match source addresses.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

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.

Loading comments…

This DEA-C01 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 DEA-C01 exam.