Google Associate Cloud Engineer Exam - Topic 3 Question 102 Discussion

Actual exam question for Google's Associate Cloud Engineer exam

Question #: 102
Topic #: 3

[All Associate Cloud Engineer Questions]

You need to deploy a single stateless web application with a web interface and multiple endpoints. For security reasons, the web application must be reachable from an internal IP address from your company's private VPC and on-premises network. You also need to update the web application multiple times per day with minimal effort and want to manage a minimal amount of cloud infrastructure. What should you do?

ADeploy the web application on Google Kubernetes Engine standard edition with an internal ingress.

BDeploy the web application on Cloud Run with Private Google Access configured

CDeploy the web application to GKE Autopilot with Private Google Access configured

DDeploy the web application on Cloud Run with Private Service Connect configured.

Show Suggested Answer

Suggested Answer: A

by Stephanie at Feb 08, 2025, 09:22 AM

Limited Time Offer

25%

Off

Get Premium Associate Cloud Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Rosio

4 months ago

Surprised that people are considering GKE at all for this!

upvoted 0 times

...

Kiley

5 months ago

B has the right balance of simplicity and security.

upvoted 0 times

...

Micheline

5 months ago

Wait, isn't GKE more complex to manage than Cloud Run?

upvoted 0 times

...

Farrah

5 months ago

I disagree, C seems more robust for scaling.

upvoted 0 times

...

Dudley

5 months ago

I think option B is the best choice for minimal management.

upvoted 0 times

...

Blair

6 months ago

I’m a bit confused about the differences between the options, especially between Cloud Run and GKE. I need to review that again.

upvoted 0 times

...

Kristel

6 months ago

I practiced a similar question where we had to secure access, and I think deploying with Private Service Connect could be the right choice.

upvoted 0 times

...

Luis

6 months ago

I think GKE Autopilot could work too, but I feel like it might involve more management than I want.

upvoted 0 times

...

Audrie

6 months ago

I remember we discussed using Cloud Run for stateless applications, but I'm not sure about the Private Google Access part.

upvoted 0 times

...

Bok

6 months ago

I'm pretty confident that option B, Cloud Run with Private Google Access, is the way to go here. It meets all the requirements, and the managed serverless platform should make it easy to update the app frequently with minimal effort on my part.

upvoted 0 times

...

Gracia

6 months ago

Okay, let me think this through. The key requirements are internal network access, minimal cloud infrastructure, and easy updates. I'm leaning towards option C - GKE Autopilot with Private Google Access. That way, I can take advantage of the managed Kubernetes service and still have the private network access I need.

upvoted 0 times

...

Pilar

6 months ago

Hmm, I'm a bit unsure about this one. The question mentions wanting to update the web app multiple times a day, so I'm wondering if Cloud Run is the best option since it might require more manual effort to deploy new versions. Maybe GKE Autopilot with Private Google Access would be a better choice?

upvoted 0 times

...

Derick

6 months ago

This looks like a pretty straightforward question. I think I'll go with option B - Deploy the web application on Cloud Run with Private Google Access configured. That seems like the easiest way to meet the requirements of being reachable from the internal network and minimizing cloud infrastructure management.

upvoted 0 times

...

Toi

1 year ago

Haha, I bet the exam designers are trying to trick us with all these similar-sounding options. But I think Option B is the way to go.

upvoted 0 times

...

Tashia

1 year ago

I'm leaning towards Option C. GKE Autopilot with Private Google Access seems like a good balance between control and ease of management.

upvoted 0 times

...

Dallas

1 year ago

I don't know, the Kubernetes management in Option A might be overkill for a simple web app. Cloud Run with Private Service Connect in Option D could be a good compromise.

upvoted 0 times

...

Lelia

1 year ago

Option B seems like the easiest way to go. Cloud Run with Private Google Access sounds like the perfect fit for this use case.

upvoted 0 times

Olive

1 year ago

I think it's a good choice for managing minimal cloud infrastructure while meeting security requirements.

upvoted 0 times

...

Janine

1 year ago

It definitely simplifies the deployment process and ensures security for internal access.

upvoted 0 times

...

Marya

1 year ago

Definitely, it's important to ensure the web application is secure and easily updatable with minimal effort.

upvoted 0 times

...

Nenita

1 year ago

I agree, Cloud Run with Private Google Access seems like the best option for this scenario.

upvoted 0 times

...

Rosalind

1 year ago

I agree, Cloud Run with Private Google Access would provide the security and ease of management needed for this scenario.

upvoted 0 times

...

Fernanda

1 year ago

B) Deploy the web application on Cloud Run with Private Google Access configured

upvoted 0 times

...

Mari

1 year ago

Option B seems like the easiest way to go. Cloud Run with Private Google Access sounds like the perfect fit for this use case.

upvoted 0 times

...

Buck

1 year ago

That's a good point, but I still think option A is more suitable for our needs of updating the web application multiple times per day with minimal effort.

upvoted 0 times

...

Katheryn

1 year ago

I disagree, I believe option B is better as it allows us to deploy the web application on Cloud Run with Private Google Access configured for better security.

upvoted 0 times

...

Buck

1 year ago

I think option A is the best choice because it allows us to deploy the web application on Google Kubernetes Engine with an internal ingress.

upvoted 0 times

...