Detailed Explanation:
* Rationale for Correct Answers:
* C. terraform.tfvars securely managed: Acceptable if distributed securely outside version control.
* D. HCP Terraform/Terraform Cloud sensitive variables: Official best practice for team-based workflows.
* E. Vault: HashiCorp Vault is designed for secret management and integrates well with Terraform.
* Analysis of Incorrect Options:
* A: Storing plaintext secrets on shared drives is insecure.
* B: Checking secrets into version control is a major security risk.
* Key Concept:Sensitive values should be managed securely in Vault, HCP Terraform, or securely shared
.tfvars files - never in plaintext or version control.
Reference:Terraform Exam Objective - Use Terraform to Manage Infrastructure.

Detailed Explanation:
* Rationale for Correct Answer (D):The Terraform Registry provides documentation for published modules, including:
* Required inputs (variables you must supply).
* Optional inputs with defaults (so you know what you can override).
* Outputs (what values the module returns for use elsewhere).
Therefore, the correct answer is all of the above.
* Analysis of Incorrect Options:
* A. Required inputs only: Incomplete.
* B. Outputs only: Incomplete.
* C. Optional inputs only: Incomplete.
* D. All of the above: Correct because the Registry provides all relevant documentation.
* Key Concept:Terraform Registry modules include inputs, outputs, and usage details, enabling reusability and modular design.
Reference:Terraform Exam Objective - Interact with Terraform Modules.

Variables declared within a module are only accessible within that module, unless they are explicitly exposed as output values1.

Theversion argumentin a module ensures Terraform uses aspecific versionof a module, preventing unintended updates.
A (source)- Specifies the module source butdoes not control versioning.
B (count)- Controls how many instances of a resource/module exist,not updates.
D (lifecycle)- Controls how resources behavebut does not control module versioning.
Official Terraform Documentation Reference:
Module Version Constraints

Detailed Explanation:
* Rationale for Correct Answer (C):Best practice is to avoid hardcoding sensitive credentials in Terraform configurations or storing them in version control. Instead, credentials should be managed via environment variables, CLI authentication helpers, or secret managers (e.g., Vault).
* Analysis of Incorrect Options:
* A. Shared server: Not secure, introduces single point of failure and risk.
* B. Storing credentials in config files: A major security risk, especially if pushed to version control.
* D. None of the above: Incorrect, because option C is a valid and recommended approach.
* Key Concept:Security best practices in Terraform dictate that credentials should be externalized from Terraform code.
Reference:Terraform Exam Objective - Navigate Terraform State and Backends.