Test a Cloud Run service revision by sending 10% of traffic to the new change while maintaining backward compatibility with minimal effort.

The correct approach for testing a Cloud Run service revision with 10% traffic while maintaining backward compatibility involves deploying the new revision without immediately routing traffic to it. Cloud Run allows you to deploy new revisions and then gradually shift traffic. By deploying the new revision with 0% traffic, you ensure it's ready but not impacting users. Subsequently, you can allocate 10% of traffic to the new revision, allowing for A/B testing or canary deployments. This method minimizes risk and effort as it leverages Cloud Run's built-in traffic management. Incorrect options: Replacing the current service and then splitting traffic is disruptive and doesn't allow for a controlled, gradual rollout. Deploying the new revision and immediately splitting traffic doesn't allow for a "no traffic" initial deployment, which is crucial for a controlled rollout. Replacing the service and using a load balancer is unnecessary; Cloud Run handles traffic splitting natively, making a separate load balancer redundant and adding complexity.