The correct answer is A workflow can start from GitHub repository activity, from scheduled times, or from events that come from outside systems.

GitHub Actions workflows can start from many repository events such as pushes, pull requests, issues, and releases. They can also run on a schedule using cron syntax in the workflow file. External systems can initiate runs by creating supported events through the GitHub API such as repository_dispatch or by invoking workflow_dispatch which allows programmatic manual runs. These capabilities together mean workflows can begin from repository activity, from scheduled times, and from events that originate outside GitHub.

Workflows can be triggered by GitHub events or on a schedule but they cannot be started by outside systems is incorrect because outside systems can start a run by calling the GitHub API to create a repository_dispatch event or by triggering workflow_dispatch, which proves that external initiation is supported.

Cloud Pub/Sub can run GitHub Actions directly without any GitHub event configuration is incorrect because a third party service cannot run jobs on its own. It must invoke a GitHub supported event such as repository_dispatch or workflow_dispatch or otherwise cause an event that the workflow is configured to listen for.

Only commits and pull requests within the repository can start a workflow is incorrect because many other events can initiate workflows including issues, releases, tags, schedules, manual dispatch, and external dispatch through the API.

Full AWS Practitioner Certification Question