6c TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   When troubleshooting a provider credential issue in HCP Terraform, what is the first step to verify that the credentials are correctly set?

   • AReview the Terraform configuration files in the repository for hardcoded credentials
   • BContact the cloud provider's support team
   • CCheck the run logs for the credential values
   • DCheck the workspace's Variables section to confirm the sensitive variables are defined and have the correct values
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   In HCP Terraform, how can you configure provider credentials using environment variables within a variable set?

   • ABy defining variables with names like 'AWS_ACCESS_KEY_ID' and marking them as environment variables in the variable set
   • BBy creating a .env file in the workspace and uploading it via the UI
   • CBy using the HCP Terraform CLI to export the variables to the remote backend
   • DBy adding the credentials to the provider block in the configuration and pushing to the repository
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   Which statement accurately describes the supported providers for storing credentials as sensitive variables in HCP Terraform?

   • AA broad set of commonly used providers (e.g., AWS, Azure, Google Cloud) are supported, and credentials are stored as sensitive variables
   • BAll providers listed in the Terraform Registry are automatically supported without any configuration
   • COnly providers that support OAuth2 authentication are supported for credential storage
   • DOnly HashiCorp's own providers (e.g., Vault, Consul) are supported for credential storage
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A Terraform run in HCP Terraform fails with an error that the Azure provider cannot authenticate. The workspace has the correct variables defined, and the variable set is applied. What is the most likely cause of this issue?

   • AThe variables are marked as sensitive, which prevents the provider from reading them.
   • BThe Azure provider is not defined in the Terraform configuration.
   • CThe variable names do not match the expected environment variable names for the Azure provider.
   • DThe workspace is using a different Terraform version that does not support Azure.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   Your team uses HCP Terraform to manage infrastructure in multiple AWS accounts. Each workspace needs different credentials. You want to avoid duplicating the variable definitions in each workspace and instead manage them centrally. What is the best approach?

   • ACreate a separate variable set for each AWS account and apply it to the corresponding workspaces.
   • BStore the credentials in the Terraform configuration using a map variable.
   • CUse the same variable names in all workspaces but with different values.
   • DCreate a single variable set with all credentials and apply it to all workspaces.
   Reveal Solution Discussion Select an answer first