The correct option is Set ACTIONS_STEP_DEBUG as either a repository secret or a repository variable and the secret value takes precedence if both are set. This configuration enables step debug logs when the value is true and GitHub uses the secret value if both a secret and a variable exist.

To generate step debug logs you define ACTIONS_STEP_DEBUG with the value true. You can create it as a repository secret for stronger protection or as a repository variable for convenience. When both are defined with the same name GitHub resolves the value from the secret first. If only a variable exists then the variable value is used.

Set ACTIONS_STEP_DEBUG as either a repository secret or a repository variable and the variable value takes precedence if both are set is incorrect because it reverses the precedence. The secret value is used when both are present.

Cloud Logging is incorrect because it is not a GitHub Actions feature and it does not control step debug logs for GitHub workflows.

Set ACTIONS_STEP_DEBUG only as a repository variable is incorrect because GitHub supports using either a secret or a variable for this setting. Limiting it to only a variable is unnecessary and does not reflect the supported methods.

Full AWS Practitioner Certification Question