The correct option is Set a retention days value on each artifact in the workflow step that uses actions/upload-artifact.

This works because the upload step accepts an input that sets the number of days to keep a specific artifact. You can set it to 45 for the artifacts that need longer retention and omit it for others so they use the default. This approach overrides the repository or organization default only for the artifacts you choose and leaves the rest unchanged.

Enable a repository artifact retention policy that automatically applies to every artifact is incorrect because a repository setting establishes a single default for all artifacts and does not selectively target individual artifacts in a workflow. You would still need a per artifact override in the upload step to meet the requirement.

Configure artifact retention only at the organization or enterprise level is incorrect because those settings set defaults for repositories and do not provide per artifact granularity. Per artifact control is done in the upload step within the workflow.

Store artifacts in a Google Cloud Storage bucket with a lifecycle rule is incorrect because that moves storage outside GitHub Actions artifact management and does not control the retention of GitHub Actions artifacts in GitHub.

Full AWS Practitioner Certification Question