The correct options are Composite actions, Docker container actions, and JavaScript actions.

Composite actions let you combine multiple workflow steps into a single reusable unit defined in YAML. They are ideal for sharing common sequences of steps across many repositories because they can call other actions and run shell commands while avoiding the need for custom runtimes.

Docker container actions package code and all dependencies inside a container image and run in a consistent environment on any runner. They are well suited for tools or languages that need specific system dependencies or isolation.

JavaScript actions run directly on the runner using the Node.js runtime which makes them fast to start and easy to distribute. They are a good choice for lightweight logic and for interacting with the GitHub API without container overhead.

Cloud Build is not a GitHub Actions action type. It is a Google Cloud continuous integration service and although you can integrate external services from a workflow it does not implement a reusable GitHub Action.

Full AWS Practitioner Certification Question