هذا الجزء لم يُترجم بعد. أنت ترى النص الإنجليزي.
$ مستخدم عادي# بصلاحية root (أو مع sudo)
المهارات في هذا الفصل
- Terraform Associate (004) — الشهر 4–5
Know the goal of phase 3
Any environment can be built, changed and destroyed from Git — with review, tests and security scans in the pipeline.
| Item | Value |
|---|---|
| Exam | HashiCorp Terraform Associate (004), tests Terraform 1.12 + HCP Terraform |
| Format | Multiple choice, 1 hour |
| Price | about $70.50 |
| Also learn | Git, GitHub Actions, containers (Docker / Podman) |
Study with these sources
The official HashiCorp study guide is free and complete. Git and Actions are learned by doing.
| Source | Use it for |
|---|---|
| ★ Terraform Associate (004) study guide | Follow it in order |
| ★ Terraform Get Started — Azure | Build real Azure resources with code |
| Terraform: Up & Running — Yevgeniy Brikman | The best book on real Terraform work |
| ★ Pro Git (free) + Learn Git Branching | Git from basics to rebase |
| ★ GitHub Actions docs + GitHub Skills | The CI/CD for the project |
| ★ Docker — Get started | Containers before Kubernetes |
| My summaries | Terraform, Git, GitHub Actions, Containers |
Build the phase project
The staging environment of a real website (for example the company web shop) as code, with a full pipeline.
- Terraform for the Azure environment of phase 2: network, VMs or App Service, database, storage, monitoring.
- Remote state in an Azure storage account with locking; one workspace or folder per environment.
- A GitHub Actions pipeline:
fmt,validate, a security scan of the Terraform code,planon every pull request,applyafter approval. - Login to Azure with OIDC (no stored passwords), secrets only in GitHub environments.
- A container image of the app, built and scanned in the pipeline.
- Backups and monitoring included in the code.
تذكّر
The project matters more than the certificate: it shows a recruiter real, working automation.
Finish the phase
The phase is done when all of these are true.
- [ ] Terraform Associate passed.
- [ ] The staging environment can be built from zero with one pipeline run, and destroyed again.
- [ ] Every change goes through a pull request with plan output and scan results.
- [ ] The project README explains the design, the pipeline and the security choices.