When does terraform apply reflect changes in the cloud environment?

Changes are rarely `Immediately` reflected in cloud environments as provisioning operations typically involve network latency and processing time by the cloud provider.

While changes are reflected after the resource provider fulfills the request, this option can be considered insufficient because Terraform often waits for resources to reach a stable, desired state, which might be a longer process than just the initial request fulfillment.

The state file is updated *after* Terraform has confirmed the changes are reflected and stable in the cloud environment, not as the trigger for the changes themselves.

The `-refresh` command-line argument causes Terraform to re-read the current state of resources from the cloud, but it does not directly cause or reflect *changes* initiated by `terraform apply` in the cloud.

None of the provided options accurately or fully capture when `terraform apply` reflects changes in the cloud environment, as it depends on the asynchronous completion of actions by the cloud provider, which can involve waiting for resources to transition to a desired stable state beyond mere immediate fulfillment.