Mountkirk Games wants to set up a continuous delivery pipeline. Their architecture includes many small services that they want to be able to update and roll back quickly. Mountkirk Games has the following requirements: ✑ Services are deployed redundantly across multiple regions in the US and Europe ✑ Only frontend services are exposed on the public internet ✑ They can provide a single frontend IP for their fleet of services ✑ Deployment artifacts are immutable Which set of products should they use?

The correct option leverages Google Kubernetes Registry (now Artifact Registry), Google Container Engine (now Google Kubernetes Engine or GKE), and Google HTTP(S) Load Balancer to meet Mountkirk Games' requirements. Kubernetes Engine provides an ideal platform for deploying and managing small, containerized services, enabling quick updates and rollbacks, and supporting multi-regional deployments. Google Kubernetes Registry stores immutable container images, fulfilling the immutable artifact requirement. The HTTP(S) Load Balancer offers a single frontend IP address for services, handles global traffic distribution across regions, and exposes only frontend services to the internet. Google Cloud Storage, Dataflow, and Compute Engine are general-purpose but less optimized for microservices and rapid deployment/rollback. App Engine is a good platform, but the Network Load Balancer is not ideal for global HTTP(S) traffic distribution and single IP for multiple services. Cloud Functions, Pub/Sub, and Deployment Manager are for serverless, messaging, and infrastructure deployment respectively, not directly addressing the core microservices deployment and load balancing needs.