The terraform.tfstate file always matches your currently built infrastructure.
The terraform.tfstate file always matches your currently built infrastructure.
The terraform.tfstate file does not always match your currently built infrastructure. This is because changes can be made to the infrastructure outside of Terraform, leading to a drift between the actual state and the state recorded in terraform.tfstate. Additionally, the state file represents the last known state from when Terraform was last run. If any changes are made outside of Terraform, they won't be reflected until a refresh or a new plan is run to update the state file.
It doesn't necessarily always matches the current infrastructure, since one can manually change resources and therefore drift from the state configuration. Terraform has no way to know or track changes made outside of it.
Incorrect,your next terraform plan or terraform refresh will inform you that there is change(provided the deployment was initially done via terraform). tfstate reflects values from actual infrastructure deployed, and it picks drift from actual tf files.
Incorrect, question does not mention about "your so called " terraform plan or refresh commands
Incorrect, question does not mention about "your so called " terraform plan or refresh commands
what if we create the resources manually from Cloud provider. It will not match state file right. If the question Specifically mention infra created by Terraform then it is true
B is correct
B is correct
B is correct answer : false.
B IS CORRECT
Not necessarily
No it doesn't. This is because; terraform doesn't necessarily reconcile infrastructure automatically. It is only after you run a terraform command like terraform plan does it reconcile your actual state with your desired state.
should be A
should be A
What happens if you change you resources through the cloud portal? Until you run a terraform plan/apply the tfstate.tf file will be out of sync with live changes. Answer should be B : false.
This is the one of 2 edge cases that makes me want to choose False. Surprised other comments saying terraform will not pick up drift-tfstate does reflect the drift post a terraform plan/terraform refresh. Other being config itself being done outside terraform-those items will not be tracked.
This is the one of 2 edge cases that makes me want to choose False. Surprised other comments saying terraform will not pick up drift-tfstate does reflect the drift post a terraform plan/terraform refresh. Other being config itself being done outside terraform-those items will not be tracked.
Should be A
in what case ?
ah "always" mb
B is the correct answer.
Definitely B
B is the right.
Not always
B is correct
No because you can configure outside the tfstate file
B TEST
Answer - False, because state file doesn't matches the current infrastructure unwantedly.
Question is a bit ambiguous-technically tfstate file reflects any deployments done VIA TERRAFORM. Even if manual changes were made to a deployment done by terraform,a terraform refresh would actually update the tfstate file to reflect actual infrastructure.(this lets terraform know that there is a mismatch betweeh tfstate and actual tf file).
After deployment, we can change change configuration by manual. So terraform.tfstate may be different with current infra. B is correct
B is the correct answer
B is the correct answer
B. False
Question is a bit ambiguous.it says currently built, does it mean to say right after Terraform apply? Anyways feel like B is the answer
The actual provisioned resources may drift, the state represents a snapshot of their status from *the last time* Terraform was run.
Of course, it's B. For example, when you perform tasks in the AWS web console, you cannot see the .tfstate file. Additionally, if we add that, you can update it to the latest state through 'tf refresh.
B is the correct
The terraform.tfstate file maintains the state of your infrastructure as managed by Terraform. It keeps track of the resources that Terraform has provisioned and their current state.
Selected Answer: B
B. False The terraform.tfstate file reflects the infrastructure as it was last known to Terraform, but changes made outside of Terraform (manually or through other tools) may not be reflected in the state file until a terraform refresh or terraform plan is run to reconcile the differences.
The terraform.tfstate file reflects Terraform's understanding of the infrastructure, but it may not always match the actual state of the infrastructure if changes have been made manually (outside of Terraform) or if the state file hasn't been updated after such changes. In those cases, the state file would be outdated or inaccurate.
The correct answer is false because Terraform performs a refresh operation before any operation to update the state with the real infrastructure. This means the state file might not always perfectly match the current infrastructure if there are discrepancies between the state and the actual resources.
ITS B. YOUR INFRA COULD BE CHANGE
Agree with others that it is B
Answer is B
Answer is B : Terraform has no way to know or track changes made outside of it.