-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Added coming soon page for TF PRO * Added exam to JSON file New copy for the pro exam, small edits to the FAQ slug * Changed title Added the coming soon to make it clear it was not GA * Added coming soon page for TF PRO * Added exam to JSON file New copy for the pro exam, small edits to the FAQ slug * Changed title Added the coming soon to make it clear it was not GA * Added coming soon page for TF PRO * Added exam to JSON file New copy for the pro exam, small edits to the FAQ slug * Changed title Added the coming soon to make it clear it was not GA * Delete non markdown version commiting to bridgets branch to see if it will give us a varcell preview * missing comma in infrastructure-automation.json * more human readable tables but no actual change meant just to trigger a new build * Update settings.json * Copyedits * Removed extra .md file * Changed separate objctive tables into one large table * Removed exclamation point from coming soon and changed ordering of langauge * Added alt text * comma add * Update src/content/certifications/exam-faqs/terraform-authoring-operations-professional.mdx Co-authored-by: Brian McClain <[email protected]> * Update src/content/certifications/exam-faqs/terraform-authoring-operations-professional.mdx Co-authored-by: Brian McClain <[email protected]> * Update src/content/certifications/exam-faqs/terraform-authoring-operations-professional.mdx Co-authored-by: Brian McClain <[email protected]> * Update src/content/certifications/programs/infrastructure-automation.json Co-authored-by: Brian McClain <[email protected]> * Update settings.json * Update settings.json * small change to kick off tests * Update infrastructure-automation.json removed trailing comma --------- Co-authored-by: Lisa Szpunar <[email protected]> Co-authored-by: Brian McClain <[email protected]>
- Loading branch information
1 parent
74558e3
commit 6e22d61
Showing
2 changed files
with
102 additions
and
3 deletions.
There are no files selected for viewing
88 changes: 88 additions & 0 deletions
88
...ontent/certifications/exam-faqs/terraform-authoring-operations-professional.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
<!-- Each "## Heading Two" section in this document will be used to populate an FAQ item --> | ||
|
||
## Exam Availability | ||
|
||
Coming soon! | ||
|
||
## Prerequisites | ||
|
||
We strongly recommend that you pass the associate-level Terraform exam before taking the professional-level exam. The professional-level exam is intended for practitioners who have extensive experience with Terraform in a production environment, and understand the concepts covered in the associate exam. | ||
|
||
- HashiCorp Certified: Terraform Associate Certification (recommended) | ||
- Linux skills such as the ability to list and edit files via command terminal | ||
- Experience working with a cloud provider (AWS, GCP, Azure) and experience with cloud credentials | ||
- Familiarity with YAML, JSON, HCL, and CSV formats | ||
- Understanding of the networking stack and networking protocols, including TCP/IP and UDP | ||
|
||
<ThemedImage | ||
lightSrc="https://www.datocms-assets.com/2885/1707512269-terraform_pro_prereq_lt.png" | ||
darkSrc="https://www.datocms-assets.com/2885/1707512261-terraform_pro_prereq_dt.png" | ||
alt="an associate badge on the left with an arrow pointing to a professional badge on the right" | ||
width="515" | ||
height="279" | ||
/> | ||
|
||
## Exam Details | ||
|
||
| | | | ||
| ------------------- | ----------------------------- | | ||
| **Assessment Type** | Lab-based and multiple choice | | ||
| **Format** | Online proctored | | ||
| **Language** | English | | ||
| **Expiration** | 2 years | | ||
|
||
## Exam Objectives | ||
|
||
Exam objectives are subject to change without prior notice before the launch of the exam. Please check back frequently to ensure you have the latest information. | ||
|
||
| | | | ||
| ----- | --------------------------------------------------------------------------------------------------- | | ||
| **1** | **Manage resource lifecycle** | | ||
| 1a | Initialize a configuration using `terraform init` and its options | | ||
| 1b | Generate an execution plan using `terraform plan` and its options | | ||
| 1c | Apply configuration changes using `terraform apply` and its options | | ||
| 1d | Destroy resources using `terraform destroy` and its options | | ||
| 1e | Manage resource state, including importing resources and reconciling resource drift | | ||
| **2** | **Develop and troubleshoot dynamic configuration** | | ||
| 2a | Use language features to validate configuration | | ||
| 2b | Query providers using data sources | | ||
| 2c | Compute and interpolate data using HCL functions | | ||
| 2d | Use meta-arguments in configuration | | ||
| 2e | Configure input variables and outputs, including complex types | | ||
| 2f | Analyze best practices for managing sensitive data, such as using Vault for secrets management | | ||
| **3** | **Develop collaborative Terraform workflows** | | ||
| 3a | Manage the Terraform binary, providers, and modules using version constraints | | ||
| 3b | Configure remote state | | ||
| 3c | Use the Terraform workflow in automation | | ||
| 3d | Share data across configurations and workspaces | | ||
| **4** | **Create, maintain, and use Terraform modules** | | ||
| 4a | Create a module | | ||
| 4b | Use a module in configuration | | ||
| 4c | Refactor a module and use module versioning | | ||
| 4d | Refactor an existing configuration into modules | | ||
| **5** | **Configure and use Terraform providers** | | ||
| 5a | Understand Terraform's plugin-based architecture | | ||
| 5b | Configure providers, including aliasing, versioning, sourcing, and managing upgrades | | ||
| 5c | Manage provider authentication | | ||
| 5d | Troubleshoot provider errors | | ||
| **6** | **Collaborate on infrastructure as code using Terraform Cloud** | | ||
| 6a | Analyze the Terraform Cloud run workflow | | ||
| 6b | Understand Terraform Cloud workspaces and their configuration options, including access management | | ||
| 6c | Manage provider credentials in Terraform Cloud | | ||
| 6d | Analyze policy as code and governance features | | ||
|
||
## Lab-based Exam | ||
|
||
This performance-based exam contains labs that must be completed in a virtual environment along with a shorter multiple-choice section. During the lab scenarios, you will be tested on performing real-world Terraform tasks using the command line, cloud providers' (AWS, GCP, or Azure) UI, and text editors. You will have access to Terraform documentation, cloud provider documentation, and limited Registry access. | ||
|
||
## Requirements for Attending an Exam | ||
|
||
Visit the [Exam-taker Handbook](https://hashicorp-certifications.zendesk.com/hc/en-us/articles/360048211571) to learn about the requirements and policies for taking exams. | ||
|
||
## Renewing Your Certification | ||
|
||
To renew your Terraform Professional certification, you will need to take and pass the Terraform Authoring and Operations Professional exam. | ||
|
||
**If you hold an _unexpired_ Terraform Professional certification:** You can take the exam again starting 18 months after your previous exam date. When you pass the exam, the expiration date on your credentials will be extended. | ||
|
||
**If you hold an _expired_ Terraform Professional certification:** You are eligible to recertify at any time. When you pass the exam again, you will receive a new, separate set of credentials with a new expiration date. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters