nerdexam
Microsoft

AZ-400 · Question #421

Drag and Drop Question You have a GitHub repository named repo1 that stores the code of an app named App1. You need deploy a workflow for repo1 by using GitHub Actions. The solution must meet the foll

The correct answer is releases/**; release*; src/**; **/*.md. The correct arrangement uses 'releases/*' to match branches with the 'releases/' prefix (the double wildcard matches any characters after the slash), 'release' as the branch exclusion or additional pattern for push triggers, 'src/*' to recursively scan all files in subdirectories

Submitted by sofia.br· Mar 6, 2026Implement and manage build and release pipelines using GitHub Actions, including configuring workflow triggers, path filters, and branch patterns

Question

Drag and Drop Question You have a GitHub repository named repo1 that stores the code of an app named App1. You need deploy a workflow for repo1 by using GitHub Actions. The solution must meet the following requirements: - Scan on pushes to the main branch. - Scan on pull requests to the main branch. - Scan on pull requests to any branch that has a prefix of releases/. - Scan all the files in the subdirectories of the src directory. - Exclude scanning of markdown files. How should you complete the code? To answer, drag the appropriate values to the correct targets. Each value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:

Exhibit

AZ-400 question #421 exhibit

Answer Area

Drag items

**/*.md*.mdrelease*releases/**src/*src/**

Correct arrangement

  • releases/**
  • release*
  • src/**
  • **/*.md

Explanation

The correct arrangement uses 'releases/' to match branches with the 'releases/' prefix (the double wildcard matches any characters after the slash), 'release*' as the branch exclusion or additional pattern for push triggers, 'src/' to recursively scan all files in subdirectories of the src directory (single * would only match one level deep), and '/*.md' to exclude markdown files anywhere in the repository (the double wildcard matches across directory boundaries). In GitHub Actions workflow syntax, 'src/' correctly captures all nested subdirectories and files under src, while '**/*.md' properly matches markdown files in any directory depth.

Topics

#GitHub Actions#CI/CD Workflows#YAML Configuration#Branch Protection

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-400 Practice