Common Pitfalls to Avoid
-
ARM Templates vs Scripts
-
ARM Template = declarative, idempotent (same result every time).
-
CLI/PowerShell = imperative, step-by-step.
-
Exam trap: If requirement says “consistent infra deployments” → ARM Template, not script.
-
-
Automation Accounts vs Pipelines
-
Automation Account (Runbooks) = ops tasks (VM start/stop, patching).
-
DevOps Pipelines / GitHub Actions = CI/CD for apps and infra.
-
Exam trap: “Shut down VMs nightly” → Runbook, not Pipeline.
-
-
CLI vs PowerShell
-
CLI = cross-platform, lightweight, good for devs.
-
PowerShell = rich automation, great for Windows admins.
-
Exam trap: “Which tool is best for cross-platform automation?” → CLI.
-
-
GitHub Actions vs Azure DevOps
-
GitHub Actions = simple, repo-driven automation.
-
DevOps Pipelines = enterprise-grade with approvals & multi-stage workflows.
-
Exam trap: “Which supports complex approval workflows?” → Azure DevOps.
-
Quick Recall Hacks
-
“Infra as Code in JSON” → ARM Templates
-
“Stop/start VMs on a schedule” → Automation Account Runbook
-
“Cross-platform CLI” → Azure CLI
-
“Windows-friendly scripting” → PowerShell
-
“Push to repo → auto-deploy app” → GitHub Actions
-
“Multi-stage enterprise pipeline” → Azure DevOps Pipelines
What to Expect in the Exam
-
At least one ARM Template question (parameters, idempotency).
-
One or two Runbook automation scenarios (stop/start VMs, patching).
-
Questions comparing CLI vs PowerShell.
-
A scenario around CI/CD pipelines (GitHub vs DevOps).
-
Trick questions mixing Runbooks and CI/CD.
Final Exam Strategy
-
Identify whether the task is deployment (ARM Template, CI/CD) or operations (Runbooks).
-
Look for platform cues: cross-platform (CLI), Windows admin (PowerShell).
-
If automation requires repeatable infra, answer is ARM Template.
-
If it involves cost savings via schedules, answer is Runbook.
-
If it’s about app deployment tied to code commits, pick CI/CD pipeline.