Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Associate Cloud Engineer Exam - Topic 3 Question 93 Discussion

Actual exam question for Google's Associate Cloud Engineer exam
Question #: 93
Topic #: 3
[All Associate Cloud Engineer Questions]

You want to deploy an application on Cloud Run that processes messages from a Cloud Pub/Sub topic. You want to follow Google-recommended practices. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

Instance groups are collections of virtual machine (VM) instances that you can manage as a single entity. Instance groups can help you simplify the management of multiple instances, reduce operational costs, and improve the availability and performance of your applications. Instance groups support autoscaling, which automatically adds or removes instances from the group based on increases or decreases in load. Autoscaling helps your applications gracefully handle increases in traffic and reduces cost when the need for resources is lower. You can set the autoscaling policy based on CPU utilization, load balancing capacity, Cloud Monitoring metrics, or a queue-based workload. In this case, since the video encoding software is CPU-intensive, setting the autoscaling based on CPU utilization is the best option to ensure high availability and optimal performance.Reference:

Instance groups

Autoscaling groups of instances


Contribute your Thoughts:

0/2000 characters
Nicholle
4 months ago
Yeah, B is definitely the recommended approach!
upvoted 0 times
...
Thora
4 months ago
D seems overly complicated for this task.
upvoted 0 times
...
Bernardo
4 months ago
Wait, can Cloud Run really pull messages?
upvoted 0 times
...
Diane
4 months ago
I think C sounds better for security.
upvoted 0 times
...
Rasheeda
5 months ago
Option B is the way to go!
upvoted 0 times
...
Doyle
5 months ago
I’m a bit confused about option D. Deploying on GKE seems more complex than necessary for this scenario, right?
upvoted 0 times
...
Steffanie
5 months ago
I feel like I saw a similar question about pulling messages from a subscription. Is that what option B is suggesting?
upvoted 0 times
...
Cristy
5 months ago
I think option C sounds familiar. It involves using a service account for the push subscription, which seems like a good practice.
upvoted 0 times
...
Adelle
5 months ago
I remember we discussed using Cloud Functions for Pub/Sub, but I'm not sure if that's the best approach for Cloud Run.
upvoted 0 times
...
Rusty
5 months ago
I think Option B might be the simplest solution. Granting the Pub/Sub Subscriber role and having the application pull messages directly from the subscription seems straightforward.
upvoted 0 times
...
Sharee
5 months ago
Hmm, I'm a bit confused about the Google-recommended practices part. I'll need to review the documentation to make sure I choose the best option.
upvoted 0 times
...
Horace
5 months ago
This question seems straightforward, but I want to make sure I understand the requirements correctly before answering.
upvoted 0 times
...
Marya
6 months ago
Option C looks like the way to go. Giving the Cloud Run Invoker role to a service account and using that for the Pub/Sub subscription seems like the most secure and recommended approach.
upvoted 0 times
...
Carma
6 months ago
I practiced a similar question on BGP troubleshooting last week. I'm leaning towards option A, but I'm not confident.
upvoted 0 times
...
Wilson
10 months ago
D, huh? Might as well throw in a kubernetes cluster, a few microservices, and a serverless function or two, just to be safe. Why keep it simple when you can make it complicated?
upvoted 0 times
Desire
9 months ago
D) 1. Deploy your application on Cloud Run on GKE with the connectivity set to Internal.2. Create a Cloud Pub/Sub subscription for that topic.3. In the same Google Kubernetes Engine cluster as your application, deploy a container that takes the messages and sends them to your application.
upvoted 0 times
...
William
9 months ago
C) 1. Create a service account.2. Give the Cloud Run Invoker role to that service account for your Cloud Run application.3. Create a Cloud Pub/Sub subscription that uses that service account and uses your Cloud Run application as the push endpoint.
upvoted 0 times
...
Felicitas
9 months ago
B) 1. Grant the Pub/Sub Subscriber role to the service account used by Cloud Run.2. Create a Cloud Pub/Sub subscription for that topic.3. Make your application pull messages from that subscription.
upvoted 0 times
...
...
Maia
11 months ago
B all the way! Keeping things simple and following Google's recommendations - can't go wrong with that.
upvoted 0 times
Simona
9 months ago
Definitely, simplicity is key when it comes to following best practices.
upvoted 0 times
...
Laura
9 months ago
That sounds like a solid plan. Google knows best!
upvoted 0 times
...
Detra
10 months ago
B) 1. Grant the Pub/Sub Subscriber role to the service account used by Cloud Run.2. Create a Cloud Pub/Sub subscription for that topic.3. Make your application pull messages from that subscription.
upvoted 0 times
...
...
Tammara
11 months ago
A? Really? Calling Cloud Run from a Cloud Function for every message? That's just adding an extra hop and potential failure point. Not a fan.
upvoted 0 times
Brice
9 months ago
A? Yeah, I agree. It seems like a more direct and efficient approach. Let's go with option B.
upvoted 0 times
...
Melvin
9 months ago
C) 1. Create a service account.2. Give the Cloud Run Invoker role to that service account for your Cloud Run application.3. Create a Cloud Pub/Sub subscription that uses that service account and uses your Cloud Run application as the push endpoint.
upvoted 0 times
...
Johnna
10 months ago
D) 1. Deploy your application on Cloud Run on GKE with the connectivity set to Internal.2. Create a Cloud Pub/Sub subscription for that topic.3. In the same Google Kubernetes Engine cluster as your application, deploy a container that takes the messages and sends them to your application.
upvoted 0 times
...
Maybelle
10 months ago
B) 1. Grant the Pub/Sub Subscriber role to the service account used by Cloud Run.2. Create a Cloud Pub/Sub subscription for that topic.3. Make your application pull messages from that subscription.
upvoted 0 times
...
Elly
10 months ago
C) 1. Create a service account.2. Give the Cloud Run Invoker role to that service account for your Cloud Run application.3. Create a Cloud Pub/Sub subscription that uses that service account and uses your Cloud Run application as the push endpoint.
upvoted 0 times
...
Mari
10 months ago
B) 1. Grant the Pub/Sub Subscriber role to the service account used by Cloud Run.2. Create a Cloud Pub/Sub subscription for that topic.3. Make your application pull messages from that subscription.
upvoted 0 times
...
...
Sarah
11 months ago
D seems a bit overkill, don't you think? Why bring in a whole GKE cluster just to connect Pub/Sub to Cloud Run? B or C are cleaner options.
upvoted 0 times
Tasia
10 months ago
Yeah, B or C would be simpler and more straightforward to implement.
upvoted 0 times
...
Bronwyn
11 months ago
I agree, D does seem like overkill. B or C are definitely cleaner options.
upvoted 0 times
...
...
Amie
11 months ago
I'm not sure, but option C also sounds like a good approach. Creating a service account and giving the Cloud Run Invoker role seems like a valid method.
upvoted 0 times
...
Kristian
11 months ago
I like C - using a service account to connect Cloud Run and Pub/Sub is a nice touch. Keeps things secure and manageable.
upvoted 0 times
...
Leota
11 months ago
B sounds like the way to go. Keeping the Pub/Sub subscription and Cloud Run application separate is a good practice.
upvoted 0 times
...
Dacia
11 months ago
I agree with Catarina. Option B seems like the most straightforward and secure way to deploy the application on Cloud Run.
upvoted 0 times
...
Catarina
11 months ago
I think option B is the best choice. It follows Google-recommended practices by granting the Pub/Sub Subscriber role to the service account used by Cloud Run.
upvoted 0 times
...

Save Cancel