Which option cannot be used to keep secrets out of Terraform configuration files?

The correct answer is D. secure string. A secure string is not a valid option to keep secrets out of Terraform configuration files. A secure string is a feature of AWS Systems Manager Parameter Store that allows you to store sensitive data encrypted with a KMS key. However, Terraform does not support secure strings…

Read, generate, and modify configuration

Question

Options

AA Terraform provider
BEnvironment variables
CA -var flag
Dsecure string

How the community answered

(15 responses)

A
7% (1)
B
7% (1)
C
13% (2)
D
73% (11)

Explanation

A secure string is not a valid option to keep secrets out of Terraform configuration files. A secure string is a feature of AWS Systems Manager Parameter Store that allows you to store sensitive data encrypted with a KMS key. However, Terraform does not support secure strings natively and requires a custom data source to retrieve them. The other options are valid ways to keep secrets out of Terraform configuration files. A Terraform provider can expose secrets as data sources that can be referenced in the configuration. Environment variables can be used to set values for input variables that contain secrets. A -var flag can be used to pass values for input variables that contain secrets from the command line or a file.

Topics

#secrets management#sensitive data#environment variables#variable inputs

Community Discussion

No community discussion yet for this question.

Full TERRAFORM-ASSOCIATE-003 Practice