Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
exam questions

Exam Terraform Associate All Questions

View all questions & answers for the Terraform Associate exam

Exam Terraform Associate topic 1 question 264 discussion

Actual exam question from HashiCorp's Terraform Associate
Question #: 264
Topic #: 1
[All Terraform Associate Questions]

Which of these is not a benefit of remote state?

  • A. Keeping unencrypted sensitive information off disk
  • B. Easily share reusable code modules
  • C. Working in a team
  • D. Delegate output to other teams
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
wh1t4k3r
Highly Voted 1 year, 4 months ago
I would appreciate comments on my thoughts: this would be a case of choose 2 right? A is also not a benefit, right?
upvoted 7 times
...
BaburTurk
Highly Voted 1 year, 2 months ago
Selected Answer: D
The answer is D. Delegate output to other teams. Remote state is a feature of Terraform that allows you to store the state of your infrastructure in a remote location. This can be beneficial for a number of reasons, including: Keeping unencrypted sensitive information off disk Easily sharing reusable code modules Working in a team Enabling version control and auditing However, remote state does not allow you to delegate output to other teams. This is because the state file contains the full state of your infrastructure, including all of the resources that have been created. If you want to delegate output to other teams, you will need to use a different mechanism, such as a configuration management tool or a messaging system.
upvoted 5 times
...
alen995454
Most Recent 10 months, 1 week ago
Selected Answer: B
Saw this on another test engine,, worded slightly different. "The Terraform State file does not contain the actual module code"
upvoted 2 times
...
uax
1 year ago
Selected Answer: B
It's B. Like another person mentioned, sharing reusable code modules is the module registry's job. https://developer.hashicorp.com/terraform/language/state/remote
upvoted 3 times
...
https://developer.hashicorp.com/terraform/language/state/remote
upvoted 2 times
...
RonZhong
1 year, 3 months ago
Selected Answer: B
Remote state wasn't made for sharing modules because that's module registry's job. :)
upvoted 5 times
...
Sima_01
1 year, 3 months ago
itssss BBBBBBB!!!!!!
upvoted 2 times
...
Rajmane
1 year, 3 months ago
Selected Answer: A
Why not A
upvoted 2 times
...
AWS_cert2023
1 year, 5 months ago
The answer B. https://developer.hashicorp.com/terraform/language/state/remote With remote state, Terraform writes the state data to a remote data store, which can then be shared between all members of a team. Remote state allows you to share output values with other configurations. For fully-featured remote backends, Terraform can also use state locking to prevent concurrent runs of Terraform against the same state.
upvoted 4 times
ShakDaddy
1 year, 3 months ago
The question states "which is NOT a benefit"
upvoted 2 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...