Terraform provisioners can be added to any resource block.

Terraform provisioners can be added to any resource block.

• A. False
• B. True
• C. Only for local resources
• D. Depends on the resource type

Answer: (B)

Provisioners run as part of a resource’s lifecycle and are defined inside the resource block. They can be attached to any resource type Terraform manages, so you can use local-exec, remote-exec, or file provisioners to perform post-creation tasks on that resource. Because they're associated with the resource block itself, the statement that you can add a provisioner to any resource block is true. They typically run after the resource is created (and optionally on destroy if configured), which makes them useful for bootstrapping the instance or pushing configuration. Remember that while handy, provisioners can make plans less predictable and are generally discouraged for core configuration compared to baked images or separate configuration management, but they still work across resource types.

Provisioners run as part of a resource’s lifecycle and are defined inside the resource block. They can be attached to any resource type Terraform manages, so you can use local-exec, remote-exec, or file provisioners to perform post-creation tasks on that resource. Because they're associated with the resource block itself, the statement that you can add a provisioner to any resource block is true. They typically run after the resource is created (and optionally on destroy if configured), which makes them useful for bootstrapping the instance or pushing configuration. Remember that while handy, provisioners can make plans less predictable and are generally discouraged for core configuration compared to baked images or separate configuration management, but they still work across resource types.