BrainyBeeBrainyBee
ExploreBlogStart Studying
HomeDesigning and Implementing Microsoft DevOps Solutions (AZ-400)Design and implement pipelines — cram sheet
Cram Sheet397 words

Design and implement pipelines — cram sheet

Topic 3.3 — Design and implement pipelines · cram sheet

The two defaults everyone gets wrong

LevelDefault orderChange with
JobsParalleldependsOn: <job>
StagesSequentialdependsOn: []

Triggers

  • Unconfigured = ON: CI on all branches, PR on all branches.
  • trigger: none · pr: none to disable.
  • exclude beats include.
  • batch: true — collect commits during a run.
  • Scheduled always: false (default) skips when nothing changed. Cron is UTC.
  • YAML says none but it still fires → a UI setting is overriding the YAML.

Agents

  • Microsoft-hosted: Services only, concurrency billing, clean VM every run.
  • GitHub-hosted for Pipelines: per-minute billing.
  • Self-hosted: caches persist · private network · custom software · you own patching.
  • Elastic: VMSS agents → Managed DevOps Pools is the current recommendation.
  • Hybrid: the agent connects outbound; no inbound ports.

Deployment jobs

  • Strategies: runOnce, rolling, canary. Blue-green and ring are patterns, not keywords.
  • rolling is VM-only; hooks fire per batch (maxParallel).
  • Hook order: preDeploy → deploy → routeTraffic → postRouteTraffic → on:.

Reuse

  • Task groups are NOT supported in YAML — classic only. Use templates.
  • template: composes · extends: constrains.
  • Parameter types: string, object, stepList, jobList, stageList.
  • Variable groups: secret variables are protected resources; non-secret are not.
  • Variable groups can link to Azure Key Vault.

Checks and approvals

Order: Static → Pre-check approvals → Dynamic → Post-check approvals → Exclusive lock

  • Defined by the resource owner, not the pipeline author.
  • Static: Branch control · Required template · Evaluate artifact.
  • Dynamic: Approval · Azure Function · REST API · Business Hours · Query Azure Monitor alerts.
  • Within a category: creation order. Timeout → stage does not execute.

Conditions

succeeded() (implicit) · failed() · always() · canceled() · succeededOrFailed()

  • A custom condition replaces succeeded().
  • Only always() survives cancellation.

GitHub integration

  • GitHub App recommended — runs as the Azure Pipelines identity, works with GitHub Checks.
  • OAuth runs as your personal identity.
  • Installing for all repos → token reaches all repos, private included.
  • Fork PRs do build; secrets are withheld by default.

Matrix

  • parallel and matrix are mutually exclusive.
  • maxParallel is only valid with matrix.
All Designing and Implementing Microsoft DevOps Solutions (AZ-400) Study Resources

Related Notes

  • Agent and runner infrastructure421 words
  • Agent and runner infrastructure — quick notes150 words
  • Alerting on pipeline events255 words
  • Alerting on pipeline events — quick notes94 words
  • Analyzing usage and application performance241 words
  • Analyzing usage and application performance — quick notes73 words
  • Appropriate access levels217 words
  • Appropriate access levels — quick notes85 words
  • Automating container scanning277 words
  • Automating container scanning — quick notes96 words
  • Automating documentation from Git history191 words
  • Automating documentation from Git history — quick notes55 words

Ready to study Designing and Implementing Microsoft DevOps Solutions (AZ-400)?

Practice tests, flashcards, and all study notes — free, no sign-up.

Start Studying

Ready to study Designing and Implementing Microsoft DevOps Solutions (AZ-400)?

Practice tests, flashcards, and all study notes — free, no sign-up needed.

Start Studying — Free
Designing and Implementing Microsoft DevOps Solutions (AZ-400) ResourcesExplore All HivesBlogHome

© 2026 BrainyBee. Free AI-powered exam prep.