Day 29 of My 30-Day Terraform Challenge
Day 29 of my 30-Day Terraform Challenge was focused on measuring how ready I am for the Terraform Associate certification exam. I completed two more full practice exams under timed conditions and compared the results with yesterday's scores to identify my remaining weak areas.
Practice Exam Progress
Here is the score trend across all four exams:
| Exam | Score | Percentage |
|---|---|---|
| Exam 1 | 41/57 | 72% |
| Exam 2 | 46/57 | 81% |
| Exam 3 | 47/57 | 82% |
| Exam 4 | 49/57 | 86% |
The results showed steady improvement in both speed and accuracy. Scoring above the passing mark in all four exams gave me confidence that my understanding is improving, but it also highlighted a few areas where I still need review.
Persistent Weak Areas
After reviewing the wrong answers across all four exams, I found that the same topics kept appearing:
- Terraform state management
- Terraform import
- Workspace behavior
- Provider version constraints
One of the most common mistakes was confusing terraform state rm with terraform destroy. I now understand that terraform state rm only removes the resource from Terraform state tracking, while terraform destroy removes the actual infrastructure resource.
I also clarified that terraform import adds resources to the state file but does not create the Terraform configuration, which means terraform plan may still show changes after importing.
Hands-On Revision
To strengthen those weak areas, I practiced the commands directly:
bash
terraform state list
terraform state show random_id.test
terraform state rm random_id.test
terraform workspace new dev
terraform workspace list
terraform workspace show
Top comments (0)