The correct option is Place the action metadata file at the repository root, draft a release, choose "Publish this Action to the GitHub Marketplace", select appropriate categories, set a version tag, and publish the release.

To list an action on GitHub Marketplace you must have a valid action.yml or action.yaml in the repository root. You then create a release and select the publish to Marketplace option and choose categories that match your action. A semantic version tag such as v1 or v1.2.3 is required and the release will publish the listing. The repository must be public for the listing to appear in Marketplace.

Request manual review of the metadata file by GitHub, wait for approval, then tag a version and the Marketplace listing will appear automatically is incorrect because publication happens through the release flow where you opt in to Marketplace and there is no separate manual review step for actions. Tagging alone does not create a listing.

Build the action with Cloud Build, push artifacts to Artifact Registry, and link the project to a Marketplace listing from Google Cloud console is incorrect because Marketplace listings are managed on GitHub. Even when an action uses a container image the listing is created by releasing on GitHub rather than through an external cloud console.

Merge the action metadata file into the default branch, draft a release, select "Publish this Action to the GitHub Marketplace", then choose categories without assigning a version tag is incorrect because a version tag is required to publish. Without a tag the release cannot be listed and GitHub recommends semantic versioning for stability and discoverability.

Full AWS Practitioner Certification Question