Your company just finished a rapid lift and shift to Google Compute Engine for your compute needs. You have another 9 months to design and deploy a more cloud-native solution. Specifically, you want a system that is no-ops and auto-scaling.
Which two compute products should you choose? (Choose two.)
To achieve a no-ops and auto-scaling system in a cloud-native solution, the best options are Google Kubernetes Engine (GKE) with containers and Google App Engine Standard Environment. GKE is a managed Kubernetes service that handles cluster management tasks such as scaling, updates, and security patches, thereby reducing operational overhead. It also automatically resizes clusters based on workload demands. Google App Engine Standard Environment is a fully managed platform that scales applications automatically based on demand and minimizes the need for infrastructure management. These two options provide a combination of automated scaling and reduced operational responsibilities, fitting the requirements perfectly.
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 = Serverless / Almost Serverless MIG is not.
No Ops -> Kubernetes? This question is too generic to choose between MIG and GKE. In the context of this exam, I would choose B (GKE), specally with current options as Autopilot. But in my day to day I would consider way more factors.
C and E GKE is absolutely nor no-ops. MIG can be closest to no-ops among the other options
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.
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 & C. Although GKE standard is definitely not no-ops!
Correct Answer: BC B: With Container Engine, Google will automatically deploy your cluster for you, update, patch, secure the nodes. Kubernetes Engine's cluster autoscaler automatically resizes clusters based on the demands of the workloads you want to run. C: Solutions like Datastore, BigQuery, AppEngine, etc are truly NoOps. App Engine by default scales the number of instances running up and down to match the load, thus providing consistent performance for your app at all times while minimizing idle instances and thus reducing cost.
Note: At a high level, NoOps means that there is no infrastructure to build out and manage during usage of the platform. Typically, the compromise you make with NoOps is that you lose control of the underlying infrastructure. https://www.quora.com/How-well-does-Google-Container-Engine-support-Google-Cloud-Platform%E2%80%99s-NoOps-claim B – Google Container Engine (autoscaling) C – Google AppEngine Standard Environment (no ops) You should understand this Q as following: after Lift-n-Shift parts of the monolith should be moved to managed services (e.g. REST API) running on GAE; and other micro-services will run in containers / pods.
B & C seems right to me, E needs lots of Ops to build image, instance template and instance group, ... maintain your image always
B&C seem to be right for this question. In reality, whoever really proposes B as an option never ran Kubernetes in production.
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
B. Google Kubernetes Engine with containers C. Google App Engine Standard Environmen
App Engine standard = container based (can even go to zero) App Engine flexible = VM based (minimum 1) No ops: container > VM
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.
Agree B and C
BC are the correct answers
Vote A and B However I think option B should address more specifically, like GKE - autopilot mode.
Correct the answer for B and C
No ops: use container or gcp product without mangement. So not VM possible in the answer