A team adds a coordination workflow after several Copilot coding agent pull requests changed the same deployment files. The team wants to detect conflicts, publish evidence, and block merge when degraded coordination is detected. Evaluate the following statements. 1. The concurrency group prevents duplicate coordination runs for the same pull request. 2. The concurrency group coordinates conflicts across different pull requests. 3. The artifact step can preserve evidence after a failed overlap check.
name: agent-coordination-check
on:
pull_request:
branches:
- main
permissions:
contents: read
pull-requests: read
concurrency:
group: coordination-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
coordinate:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Detect shared-file conflict
id: overlap
run: |
mkdir -p coordination
git diff --name-only origin/main...HEAD > coordination/files.txt
python .github/scripts/check_shared_agent_files.py \
--files coordination/files.txt \
--owners .github/agent-ownership.yml \
| tee coordination/overlap.log
- name: Upload coordination evidence
if: always()
uses: actions/upload-artifact@v4
with:
name: coordination-evidence
path: coordination/Choose an answer
Tap an option to check your answer.
Correct answer: 1=Yes 2=No 3=Yes.
Why this is the answer
Statement 1 is correct because the concurrency.group is set to coordination-${{ github.event.pullrequest.number }}. This ensures that only one workflow run for a specific pull request (identified by its number) can execute at a time, preventing duplicate coordination runs for the same PR. Statement 2 is incorrect. The concurrency group, as configured, is scoped to a single pull request number. It does not inherently coordinate conflicts across different pull requests; rather, it manages concurrent runs for the same pull request. Detecting conflicts across different pull requests would require additional logic. Statement 3 is correct. The Upload coordination evidence step uses if: always(), meaning it will execute regardless of whether the preceding Detect shared-file conflict step (which includes the overlap check) succeeds or fails. This ensures that evidence, such as overlap.log, is preserved even after a failed check.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed