You guys are absolutely right. C is the way to go. The remote backend is a game-changer for Terraform. No more 'who has the latest state file?' discussions. Plus, you get all the added benefits like locking and versioning. It's a no-brainer in my opinion.
Haha, can you imagine if the answer was A) In an environment variable? That would be a disaster! Just imagine trying to manage your state that way. 'Hey, did you remember to set the TF_STATE_FILE environment variable before running apply?' Yikes, no thank you.
I agree, C is the correct answer. Storing the state in the remote backend or Terraform Cloud is the way to go, especially when working on shared infrastructure. It makes collaboration and version control much easier. Plus, it keeps our local machine nice and clean, no messy state files lying around.
Hmm, this is an interesting question. I'm glad they're testing our knowledge on state management, as that's a crucial aspect of Terraform. Let's see, I think the answer is C) In the remote backend or Terraform Cloud. That's the whole point of using a remote backend, right? To store the state file somewhere secure and accessible to the team.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Sabrina
1 years agoArt
1 years agoDanica
1 years agoTerrilyn
12 months agoCharlene
12 months agoKarl
12 months agoNiesha
12 months agoDevorah
12 months agoNickie
12 months agoRoxane
12 months agoSimona
12 months agoJuan
1 years ago