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
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Google Exam Professional-Cloud-Developer Topic 1 Question 79 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 79
Topic #: 1
[All Professional Cloud Developer Questions]

You need to load-test a set of REST API endpoints that are deployed to Cloud Run. The API responds to HTTP POST requests Your load tests must meet the following requirements:

* Load is initiated from multiple parallel threads

* User traffic to the API originates from multiple source IP addresses.

* Load can be scaled up using additional test instances

You want to follow Google-recommended best practices How should you configure the load testing'?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Eden at Apr 12, 2024, 04:02 AM

Limited Time Offer

25%

Off

Get Premium Professional-Cloud-Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Tamala
4 months ago
You're right, Tequila. Option C does seem to provide more flexibility in scaling up the load. Let's stick with that.
upvoted 0 times
...
Tequila
4 months ago
But doesn't option D limit our ability to scale up the load using additional test instances?
upvoted 0 times
...
Hui
4 months ago
I would go with option D instead. Downloading a container image on Cloud Shell seems more efficient to me.
upvoted 0 times
...
Tamala
4 months ago
I agree with Tequila. Option C seems to be the best choice for following Google-recommended best practices.
upvoted 0 times
...
Tequila
4 months ago
I think we should go with option C because it allows us to deploy additional Pods as needed and support more concurrent users.
upvoted 0 times
...
Ilona
4 months ago
I'm leaning towards option A. Using cURL and deploying the image in a managed instance group for each VM seems like a robust solution to me.
upvoted 0 times
...
Fletcher
5 months ago
I agree with Emily. Option D sounds simpler and easier to manage. Plus, it allows for easily increasing the load on the API.
upvoted 0 times
...
Sharee
5 months ago
I disagree, Alex. Option D seems like a more straightforward approach. Just download the container image and start multiple instances on Cloud Shell.
upvoted 0 times
...
Maia
5 months ago
I think option C is the best choice. Using a distributed load testing framework on a private GKE cluster seems like a scalable and efficient solution.
upvoted 0 times
...
Jamika
6 months ago
Hmm, I see what you mean about option D being simpler, but I'm not sure it would really meet all the requirements. Sequentially starting instances on Cloud Shell doesn't seem like it would give us the parallel threads and multiple IP addresses that the question calls for. I think C is still the way to go, even if it's a bit more complex.
upvoted 0 times
...
Iraida
6 months ago
I'm with you on the GKE approach. That seems like the most flexible and scalable option here. Plus, we can leverage all the built-in monitoring and autoscaling features of Kubernetes to really dial in the load testing.
upvoted 0 times
...
Krystal
6 months ago
I'm a little hesitant about option C, though. Setting up a private GKE cluster just for load testing seems a bit overkill, don't you think? I'm wondering if option D might be a simpler solution - just use the distributed load testing framework container on Cloud Shell to get the job done.
upvoted 0 times
...
Lelia
6 months ago
Yeah, I agree that C seems like the best option. The requirements specifically mention needing to load test from multiple parallel threads and multiple source IP addresses. A managed instance group with cURL doesn't sound like it would give us that kind of flexibility.
upvoted 0 times
...
Madalyn
6 months ago
Haha, can you imagine trying to scale up the load by just starting more instances of the container in Cloud Shell? That's like trying to put out a forest fire with a squirt gun!
upvoted 0 times
Lili
6 months ago
C) Deploy a distributed load testing framework on a private Google Kubernetes Engine Cluster Deploy additional Pods as needed to initiate more traffic and support the number of concurrent users.
upvoted 0 times
...
Susana
6 months ago
A) Create an image that has cURL installed and configure cURL to run a test plan Deploy the image in a managed instance group, and run one instance of the image for each VM.
upvoted 0 times
...
...
Reyes
6 months ago
The Cloud Shell option sounds kind of janky to me. I can't imagine that would be a very reliable or robust way to load-test the API. I think we need to go with a more enterprise-grade solution here.
upvoted 0 times
...
Tresa
6 months ago
Whoa, this question is really tricky! I'm not sure exactly how to approach it, but I think option C might be the way to go. Using a distributed load testing framework on a private GKE cluster seems like it would give us the ability to scale up the load and simulate traffic from multiple IP addresses.
upvoted 0 times
Dion
5 months ago
User 1
upvoted 0 times
...
...
Joye
6 months ago
Hmm, this is tricky. I'm not sure if I'd go with the cURL approach, since that seems a bit manual and not very scalable. I'm leaning towards the distributed load testing framework on GKE, but I'd need to do some more research to make sure that's the right approach.
upvoted 0 times
...
Nelida
6 months ago
I agree, this is a solid question. I think it's important to follow Google's best practices here, since they're the experts on Cloud Run and have a lot of experience with it.
upvoted 0 times
...
Oneida
6 months ago
This is a great question! I'm really interested to see how we can properly load-test these REST API endpoints on Cloud Run. The requirements around parallel threads, multiple source IP addresses, and scalability are all really important considerations.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77