When using Terraform to deploy resources into Azure, which scenarios are true regarding state files? (Choose two.)

Changes made in the Azure Cloud Console are not automatically reflected in the Terraform state file; the state file only updates when Terraform explicitly runs a refresh or apply operation.

When a resource is modified directly in the Azure Cloud Console, Terraform's state file remains stale and unaware of the out-of-band change. On the next 'terraform plan' or 'terraform apply' execution, Terraform calls the Azure provider APIs to refresh the actual resource state and compares it against the stored state, detecting the configuration drift. This drift detection behavior is a fundamental characteristic of how Terraform manages the relationship between declared configuration and real infrastructure.

The current state file is not automatically synchronized with out-of-band changes; it remains stale until Terraform actively queries the provider APIs.

Out-of-band changes in the Azure Cloud Console are not automatically reconciled into the Terraform state; a 'terraform refresh' or 'terraform apply' is required to detect and record them.