Exam Professional Cloud Architect topic 1 question 169 discussion

I would go with B&C Cloud-native, less-ops and auto-scaling all get addressed

Why E is incorrect? can't MIG also perform autoscaling? Also it needs fewer administration as GKE

no ops and more cloud native, GKE and app engine;

App Engine Standard is a Platform-as-a-Service (PaaS) offering that’s fully managed, allowing you to deploy applications with zero infrastructure management. It supports auto-scaling out-of-the-box and handles traffic spikes automatically. It’s great for stateless applications, APIs, and web applications that need rapid deployment and minimal operations. Best Use Case: Ideal for teams looking for a serverless approach without worrying about infrastructure scaling or patching.

Option B, Google Kubernetes Engine (GKE) with containers, is a managed Kubernetes service that automatically manages and scales containerized applications. GKE handles cluster management tasks like scaling, upgrades, and security patches, allowing you to focus on the application itself. Option C, Google App Engine Standard Environment, is a fully managed platform for building and deploying applications. It automatically scales applications based on demand and provides a no-ops experience. With App Engine Standard Environment, you don't need to worry about infrastructure management, as Google handles it for you.

B: GKE with autopilot mode for workload not requiring ingress or egress. Otherwise you will need some ops work IMHO. C: app engine for workload requiring ingress. It comes with autoscaling features and rolling update features without being as heavy as gke.

I would still go for C & E. My take is GKE still requires some operational overhead for managing the Kubernetes cluster and ensuring high availability of the workloads. Hence C & E would be most suitable one.

No ops: use container or gcp product without mangement. So not VM possible in the answer

App Engine standard = container based (can even go to zero) App Engine flexible = VM based (minimum 1) No ops: container > VM

B & C seems right to me, E needs lots of Ops to build image, instance template and instance group, ... maintain your image always

B. Google Kubernetes Engine with containers C. Google App Engine Standard Environmen

No ops = Serverless / Almost Serverless, less operational management overhead. Kubernetes and App Engine are the only one that gives us that flexibility, plus is modernizing apps

C and E GKE is absolutely nor no-ops. MIG can be closest to no-ops among the other options

B&C seem to be right for this question. In reality, whoever really proposes B as an option never ran Kubernetes in production.

Vote A and B However I think option B should address more specifically, like GKE - autopilot mode.

BC are the correct answers

Agree B and C