You are building Docker-based microservices and want Google-recommended CI and artifact storage. What should you do?

The recommended Google Cloud approach for CI/CD with Docker-based microservices is to use Cloud Build and Container Registry. Cloud Build integrates directly with source repositories (like Cloud Source Repositories, GitHub, or Bitbucket) via triggers, automatically building container images upon code changes. Tagging images with the commit hash ensures unique, traceable versions, which is crucial for rollbacks and auditing. Container Registry is Google's fully managed Docker image registry, providing secure and efficient storage for these artifacts. Incorrect options: Pushing to Cloud Storage is not the purpose of Cloud Storage for container images; Container Registry is designed for this. Polling with Cloud Scheduler is inefficient and unnecessary when Cloud Build triggers offer real-time integration. Tagging with a timestamp is less useful for traceability than a commit hash. Building one "latest" image is problematic for microservices, as it lacks version control and makes rollbacks difficult. Each microservice should have its own versioned image.