A team reviews whether this workflow isolates parallel agent validation for separate services in a monorepo. Evaluate the following statements. 1. The concurrency group isolates cancellation per pull request. 2. The matrix configuration prevents service jobs from running in parallel. 3. The artifact settings separate evidence for each service scope.
name: validate-parallel-agents
on:
pull_request:
branches:
- main
permissions:
contents: read
pull-requests: read
concurrency:
group: validate-${{ github.workflow }}-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
validate:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
service: [billing, orders, identity]
steps:
- uses: actions/checkout@v4
- name: Validate service output
run: ./scripts/validate-service.sh "${{ matrix.service }}"
- name: Upload service evidence
uses: actions/upload-artifact@v4
with:
name: evidence-${{ matrix.service }}
path: reports/${{ matrix.service }}/Choose an answer
Tap an option to check your answer.
Correct answer: 1=Yes 2=No 3=Yes.
Why this is the answer
1=Yes: The concurrency group uses github.event.pullrequest.number, ensuring that each pull request has its own unique concurrency group. This allows parallel runs for different pull requests while canceling in-progress runs for the same pull request if a new commit is pushed. 2=No: The strategy.matrix configuration with fail-fast: false and multiple service values explicitly causes the jobs for 'billing', 'orders', and 'identity' to run in parallel. 3=Yes: The upload-artifact step uses name: evidence-${{ matrix.service }}, which dynamically creates unique artifact names (e.g., 'evidence-billing', 'evidence-orders') for each service. This effectively separates the evidence for each service scope.
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