5c TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   A Terraform configuration uses the AWS provider. Which authentication method is considered a shared configuration file?

   • AThe .terraform.lock.hcl file
   • BThe provider.tf file
   • CThe terraform.tfvars file
   • DThe ~/.aws/credentials file
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   What is a key advantage of using dynamic credentials (e.g., short-lived tokens) for Terraform provider authentication?

   • AThey are automatically shared across all team members
   • BThey are easier to hardcode in configuration files
   • CThey reduce the risk of credential exposure because they expire quickly
   • DThey eliminate the need for any authentication configuration
   Reveal Solution Discussion Select an answer first
4. 13expert · medium

   A company uses Terraform with the Google Cloud provider. They have separate projects for development and production. They want to use the same Terraform configuration for both, and they want to authenticate using different service accounts. They also want to avoid storing service account keys in the repository. Which approach should they use?

   • AUse Terraform workspaces and set the credentials in the workspace's variables
   • BUse the `gcloud` CLI and set the active account per environment
   • CUse the `GOOGLE_APPLICATION_CREDENTIALS` environment variable set differently in each environment
   • DUse a single service account that has access to both projects
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   When using workspaces to manage multiple environments, how can you provide environment-specific provider credentials?

   • ABy referencing workspace-specific variable values that contain the credentials
   • BBy using a single set of credentials for all workspaces
   • CBy creating a separate provider block for each workspace in the same configuration
   • DBy hardcoding different credentials in the provider block for each workspace
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A company uses Terraform with the Azure provider. They have a policy that all infrastructure changes must be made using managed identities, and no service principal secrets should be stored in code or configuration. They run Terraform in an Azure DevOps pipeline. How should they authenticate the Azure provider?

   • AUse a service principal certificate stored in the pipeline
   • BUse environment variables for the service principal credentials
   • CUse a service principal with a client secret stored as a pipeline variable
   • DUse the Azure CLI task in the pipeline to log in, and then run Terraform
   Reveal Solution Discussion Select an answer first