Dev teams use Cloud Build to build/push Docker images but operations requires all images published to a centralized ops-managed registry. What should you do?

The correct option centralizes the registry as requested by operations while maintaining security and automation. By creating a separate project for operations with Container Registry, all images are stored in one controlled location. Granting the Cloud Build service account (which runs the builds) from each development project appropriate permissions to this centralized registry allows automated pushing of images without exposing sensitive credentials or requiring manual intervention. The first incorrect option creates multiple registries, violating the requirement for a centralized, ops-managed registry. The third incorrect option suggests storing service account keys in source control, which is a significant security risk and against best practices. The fourth incorrect option proposes deploying an open-source Docker Registry on Compute Engine, which introduces unnecessary operational overhead, management, and security concerns compared to using the fully managed Container Registry service.