The correct option is Create a composite action that groups common steps into a single reusable action. This packages the repeated setup test and deployment steps into one versioned unit that workflows in many repositories can call with a few inputs which minimizes duplication and maintenance.

This approach keeps the shared logic close to the steps you want to reuse. It runs inside the caller job so teams can drop it into any workflow without restructuring their pipelines. You can define inputs and outputs to keep configuration minimal and you can version the action so updates are controlled and predictable.

Use a reusable workflow called with workflow_call to share a standard pipeline across repositories is better when you want to orchestrate whole workflows across jobs rather than embed a small set of steps inside an existing job. A reusable workflow is invoked as a separate workflow or job which adds structure that is not necessary when you only need to bundle common steps.

Create a Docker container action to isolate workflow commands inside a dedicated image is unnecessary when you simply want to group existing steps. A container action adds the overhead of building and publishing an image and it focuses on packaging tools rather than reducing step duplication across workflows.

Develop a JavaScript action to implement custom workflow logic in Node.js is suited for custom programmatic behavior. In this scenario you already have shell based steps to reuse and a JavaScript action would add code complexity without solving the need to group and reuse those steps.

Full AWS Practitioner Certification Question