TA-003 Question 62

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A1

  The option that cannot be used to keep secrets out of Terraform configuration files is: A. A Terraform provider Explanation of Options: A. A Terraform provider: Providers are used to interact with cloud services and resources but do not inherently provide a mechanism for managing secrets or sensitive data. B. Environment variables: You can use environment variables to store sensitive information, which can then be referenced in your Terraform configuration without hardcoding them in the files. C. A -var flag: The -var flag allows you to pass variables to Terraform at runtime, which can be used to provide sensitive data without including it in the configuration files. D. Secure string: While not a standard term in Terraform, if referring to secure storage mechanisms (like AWS Secrets Manager or Azure Key Vault), these can be used to manage secrets outside of Terraform configuration files.

• Chose A1

  The correct answer is: A. A Terraform provider Explanation: Terraform providers are used to interact with external APIs and services (e.g., AWS, Azure, Google Cloud), but they are not designed to manage secrets or keep them out of configuration files. The other options, however, are valid ways to keep secrets secure.

• 1

  A. A Terraform provider A Terraform provider is not typically used to keep secrets out of Terraform configuration files. Instead, environment variables, the -var flag, and secure strings are common methods used to manage secrets securely in Terraform.