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…

Question

Options

• ACompute Engine with containers
• BGoogle Container Engine with containers
• CGoogle App Engine Standard Environment
• DCompute Engine with custom instance types
• ECompute Engine with managed instance groups

• A
  4% (2)
• B
  93% (50)
• D
  2% (1)
• E
  2% (1)

Explanation

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. Cloud-Platform%E2%80%99s-NoOps-claim

No community discussion yet for this question.