ExamTopics Logo
Mail Us[email protected]
Menu
Google Discussions
exam questions

Exam Professional Cloud Architect All Questions

View all questions & answers for the Professional Cloud Architect exam
Go to Exam

Exam Professional Cloud Architect topic 1 question 169 discussion

Actual exam question from Google's Professional Cloud Architect
Question #: 169
Topic #: 1
[All Professional Cloud Architect Questions]

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.)

  • A. Compute Engine with containers
  • B. Google Kubernetes Engine with containers
  • C. Google App Engine Standard Environment
  • D. Compute Engine with custom instance types
  • E. Compute Engine with managed instance groups
Show Suggested Answer Hide Answer
Suggested Answer: BC 🗳️
by rishab86 at June 3, 2021, 9:34 a.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
PeppaPig
Highly Voted 3 years, 5 months ago
I would go with B&C Cloud-native, less-ops and auto-scaling all get addressed
upvoted 18 times
...
kinghin
Highly Voted 2 years, 9 months ago
Why E is incorrect? can't MIG also perform autoscaling? Also it needs fewer administration as GKE
upvoted 9 times
AhmedH7793
2 years, 3 months ago
No ops = Serverless / Almost Serverless MIG is not.
upvoted 8 times
JaimeMS
6 months, 3 weeks ago
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.
upvoted 2 times
...
...
...
piyu1515
Most Recent 1 day, 5 hours ago
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.
upvoted 1 times
...
JC0926
1 year, 8 months ago
Selected Answer: BC
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.
upvoted 5 times
...
jlambdan
1 year, 9 months ago
Selected Answer: BC
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.
upvoted 2 times
...
Deb2293
1 year, 9 months ago
Selected Answer: CE
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.
upvoted 5 times
...
telp
1 year, 10 months ago
Selected Answer: BC
No ops: use container or gcp product without mangement. So not VM possible in the answer
upvoted 1 times
...
habros
2 years ago
Selected Answer: BC
App Engine standard = container based (can even go to zero) App Engine flexible = VM based (minimum 1) No ops: container > VM
upvoted 2 times
...
Mahmoud_E
2 years, 2 months ago
Selected Answer: BC
B & C seems right to me, E needs lots of Ops to build image, instance template and instance group, ... maintain your image always
upvoted 3 times
...
AzureDP900
2 years, 2 months ago
B. Google Kubernetes Engine with containers C. Google App Engine Standard Environmen
upvoted 2 times
...
alexandercamachop
2 years, 3 months ago
Selected Answer: BC
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
upvoted 2 times
...
6721sora
2 years, 3 months ago
Selected Answer: CE
C and E GKE is absolutely nor no-ops. MIG can be closest to no-ops among the other options
upvoted 5 times
...
jabrrJ68w02ond1
2 years, 3 months ago
Selected Answer: BC
B&C seem to be right for this question. In reality, whoever really proposes B as an option never ran Kubernetes in production.
upvoted 2 times
...
JoeyCASD
2 years, 7 months ago
Vote A and B However I think option B should address more specifically, like GKE - autopilot mode.
upvoted 1 times
JoeyCASD
2 years, 7 months ago
Correct the answer for B and C
upvoted 1 times
...
...
vincy2202
3 years ago
Selected Answer: BC
BC are the correct answers
upvoted 1 times
...
Bobch
3 years ago
Selected Answer: BC
Agree B and C
upvoted 1 times
...
MaxNRG
3 years, 2 months ago
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.
upvoted 3 times
MaxNRG
3 years, 2 months ago
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.
upvoted 3 times
...
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago