Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

HashiCorp Exam Terraform-Associate-003 Topic 6 Question 35 Discussion

Actual exam question for HashiCorp's Terraform-Associate-003 exam
Question #: 35
Topic #: 6
[All Terraform-Associate-003 Questions]

Which argument can you use to prevent unexpected updates to a module's configuration when calling Terraform Registry modules?

Show Suggested Answer Hide Answer
Suggested Answer: C

Comprehensive and Detailed in-Depth

The version argument in a module ensures Terraform uses a specific version of a module, preventing unintended updates.

A (source) -- Specifies the module source but does not control versioning.

B (count) -- Controls how many instances of a resource/module exist, not updates.

D (lifecycle) -- Controls how resources behave but does not control module versioning.

Official Terraform Documentation Reference:


by Alesia at Mar 19, 2025, 01:18 PM

Limited Time Offer

25%

Off

Get Premium Terraform-Associate-003 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Maurine
2 months ago
Ah, the age-old question of keeping your infrastructure on a leash. Clearly, the answer is to use the 'do-not-touch-this-or-else' option. Good luck, everyone!
upvoted 0 times
Vanda
12 days ago
Always check the module documentation for any specific configuration options.
upvoted 0 times
...
Kris
13 days ago
You can use the 'constraints' argument to specify version constraints.
upvoted 0 times
...
Aretha
23 days ago
Set the 'version' argument to a specific version to prevent unexpected updates.
upvoted 0 times
...
Buddy
27 days ago
Use the 'source' argument to pin the module to a specific version.
upvoted 0 times
...
...
Rodrigo
2 months ago
B) count? Really? I'm pretty sure that's just for duplicating resources, not locking down versions. Rookie mistake!
upvoted 0 times
...
Cruz
2 months ago
A) source, because that's where the magic happens! Or, you know, the potential disaster, depending on how you look at it.
upvoted 0 times
...
Lisbeth
2 months ago
D) lifecycle is the answer. Gotta keep that configuration locked down tight, no room for shenanigans here!
upvoted 0 times
Valentin
19 days ago
That's right, setting the lifecycle configuration can help maintain control over changes to module configurations.
upvoted 0 times
...
Laura
25 days ago
Exactly, using the lifecycle argument in Terraform can help prevent unexpected updates to module configurations.
upvoted 0 times
...
...
Kattie
2 months ago
C) version is the way to go. Don't want any surprises when your infrastructure decides to update itself without your permission!
upvoted 0 times
...
Sheridan
2 months ago
Because the lifecycle argument allows you to control when resources are created, updated, or deleted.
upvoted 0 times
...
Merissa
2 months ago
Why do you think it's lifecycle?
upvoted 0 times
...
Sheridan
2 months ago
I disagree, I believe it's D) lifecycle.
upvoted 0 times
...
Merissa
2 months ago
I think the answer is C) version.
upvoted 0 times
...

Save Cancel
a