You are managing an application deployed on Cloud Run for Anthos, and you need to define a strategy for deploying new versions of the application. You want to evaluate the new code with a subset of production traffic to decide whether to proceed with the rollout. What should you do?

The correct approach is to deploy a new revision to Cloud Run and configure traffic splitting. Cloud Run for Anthos inherently supports traffic management at the revision level, allowing you to gradually shift traffic from an old revision to a new one. This enables canary deployments or A/B testing by directing a specific percentage of requests to the new version, allowing for evaluation before a full rollout. Deploying a new service and adding a Cloud Load Balancing instance is overly complex and unnecessary, as Cloud Run's built-in traffic management handles this scenario more efficiently. Setting up continuous deployment with a TRAFFICPERCENTAGE substitution variable in Cloud Build is not a standard or direct method for managing live traffic percentages in Cloud Run; Cloud Build is for building and deploying, not for runtime traffic management. Configuring Traffic Director is for managing mesh services and is not the native or most straightforward solution for traffic splitting within Cloud Run for Anthos.