MENU
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'?
Suggested Answer: C
Get Premium Professional Cloud Developer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
38 comments · newest first
JU
Junita
11 months ago
Definitely going with C, it's the most flexible approach!
BR
Brianne
11 months ago
Wait, can Cloud Shell really handle that much load?
SH
Sherill
11 months ago
Unmanaged instance groups? Not sure that's the best choice.
TW
Twana
11 months ago
I think A is more straightforward though.
LI
Lindsey
12 months ago
Option C sounds solid for scaling up traffic.
EM
Emerson
12 months ago
I practiced a similar question where we had to consider multiple IP addresses for traffic. I wonder if that impacts which option is better here.
CO
Cortney
1 year ago
I feel like option D might not scale well since it's using Cloud Shell, but I can't remember the specifics of why that might be a problem.
CA
Carmen
1 year ago
I think using cURL is a common practice for load testing, but I can't recall the difference between managed and unmanaged instance groups.
OL
Olene
1 year ago
I remember we discussed using Kubernetes for load testing in class, so option C sounds familiar, but I'm not sure if it's the best choice for this scenario.
DO
Dorthy
1 year ago
Okay, I think I've got a handle on this. The distributed load testing framework in option C sounds like the way to go. That way I can easily scale up the number of concurrent users by deploying more Pods. Plus, it's running on a private GKE cluster, which should give me more control and flexibility.
TH
Theodora
1 year ago
Hmm, I'm a bit unsure about this one. The requirements mention scaling up the load using additional test instances, but I'm not sure if the other options fully address that. I might need to do some more research on the different load testing frameworks and how they can be deployed.
LA
Laurel
1 year ago
This looks like a pretty straightforward load testing scenario. I think the key is to follow Google's best practices, so I'm leaning towards option C - deploying a distributed load testing framework on a private GKE cluster.
PA
Paris
1 year ago
I'm a little confused by the difference between managed and unmanaged instance groups in options A and B. I'm not sure which one would be better for this use case. Maybe I should look into the pros and cons of each approach before deciding.
AJ
Aja
1 year ago
Hmm, I'm not totally sure about this one. The GDPR mentions data portability, but I'm not clear on the exact objective. I'll have to think this through carefully.
SU
Suzan
1 year ago
I'm a bit lost on this one. The details in the answer choices are pretty specific, and I'm not super familiar with the terminology. I'll have to guess and hope for the best.
MA
Marg
1 year ago
Ah, I know this one! Business continuity programs should be part of the Governance process. That's the area that oversees the organization's overall direction and decision-making.
TA
Tamala
2 years ago
You're right, Tequila. Option C does seem to provide more flexibility in scaling up the load. Let's stick with that.
TE
Tequila
2 years ago
But doesn't option D limit our ability to scale up the load using additional test instances?
HU
Hui
2 years ago
I would go with option D instead. Downloading a container image on Cloud Shell seems more efficient to me.
TA
Tamala
2 years ago
I agree with Tequila. Option C seems to be the best choice for following Google-recommended best practices.
TE
Tequila
2 years ago
I think we should go with option C because it allows us to deploy additional Pods as needed and support more concurrent users.
IL
Ilona
2 years 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.
FL
Fletcher
2 years ago
I agree with Emily. Option D sounds simpler and easier to manage. Plus, it allows for easily increasing the load on the API.
SH
Sharee
2 years ago
I disagree, Alex. Option D seems like a more straightforward approach. Just download the container image and start multiple instances on Cloud Shell.
MA
Maia
2 years 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.
JA
Jamika
3 years 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.
IR
Iraida
3 years 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.
KR
Krystal
3 years 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.
LE
Lelia
3 years 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.
MA
Madalyn
3 years 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!
LI
Lili
3 years 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.
SU
Susana
3 years 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.
RE
Reyes
3 years 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.
TR
Tresa
3 years 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.
DI
Dion
2 years ago
User 1
JO
Joye
3 years 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.
NE
Nelida
3 years 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.
ON
Oneida
3 years 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.