Create and Troubleshoot Custom Actions GH-200 Practice Questions (Page 5)

Questions 21–25

1. 21application · medium

   A JavaScript action uses core.setFailed() to signal a failure. The action runs, but the workflow step is marked as 'success' even though the action logged an error. What is the most likely cause?

   • AThe action is a composite action, not a JavaScript action.
   • BThe action's index.js is not the entry point specified in action.yml.
   • CThe action.yml does not specify 'runs.using: node20'.
   • DThe action uses console.error() instead of core.setFailed().
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   What is the key characteristic of a composite action?

   • AIt combines multiple workflow steps into a single action using action.yml with a `steps` section.
   • BIt is a JavaScript file that uses the GitHub Actions toolkit.
   • CIt is a pre-built action hosted on the GitHub Marketplace.
   • DIt runs inside a Docker container defined by a Dockerfile.
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   A Docker container action fails with a permission denied error when trying to write to a directory. What is a likely cause?

   • AThe action is missing an input that is required.
   • BThe container's user does not have write permissions to the directory.
   • CThe action.yml file has a syntax error.
   • DThe runner does not support Docker containers.
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   Which of the following is a common technique for debugging a custom action that is failing?

   • ADeleting the action's `action.yml` file to force a rebuild.
   • BChanging the action's runtime from node20 to node16.
   • CRemoving all inputs from the action's action.yml.
   • DAdding debug messages using `core.debug()` in a JavaScript action and enabling step debug logging.
   Reveal Solution Discussion Select an answer first
6. 25expert · hard

   An organization publishes an action. They accidentally pushed a breaking change to the v1 tag. They want to revert the tag to the previous commit. What is the best course of action?

   • AForce-push the v1 tag back to the previous commit.
   • BDelete the v1 tag and recreate it at the previous commit.
   • CRevert the breaking change with a new commit and move the v1 tag to that commit.
   • DCreate a new tag v1.0.1 pointing to the previous commit and leave v1 at the broken commit.
   Reveal Solution Discussion Select an answer first