Development workflow: any push to the remote develop branch must be automatically built, tested, and—if successful—deployed to the development environment. Ensure only approved artifacts are deployed. What should you implement?

The correct option establishes an automated CI/CD pipeline. A Cloud Build trigger on the develop branch ensures that every push automatically initiates testing, container image building, and storage in Container Registry. A separate deployment pipeline then deploys these validated images to the development environment. Restricting deploy permissions to the deployment tool ensures that only approved artifacts (those successfully processed by the pipeline) are deployed, maintaining control and security. The first incorrect option relies on manual developer actions and local deployments, which is error-prone, lacks automation, and doesn't guarantee approved artifacts. The second incorrect option uses a post-commit hook, which is better than pre-commit but still requires developers to manually deploy, again lacking full automation and control over approved artifacts. The third incorrect option incorrectly suggests relying on Vulnerability Scanning for test validation (Vulnerability Scanning is for security, not functional tests) and grants Cloud Build direct deployment access, which is less secure than having a dedicated deployment tool with restricted permissions.