True or False: A Terraform provisioner must be nested inside a resource configuration block.

A Terraform provisioner is designed to execute scripts or commands on a resource created by Terraform, and for it to function correctly, it must be associated with a specific resource. This is why a provisioner must be nested within a resource configuration block.

This structure allows the provisioner to have context about the resource it's managing, ensuring it runs in the correct environment and can access the necessary attributes of that resource. Provisioners work on the resources they are defined in, allowing you to configure or manage the created instances effectively after they have been provisioned.

The other possible options don't align with this fundamental structure of Terraform. For instance, stating that it is false would imply that provisioners could be defined independently, which is not accurate. Similarly, the options suggesting that nesting might be dependent on certain resource types or the version of Terraform do not hold because regardless of changes in Terraform versions or resource types, provisioners are always scoped to the resources they're intended to manage. This consistent structure reinforces the necessity of nesting provisioners within resource blocks for operational correctness.