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 Exam Professional-Cloud-Developer Topic 8 Question 90 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 90
Topic #: 8
[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

Contribute your Thoughts:

Portia
12 days ago
I'd have to say C is the way to go. Leveraging a distributed load testing framework on GKE is the most Google-approved and scalable solution.
upvoted 0 times
Basilia
2 days ago
That sounds like a solid plan. It's always good to follow Google's recommendations.
upvoted 0 times
...
Annmarie
8 days 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
...
...
Ashlyn
24 days ago
Personally, I think C is the best choice. It ticks all the boxes - parallel threads, multiple source IPs, and scalability. Can't go wrong with that.
upvoted 0 times
Stefania
13 days ago
I think option D could also work well, starting multiple instances on Cloud Shell could be efficient.
upvoted 0 times
...
Vivan
15 days ago
I agree, option C seems like the most comprehensive choice for load testing.
upvoted 0 times
...
...
Mira
1 months ago
Haha, using Cloud Shell to run load tests? That's like trying to power a rocket with a AA battery. C is the clear winner here.
upvoted 0 times
Leota
13 days 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
...
Jovita
18 days 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
...
...
Phuong
1 months ago
I agree, C seems like the most appropriate option. Deploying on a private GKE cluster gives you the flexibility to handle the load requirements.
upvoted 0 times
...
Gracia
1 months ago
C is definitely the way to go. Using a distributed load testing framework on GKE aligns with the Google-recommended best practices and allows for easy scaling of the load.
upvoted 0 times
Moon
10 days ago
That makes sense. It's important to follow best practices when load testing REST API endpoints on Cloud Run.
upvoted 0 times
...
Adell
12 days ago
I agree, deploying additional Pods on GKE is a scalable solution for load testing.
upvoted 0 times
...
Valentin
22 days ago
C is definitely the way to go. Using a distributed load testing framework on GKE aligns with the Google-recommended best practices and allows for easy scaling of the load.
upvoted 0 times
...
...
Helga
2 months ago
I'm not sure about option D. Downloading a container image on Cloud Shell and starting several instances sequentially may not be as scalable as deploying on a Kubernetes Engine Cluster.
upvoted 0 times
...
Marylou
2 months ago
I agree with Clay. Option C seems like the most efficient way to configure the load testing while following Google-recommended best practices.
upvoted 0 times
...
Clay
2 months ago
I think option C is the best choice. Deploying a distributed load testing framework on a private Google Kubernetes Engine Cluster allows for scalability and flexibility.
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