SOA-C02 Deployment, Provisioning, and Automation Practice Question
A company uses AWS CloudFormation to deploy a stack that includes an Amazon S3 bucket. The stack creation fails because the S3 bucket name already exists. What should the administrator do to resolve this issue?
⚠ Common exam trap
SOA-C02 often tests whether candidates remember that S3 bucket names are globally unique — the tempting wrong answer is to manipulate the existing bucket (tags, policy) rather than rename the one being created.
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
✓
Change the S3 bucket name in the CloudFormation template to a unique name.
S3 bucket names are globally unique across all AWS accounts and regions, so CloudFormation cannot create a bucket whose name is already taken by another account. The correct fix is to change the BucketName property in the template to a name that is not in use, then re-run the stack. This resolves the naming collision without touching resources owned by other accounts.
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 a tag to the existing bucket to make it available for the stack.
Why it's wrong here
Adding a tag to the existing bucket is futile because S3 bucket names are globally unique across all AWS accounts and regions. CloudFormation calls the CreateBucket API with the exact name from the template, and that request fails with a 409 BucketAlreadyExists error regardless of any tags on the pre-existing bucket. Tags are metadata for cost tracking and resource identification, not a mechanism to claim or reuse an existing bucket in a stack.
- ✓
Change the S3 bucket name in the CloudFormation template to a unique name.
Why this is correct
Changing the S3 bucket name in the CloudFormation template to a unique name resolves the conflict because the CreateBucket API only needs a name that is not already taken globally. This is the correct approach because it allows CloudFormation to provision a brand-new bucket without naming collision. Alternatively, you could omit the BucketName property entirely so CloudFormation generates a unique name with a random suffix, but specifying a deliberate unique name works equally well.
- ✗
Delete the existing S3 bucket and recreate the stack.
Why it's wrong here
Deleting the existing bucket is unnecessarily destructive and does not guarantee success — the bucket name may enter a lingering period or be taken by another account after deletion. Moreover, you should not delete production data just to appease a template; the proper fix is to modify the template so the bucket name is unique. CloudFormation updates are designed to apply changes to the template without forcing you to destroy unrelated resources or data.
- ✗
Update the bucket policy to allow the stack to use the bucket.
Why it's wrong here
Updating the bucket policy is irrelevant because the failure occurs during the CreateBucket call, which is a metadata operation that is not subject to the policy of an existing bucket. Bucket policies govern authorized actions on a bucket, such as GetObject or PutObject, but they cannot grant CloudFormation permission to claim a name that is already in use. Resolving the name conflict requires a different bucket name, not a change to permissions or access controls.
Visual reference
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
Related to this question
About these practice questions
This SOA-C02 question is part of Courseiva's 1,169-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
This SOA-C02 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 SOA-C02 exam.