A Terraform provider is not responsible for:

A Terraform provider is not responsible for:

• A. Understanding API interactions with some service
• B. Exposing resources and data sources based on an API
• C. Provisioning infrastructure in multiple clouds
• D. Managing actions to take based on resource differences

Answer: (C)

A Terraform provider is designed to talk to a single service’s API, expose the resources and data sources that map to that API, and implement the create/read/update/delete actions along with how to apply diffs during planning. It handles the lifecycle for that one service and reconciles state for resources from that API. Provisioning infrastructure across multiple clouds isn’t the provider’s job by itself. To manage more than one cloud, you combine multiple providers in a single configuration—each provider handles its own cloud’s API, and Terraform coordinates across them. So, while you can provision across clouds, that capability comes from using multiple providers, not from a single provider. That’s why this option is the correct choice.

A Terraform provider is designed to talk to a single service’s API, expose the resources and data sources that map to that API, and implement the create/read/update/delete actions along with how to apply diffs during planning. It handles the lifecycle for that one service and reconciles state for resources from that API.

Provisioning infrastructure across multiple clouds isn’t the provider’s job by itself. To manage more than one cloud, you combine multiple providers in a single configuration—each provider handles its own cloud’s API, and Terraform coordinates across them. So, while you can provision across clouds, that capability comes from using multiple providers, not from a single provider. That’s why this option is the correct choice.