Free Practice Questions for HashiCorp Terraform Authoring and Operations Professional Certification

This subdomain covers initializing a Terraform configuration using the `init` command and its various options.

- Initialization overview - init CLI command

This subdomain covers generating and reviewing execution plans with the `plan` command to preview changes before applying them.

- plan CLI command

This subdomain covers applying configuration changes to create, update, or delete infrastructure resources using the `apply` command.

- apply CLI command

This subdomain covers destroying Terraform-managed infrastructure using the `destroy` command and its options.

- destroy CLI command

This subdomain covers advanced state management tasks, including importing existing resources into Terraform state, moving resources within the state, and reconciling differences between configuration and the real-world infrastructure.

- State overview - import blocks - moved blocks - CLI documentation

This subdomain covers using HCL features to ensure configuration is valid and adheres to requirements. This includes writing tests and checks, defining input variables with type constraints, and implementing custom validation conditions.

- Tests - Checks - Input variables - Type constraints - Custom conditions

This subdomain covers using data sources to fetch information from provider APIs, allowing configurations to be more dynamic and reference existing infrastructure.

- Data sources

This subdomain covers using built-in HCL functions to transform and combine data, enabling complex logic and dynamic value generation within the configuration.

- Functions

This subdomain covers the use of meta-arguments like `count`, `for_each`, `depends_on`, and `lifecycle` to control resource behavior and create dynamic, scalable configurations.

- Resources

This subdomain covers defining input variables to parameterize configurations and outputs to expose information. This includes working with complex data types like lists, maps, and objects.

- Variables and outputs - Types and values - Expressions

This subdomain covers strategies for handling sensitive data within Terraform configurations, including understanding how sensitive values are stored in state and integrating with external secrets management tools like HashiCorp Vault.

- Sensitive data in state

This subdomain covers best practices for ensuring consistent and predictable Terraform runs by pinning versions of the Terraform binary, providers, and modules using version constraints and the dependency lock file.

- terraform blocks - Version constraints - Dependency lock file

This subdomain covers configuring remote backends to store Terraform state, enabling collaboration among team members and providing features like state locking.

- Remote state

This subdomain covers integrating the standard Terraform workflow (init, plan, apply) into CI/CD pipelines and other automation systems, including the configuration of state locking to prevent concurrent modifications.

- Configuring state locking

This subdomain covers methods for sharing information between different Terraform configurations or workspaces, primarily using the `terraform_remote_state` and `tfe_outputs` data sources.

- The terraform_remote_state data source - tfe_outputs data source

This subdomain covers the fundamentals of creating reusable Terraform modules, following recommended patterns for module design to ensure they are flexible, composable, and maintainable.

- Modules documentation - Creating a module - Module design recommended patterns

This subdomain covers how to source and declare modules within a root configuration, passing variables to customize their behavior.

- Sourcing a module - Declaring a module

This subdomain covers the process of refactoring modules to improve their structure and functionality, as well as using version constraints to manage module updates and ensure stability.

- Refactoring modules - Version constraints

This subdomain covers the process of breaking down a monolithic Terraform configuration into smaller, reusable modules to improve organization and maintainability, using tools like `moved` blocks to manage state during the refactoring process.

- moved blocks

This subdomain covers the core concept of Terraform's plugin-based architecture, where providers act as the bridge between Terraform Core and target APIs.

- Providers

This subdomain covers the configuration of providers within a Terraform block, including setting version constraints, sourcing from alternative registries, using aliases for multiple provider configurations, and managing provider upgrades via the dependency lock file.

- Provider requirements - Provider configuration - Dependency lock file - Configuring providers in modules

This subdomain covers the various methods for authenticating providers with their respective cloud or service APIs, such as using static credentials, environment variables, or other platform-specific mechanisms.

- Provider configuration

This subdomain covers techniques for diagnosing and resolving issues related to Terraform providers, including understanding the dependency lock file and enabling debug logging.

- Dependency lock file - Debugging Terraform

This subdomain covers the workflow for executing Terraform runs within HCP Terraform, including remote operations, different run modes, and how to view and manage run history. It also includes migrating existing configurations to HCP Terraform.

- Remote operations - Viewing and managing runs - Run modes and options - Migrating to HCP Terraform

This subdomain covers the concept of workspaces in HCP Terraform as a way to manage separate environments or components, including their configuration options and access control settings.

- Workspaces documentation

This subdomain covers methods for securely managing provider credentials within HCP Terraform, using both static workspace variables and dynamic provider credentials for enhanced security.

- Workspace variables - Dynamic provider credentials

This subdomain covers the use of policy-as-code frameworks like Sentinel within HCP Terraform to enforce governance, compliance, and security rules across infrastructure deployments.

- Policy enforcement