DEA-C01 Data Operations and Support Practice Question

Exhibit

Refer to the exhibit.

IAM Policy:
```json
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:PutObject",
                "s3:DeleteObject"
            ],
            "Resource": "arn:aws:s3:::data-lake-bucket/*"
        },
        {
            "Effect": "Deny",
            "Action": "s3:*",
            "Resource": "arn:aws:s3:::data-lake-bucket/confidential/*"
        }
    ]
}
```

A user with this policy tries to upload an object to `s3://data-lake-bucket/confidential/report.pdf`. What will happen?

A data engineer is troubleshooting an access issue. A user has the IAM policy shown in the exhibit. The user attempts to upload an object to `s3://data-lake-bucket/confidential/report.pdf`. What will happen?

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

✓

The upload will fail with an 'Access Denied' error.

The explicit Deny statement in the IAM policy overrides the Allow statement, so the user is denied permission to upload to the 'confidential' path. Therefore, the upload will fail with an 'Access Denied' error, making option A correct.

Answer analysis

Option-by-option breakdown

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

✓
The upload will fail with an 'Access Denied' error.
Why this is correct
The Deny statement explicitly denies all s3 actions on the confidential prefix, taking precedence over the Allow.
✗
The upload will succeed because the Deny statement is not valid without a condition.
Why it's wrong here
The Deny statement is valid as written.
✗
The upload will succeed because the Allow statement is more specific than the Deny.
Why it's wrong here
Deny always overrides Allow regardless of specificity.
✗
The upload will succeed because the user has s3:PutObject permission on the bucket.
Why it's wrong here
The explicit Deny on the confidential path overrides the Allow.

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

DEA-C01 Data Operations and Support Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

AWS S3 Storage Class Comparison

Related to this question