You are building a continuous deployment pipeline for a project stored in a Git source repository and want to ensure that code changes can be verified before deploying to production. What should you do?

This option describes a robust CI/CD workflow that ensures verification before production deployment. Monitoring tags allows for clear versioning and control. Deploying staging tags to a staging environment for testing provides a dedicated space to validate changes without impacting production. Only after successful testing is the repository tagged for production, triggering deployment to the live environment. This sequential, tag-driven approach guarantees that only verified code reaches production. The other options have drawbacks: Using Spinnaker with red/black deployment is a good strategy for production deployment, but it doesn't explicitly address the pre-production verification requirement. Running tests directly on production deployments is risky and not a best practice for verification. Deploying to 10% of users (canary release) is a good production deployment strategy, but it still lacks a dedicated pre-production verification step for all changes.