Free Practice Questions for HashiCorp Terraform Authoring and Operations Professional Certification

This objective covers the process of preparing a working directory for other Terraform commands.

- Initialization overview - init CLI command

This objective covers the process of creating an execution plan, which lets you preview the changes that Terraform plans to make to your infrastructure.

- plan CLI command

This objective covers the process of executing the actions proposed in a Terraform plan to create, update, or destroy infrastructure.

- apply CLI command

This objective covers the process of destroying all remote objects managed by a particular Terraform configuration.

- destroy CLI command

This objective covers the management of Terraform state, which is used to map real-world resources to your configuration, keep track of metadata, and improve performance for large infrastructures.

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

This objective covers using Terraform's built-in features to ensure that configurations are syntactically valid and conform to specified constraints and conditions.

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

This objective covers the use of data sources to fetch information from APIs or other Terraform configurations, making it available for use elsewhere in your configuration.

- Data sources

This objective covers the use of built-in functions in the HashiCorp Configuration Language (HCL) to transform and combine values within a configuration.

- Functions

This objective covers the use of meta-arguments, which change the behavior of resources, such as `count`, `for_each`, `provider`, `depends_on`, and lifecycle blocks.

- Resources

This objective covers defining input variables to parameterize configurations and using output values to expose information about the managed infrastructure, including the use of complex data types like lists, maps, and objects.

- Variables and outputs - Types and values - Expressions

This objective covers strategies for handling sensitive information like passwords, API keys, and certificates within Terraform configurations, including integration with external secrets management tools.

- Sensitive data in state

This objective covers specifying versions for Terraform, providers, and modules to ensure consistency and prevent unexpected changes across collaborative environments.

- terraform blocks - Version constraints - Dependency lock file

This objective covers the configuration of remote backends to store Terraform state, enabling collaboration and providing features like locking to prevent concurrent modifications.

- Remote state

This objective covers integrating the standard Terraform workflow (init, plan, apply) into automated CI/CD pipelines, including handling state locking in automated environments.

- Configuring state locking

This objective covers methods for sharing information between different Terraform configurations or workspaces, such as using remote state data sources.

- The terraform_remote_state data source - tfe_outputs data source

This objective covers the fundamentals of creating reusable Terraform modules to encapsulate and organize infrastructure components, following recommended design patterns.

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

This objective covers how to call a module from a root or parent module, including sourcing it from various locations like the Terraform Registry, a Git repository, or a local path.

- Sourcing a module - Declaring a module

This objective covers the process of modifying and improving existing modules while managing their versions to ensure that downstream configurations are not broken by changes.

- Refactoring modules - Version constraints

This objective covers the process of taking a monolithic Terraform configuration and breaking it down into smaller, reusable modules to improve maintainability and scalability.

- moved blocks

This objective covers the core concept of how Terraform uses providers as plugins to interact with the APIs of various services like cloud providers and SaaS platforms.

- Providers

This objective covers the detailed configuration of providers within a Terraform block, including setting version constraints, using aliases for multiple configurations of the same provider, and managing the provider dependency lock file.

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

This objective covers the various methods for authenticating Terraform providers with their respective APIs, such as using environment variables, configuration file credentials, or instance profiles.

- Provider configuration

This objective covers techniques for diagnosing and resolving issues related to Terraform providers, including debugging Terraform's execution and managing the dependency lock file.

- Dependency lock file - Debugging Terraform

This objective covers the workflow for executing Terraform runs within HCP Terraform, including remote operations, different run modes, and how to view and manage run history.

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

This objective covers the concept of workspaces in HCP Terraform as distinct environments for managing infrastructure, including their configuration and access control settings.

- Workspaces documentation

This objective covers the secure management of provider credentials within HCP Terraform, using features like workspace variables and dynamic provider credentials.

- Workspace variables - Dynamic provider credentials

This objective covers the use of policy as code frameworks, such as Sentinel, within HCP Terraform to enforce governance and compliance rules on infrastructure changes.

- Policy enforcement