A repository uses Copilot cloud agent to prepare remediation pull requests and a separate release-validation workflow to verify production readiness. When validation detects degraded behavior after a multi-agent change, rollback must be triggered manually and held by a protected production rollback environment before execution. Which option completes the workflow?
name: rollback-orchestrator
on:
(Missing value 1):
inputs:
target_sha:
description: Last known good deployment SHA
required: true
type: string
reason:
description: Human-approved rollback reason
required: true
type: string
permissions:
contents: read
(Missing value 2): write
jobs:
rollback:
runs-on: ubuntu-latest
environment: (Missing value 3)
steps:
- uses: actions/checkout@v4
with:
ref: ${{ inputs.target_sha }}
- name: Run production rollback
run: ./ops/rollback.sh "${{ inputs.target_sha }}" "${{ inputs.reason }}"Choose an answer
Tap an option to check your answer.
Correct answer: Missing value 1 = workflow_dispatch Missing value 2 = deployments Missing value 3 = production-rollback.
Why this is the answer
The correct answer is workflowdispatch, deployments, and production-rollback. Missing value 1: workflowdispatch is correct because the scenario states that rollback must be triggered manually. workflowdispatch allows a workflow to be triggered manually from the GitHub UI, via a REST API call, or from the GitHub CLI, which aligns with the requirement for manual intervention. pullrequest and workflowrun are incorrect as they trigger automatically based on pull request events or the completion of other workflows, respectively, not manual intervention. Missing value 2: deployments permission is required for the workflow to interact with deployments, specifically to manage the rollback process which often involves updating deployment statuses or creating new deployments. This permission grants the necessary access. checks is incorrect as it relates to GitHub Checks API, not deployment management. Missing value 3: production-rollback is correct because the scenario specifies that the rollback is held by a "protected production rollback environment." This indicates that the workflow should run within an environment specifically configured for production rollbacks, likely with specific protections and secrets. staging is incorrect as the rollback is for production.
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