The correct option is Shell commands enable running tailored scripts and commands inside a job which provides flexibility.

Using the run field lets you write ad hoc commands that glue together reusable actions and cover gaps that a marketplace action does not address. You can set up the environment, run linters and tests, transform files, or invoke command line tools available on the runner. This approach gives precise control without needing to create a new action for every small task.

The statement Shell commands let you trigger a workflow manually from the GitHub Actions interface is incorrect. Manual runs are enabled by defining the workflow_dispatch event in the workflow file and are not related to adding run steps.

The statement Shell commands allow workflows to deploy directly to Google Cloud without any additional tools is incorrect. Deploying to Google Cloud requires credentials and appropriate tooling such as the gcloud CLI or official Google Cloud actions and shell commands alone do not remove those requirements.

The statement Shell commands eliminate the need for GitHub Secrets when handling sensitive configuration is incorrect. Secrets are still necessary and shell steps should consume sensitive values from secrets or another secure store rather than hard coding them.

Full AWS Practitioner Certification Question