The answer is to coordinate with the module maintainers to update the module, using the new encryption resource and removing the deprecated argument in a later release. This is correct because the AWS provider now recommends separate sub-resources like `aws_s3_bucket_server_side_encryption_configuration` over the deprecated `server_side_encryption_configuration` argument inside the bucket resource, and a direct in-place update to the shared module could break other teams' configurations. On the HashiCorp Terraform Associate TF-003 exam, this scenario tests your understanding of provider lifecycle management and safe refactoring patterns, specifically how to migrate S3 bucket encryption to new Terraform resources without disrupting existing infrastructure. A common trap is assuming you can simply add the new resource and delete the old argument in one plan, but Terraform will attempt to update the bucket in-place, potentially causing drift for other consumers. Remember the migration mantra: “Add the new, remove the old, but coordinate the rollout.”
TF-003 Read, generate and modify configuration Practice Question
This TF-003 practice question tests your understanding of read, generate and modify configuration. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 large organization uses Terraform to manage hundreds of AWS resources across multiple accounts. They have a central repository with modules for common patterns. A new engineer is tasked with adding a new feature that requires modifying the configuration of an existing S3 bucket to enable server-side encryption. The current configuration for the bucket is defined in a module that is used by many other teams. The engineer adds an `aws_s3_bucket_server_side_encryption_configuration` resource as recommended by the latest AWS provider. After running `terraform plan`, they see that the plan will create the new encryption resource but also shows an in-place update to the bucket itself. They check the bucket resource and see that it has a `server_side_encryption_configuration` argument that is deprecated. The engineer wants to ensure backward compatibility and avoid breaking other teams' configurations. What is the best course of action?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Use the deprecated `server_side_encryption_configuration` argument in the bucket resource to avoid adding a new resource.
Why wrong: deprecated and may be removed in future provider versions
B
Coordinate with the module maintainers to update the module, using the new encryption resource and removing the deprecated argument in a later release.
ensures backward compatibility via module versioning
C
Proceed with the plan as is, since the in-place update is expected during migration.
Why wrong: the plan shows a create and update; need to ensure consistency
D
Add a `lifecycle` block with `create_before_destroy` to the new encryption resource to prevent destruction.
Why wrong: not needed; the new resource is created, not replacing
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Coordinate with the module maintainers to update the module, using the new encryption resource and removing the deprecated argument in a later release.
Option D is correct because using the new separate resource is the modern approach, and migrating from the old argument requires careful coordination. The best course is to implement the change using the new resource and update the module's version, communicating the change. Option A is wrong because using the deprecated argument is not recommended. Option B is wrong because the plan already shows the correct approach; ignoring the plan might cause issues. Option C is wrong because forcing recreation might break other teams.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use the deprecated `server_side_encryption_configuration` argument in the bucket resource to avoid adding a new resource.
Why it's wrong here
deprecated and may be removed in future provider versions
✓
Coordinate with the module maintainers to update the module, using the new encryption resource and removing the deprecated argument in a later release.
Why this is correct
ensures backward compatibility via module versioning
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Static NAT maps one inside address to one outside address.
✗
Proceed with the plan as is, since the in-place update is expected during migration.
Why it's wrong here
the plan shows a create and update; need to ensure consistency
✗
Add a `lifecycle` block with `create_before_destroy` to the new encryption resource to prevent destruction.
Why it's wrong here
not needed; the new resource is created, not replacing
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Trap categories for this question
Command / output trap
the plan shows a create and update; need to ensure consistency
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related TF-003 NAT questions on configuration and troubleshooting.
Read, generate and modify configuration — This question tests Read, generate and modify configuration — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Coordinate with the module maintainers to update the module, using the new encryption resource and removing the deprecated argument in a later release. — Option D is correct because using the new separate resource is the modern approach, and migrating from the old argument requires careful coordination. The best course is to implement the change using the new resource and update the module's version, communicating the change. Option A is wrong because using the deprecated argument is not recommended. Option B is wrong because the plan already shows the correct approach; ignoring the plan might cause issues. Option C is wrong because forcing recreation might break other teams.
What should I do if I get this TF-003 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related TF-003 NAT questions on configuration and troubleshooting.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 →
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.
This TF-003 practice question is part of Courseiva's free HashiCorp 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 TF-003 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.