Microsoft Certified: DevOps Engineer ExpertDesign and implement pipelinesMedium

A DevOps team is developing a new microservices-based application using Azure Kubernetes Service (AKS). Each microservice has its own Git repository, building its own Docker image, and deploying independently. The team wants to automate the CI/CD process for each microservice. They need to configure their Azure Pipelines such that a new build and deployment is automatically triggered ONLY when changes are pushed to the specific Git repository associated with that microservice. Which trigger configuration should they apply to each microservice's pipeline?

  1. APull request triggers to build every time a PR is created.
  2. BManual triggers, requiring developers to start deployments.
  3. CContinuous Integration (CI) triggers with path filters.
  4. DSchedule triggers to run daily for all microservices.
Show answer & explanation

Correct answer: C. Continuous Integration (CI) triggers with path filters.

Continuous Integration (CI) triggers in Azure Pipelines automatically start a pipeline whenever changes are pushed to the repository. By using path filters, you can further refine this to trigger only when changes occur within specific directories or files relevant to a microservice, ensuring that only necessary pipelines run.

Why the other options are wrong

  • A. Pull request triggers are for validating code *before* merging, not for deploying *after* merging to a branch like `main`.
  • B. Manual triggers negate automation and slow down the development feedback loop.
  • D. Scheduled triggers do not respond to code changes and would deploy unnecessarily or too late.

Continuous Integration (CI) Trigger

An Azure Pipelines trigger that automatically starts a pipeline when code changes are pushed to a specified repository and branch.

  • Automates builds and tests on every code commit.
  • Can be configured with branch and path filters.
  • Essential for rapid feedback in CI/CD workflows.

Memory trick: CI triggers filter paths for microservice harmony.

More Design and implement pipelines questions