A required workflow is supposed to capture an agent’s task progress and decision log. Reviewers say the workflow passed, but no downloadable decision log appears on the run summary page. Which option best explains the missing durable artifact?
Workflow: capture-agent-state
Event: pull_request
Job: summarize
Step: Generate decision log
mkdir -p agent-state
./scripts/validate-agent-output.sh > agent-state/decision-log.md
exit code: 0
Step: Add workflow summary
echo "## Agent validation summary" >> $GITHUB_STEP_SUMMARY
cat agent-state/decision-log.md >> $GITHUB_STEP_SUMMARY
exit code: 0
Step: Upload durable decision log
Warning: No files were found with the provided path: agent-state/decisions.md
No artifacts will be uploaded.
exit code: 0
Conclusion: success
Artifacts: noneChoose an answer
Tap an option to check your answer.
Correct answer: The artifact upload path does not match the file.
Why this is the answer
The correct answer is that the artifact upload path does not match the file. The "Generate decision log" step creates a file named agent-state/decision-log.md. However, the "Upload durable decision log" step attempts to upload agent-state/decisions.md (note the missing "-log"). This mismatch causes the upload to fail, resulting in no downloadable artifact. The pullrequest event can upload artifacts, so that option is incorrect. The workflow summary consumes the content of the file, not the file itself, so it doesn't prevent artifact upload. The job permission pull-requests: write is for modifying pull requests, not for uploading workflow artifacts, which typically requires actions: write or contents: write depending on the artifact type and destination.
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