MENU
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 2 answers
Suggested Answer: B
Get Premium Professional Cloud Architect (PR000213) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
38 comments · newest first
MA
Margret
11 months ago
Wait, can App Engine really handle everything we need?
ST
Stephane
11 months ago
Compute Engine with custom instance types? Really?
LE
Levi
11 months ago
Definitely GKE, but not sure about the second option.
MA
Mary
11 months ago
I think App Engine is the way to go for no-ops.
LO
Lorrine
12 months ago
GKE with containers is a solid choice for auto-scaling!
TE
Terina
12 months ago
I feel like Google Kubernetes Engine is definitely one of the answers, but I’m torn between App Engine and Compute Engine with managed instance groups for the second choice.
EU
Eun
1 year ago
I'm a bit confused about Compute Engine with managed instance groups. I know it can scale, but is it really considered no-ops compared to App Engine?
MI
Milly
1 year ago
I remember practicing a question similar to this, and I think Google App Engine might be the right fit for a no-ops solution. It handles scaling automatically, right?
VI
Vi
1 year ago
I think Google Kubernetes Engine could be a good choice since it supports auto-scaling and is designed for containerized applications, but I'm not entirely sure about the second option.
IZ
Izetta
1 year ago
I'm feeling pretty confident about this one. Compute Engine with containers and Google Kubernetes Engine are the way to go. They'll give me the flexibility and scalability I need for this new cloud-native solution.
JE
Jenelle
1 year ago
Okay, I've got this. The key requirements are no-ops and auto-scaling, so I'm going to go with Google Kubernetes Engine and Google App Engine. Those seem like the best choices to meet those needs.
SA
Salena
1 year ago
Hmm, I'm a bit confused. I'm not sure if Compute Engine with containers or Compute Engine with managed instance groups would also be good options. I'll need to review the differences between these compute products.
FA
Fanny
1 year ago
This question seems straightforward. I think the two compute products I should choose are Google Kubernetes Engine with containers and Google App Engine Standard Environment.
MA
Mary
1 year ago
Whoa, slow down there, Elon Musk! I think (B) and (C) are the clear winners here. Unless you want to spend the next 9 months tinkering with your instances instead of actually building your app.
TI
Tiera
1 year ago
Let's go with Google Kubernetes Engine with containers and Google App Engine Standard Environment for our cloud-native solution.
EV
Eve
1 year ago
I think (B) and (C) will save us a lot of time and effort in the long run.
OL
Olene
1 year ago
Yeah, Google Kubernetes Engine with containers and Google App Engine Standard Environment seem like the best choices for no-ops and auto-scaling.
SH
Sherell
1 year ago
I agree, (B) and (C) are definitely the way to go for a more cloud-native solution.
DE
Delsie
1 year ago
Hold up, you're telling me I can't use my custom instance types? Dang, guess I'm stuck with (B) and (C) then. Oh well, at least I don't have to obsess over my VMs anymore.
KA
Karan
1 year ago
Don't worry about custom instance types, focus on the benefits of Google Kubernetes Engine with containers and Google App Engine Standard Environment.
GE
Gearldine
1 year ago
Yeah, those two choices will give you the no-ops and auto-scaling features you're looking for.
WI
Willard
1 year ago
Custom instance types won't work for this, but Google Kubernetes Engine with containers and Google App Engine Standard Environment are good options.
MA
Mattie
2 years ago
I was considering (A) and (E), but you're right, (B) and (C) are the way to go. I'm just glad I don't have to worry about managing the infrastructure myself!
RO
Rosalind
1 year ago
It's great that you don't have to worry about managing the infrastructure yourself with (B) and (C) in place.
CA
Carey
1 year ago
I agree, (B) and (C) are the way to go for a more efficient and scalable solution.
BA
Barrett
1 year ago
Definitely, (B) and (C) will make your life easier with auto-scaling and less manual management.
DO
Dominga
1 year ago
I think (A) and (E) are good options too, but (B) and (C) are more cloud-native and no-ops.
GL
Glenna
2 years ago
Definitely going with (B) and (C). The prompt specifically asks for a no-ops and auto-scaling solution, and those two options fit the bill perfectly.
LI
Lili
1 year ago
I think (B) and (C) are the most suitable options for achieving a cloud-native solution with auto-scaling capabilities.
CH
Cherelle
1 year ago
I agree, (B) Google Kubernetes Engine with containers and (C) Google App Engine Standard Environment are the best choices for a no-ops and auto-scaling solution.
HA
Halina
2 years ago
I think Google Kubernetes Engine with containers (B) and Google App Engine Standard Environment (C) are the best choices here. They're both auto-scaling and provide a more hands-off, no-ops experience.
BU
Burma
1 year ago
Those two choices sound perfect for a more cloud-native solution with no-ops and auto-scaling capabilities.
BA
Barrie
1 year ago
I would go with Google Kubernetes Engine with containers (B) and Google App Engine Standard Environment (C) for sure.
BR
Brice
1 year ago
I think Google App Engine Standard Environment (C) is also a good option for a no-ops experience.
VE
Velda
1 year ago
I agree, Google Kubernetes Engine with containers (B) is a great choice for auto-scaling.
VE
Veronika
2 years ago
I prefer Compute Engine with managed instance groups for more control over the instances.
YV
Yvonne
2 years ago
I agree with Rebecka. Google App Engine Standard Environment could also be a good choice for a no-ops solution.
RE
Rebecka
2 years ago
I think we should choose Google Kubernetes Engine with containers for auto-scaling.