mediumMultiple Choice

CCSP Practice Question: Refer to the exhibit

Exhibit

Refer to the exhibit.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetObject",
        "s3:ListBucket"
      ],
      "Resource": [
        "arn:aws:s3:::example-bucket",
        "arn:aws:s3:::example-bucket/*"
      ]
    },
    {
      "Effect": "Deny",
      "Action": [
        "s3:DeleteObject"
      ],
      "Resource": "arn:aws:s3:::example-bucket/*"
    }
  ]
}

Refer to the exhibit. An IAM policy is attached to a user. Which action is the user allowed to perform?

⚠ Common exam trap

ISC2 often tests the distinction between read and write permissions in S3 policies, where candidates mistakenly assume that `s3:GetObject` implies the ability to upload or modify objects, but each action (Get, Put, Delete) must be explicitly granted.

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

✓

Read an existing object from the bucket.

The IAM policy grants the `s3:GetObject` action, which allows the user to read (download) an existing object from the specified S3 bucket. The policy explicitly allows this action for the bucket `my-bucket` and its objects, so the user can perform read operations on objects within that bucket.

Answer analysis

Option-by-option breakdown

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

✗
Change the bucket's policy.
Why it's wrong here
The IAM policy grants s3:PutObject on the bucket's objects, not s3:PutBucketPolicy, so changing the bucket policy is denied. Bucket-policy modification requires an explicit s3:PutBucketPolicy permission on the bucket resource. This action would be allowed if the policy statement targeted the bucket ARN with that action.
✓
Read an existing object from the bucket.
Why this is correct
The policy grants s3:GetObject on the bucket's objects, so the user can retrieve existing objects. It does not permit s3:PutObject or s3:DeleteObject, so writing or removing objects is denied. Reading an existing object is therefore the only allowed action.
✗
Upload a new object to the bucket.
Why it's wrong here
The policy's action list covers object-level read operations such as s3:GetObject, not s3:PutObject, so uploading a new object is denied. Uploading requires s3:PutObject on the bucket's object ARN. This action would be permitted if the statement included s3:PutObject alongside the existing read permissions.
✗
Delete an object from the bucket.
Why it's wrong here
The policy grants read actions on objects, not s3:DeleteObject, so deleting an object is denied. Deletion requires s3:DeleteObject on the object ARN. This action would be allowed if the policy statement explicitly listed s3:DeleteObject for the bucket's objects.

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

CCSP Practice Question: Refer to the exhibit

Exhibit

Why each option matters

Option-by-option breakdown

AWS S3 Storage Class Comparison

Related to this question