1c Explain How Terraform Manages Multi-Cloud, Hybrid Cloud, and Service-Agnostic Workflows TERRAFORM-ASSOCIATE-004 Practice Questions (Page 3)

Questions 11–13

1. 11application · medium

   An organization runs a legacy application on VMware in its on-premises data center and wants to extend capacity to Azure for burst workloads. The network team has established a VPN connection between the data center and Azure. The infrastructure team wants to manage both on-premises and cloud resources with Terraform. What is the most appropriate approach?

   • AManage on-premises resources with a configuration management tool and Azure with Terraform.
   • BExport the on-premises configuration to Azure Resource Manager templates and manage everything with the azurerm provider.
   • CUse the vSphere provider for on-premises resources and the azurerm provider for Azure resources in the same Terraform configuration.
   • DUse the azurerm provider for both on-premises and Azure resources by treating the VPN as a virtual network.
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A startup uses Terraform to provision resources on AWS, but is considering adding Google Cloud Platform (GCP) for a new project. They want to reuse their existing Terraform modules and workflow as much as possible. What is the primary benefit of Terraform's provider-based architecture in this scenario?

   • AIt allows the same module to be used for both AWS and GCP without any changes.
   • BIt eliminates the need to learn GCP-specific resource types and arguments.
   • CIt abstracts cloud-specific APIs, so the team can use the same Terraform workflow and language to manage resources on both clouds.
   • DIt automatically migrates existing AWS resources to GCP.
   Reveal Solution Discussion Select an answer first
3. 13foundation · easy

   How does Terraform's provider-based architecture support service-agnostic workflows?

   • AIt eliminates the need to understand the service's specific configuration options.
   • BIt automatically converts cloud-specific configurations into a universal format.
   • CIt abstracts the underlying API differences so you use the same workflow to manage diverse services.
   • DIt allows the same configuration to be used for any service without modification.
   Reveal Solution Discussion Select an answer first