ExamTopics Logo
Mail Us[email protected]
Menu
Google Discussions
exam questions

Exam Professional Cloud Developer All Questions

View all questions & answers for the Professional Cloud Developer exam
Go to Exam

Exam Professional Cloud Developer topic 1 question 255 discussion

Actual exam question from Google's Professional Cloud Developer
Question #: 255
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?

  • 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.
  • B. Create an image that has cURL installed, and configure cURL to run a test plan. Deploy the image in an unmanaged instance group, and run one instance of the image for each VM.
  • 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.
  • D. Download the container image of a distributed load testing framework on Cloud Shell. Sequentially start several instances of the container on Cloud Shell to increase the load on the API.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️
by TNT87 at Feb. 1, 2023, 12:04 a.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
JonathanSJ
9 months ago
Selected Answer: C
I will go for C.
upvoted 1 times
...
purushi
1 year, 2 months ago
Selected Answer: C
Requirements are very clear. Load testing with concurrent users/threads + Multiple source origins/IP address, C is the best choice.
upvoted 1 times
purushi
1 year, 2 months ago
Option D is closer but we cannot instantiate the mutliple requests with different IP addresses.
upvoted 1 times
...
...
NewComer200
1 year, 5 months ago
Selected Answer: D
It's normal to launch some compute engine from cloud shell. I think we can increase right load by increasing Compute Engine which do load-test from Cloud Shell step by step. Can the test from GKE cover the condition which is "from multiple source IP addresses.".
upvoted 1 times
NewComer200
1 year, 5 months ago
I feel that load testing from the Compute Engine is more accurate than load testing from the Pod. I'm not sure what to think. Is it possible that GKE's engress is a bottleneck and load testing is not possible?
upvoted 1 times
...
...
mrvergara
1 year, 9 months ago
Selected Answer: C
Option D, which involves starting several instances of a load testing framework container on Cloud Shell, may not be a recommended approach for several reasons: Cloud Shell is a shell environment for managing resources hosted on Google Cloud and does not provide a scalable infrastructure for running load tests. Starting several instances of a container on Cloud Shell is not a highly available or scalable solution for load testing, and may not provide sufficient parallelism or control over the source IP addresses of the traffic. Using a private Google Kubernetes Engine cluster to deploy a distributed load testing framework allows for scaling up the load testing by deploying additional Pods, which can provide more control over the number of concurrent users and the source IP addresses of the traffic, and can provide a more robust and scalable infrastructure for load testing.
upvoted 3 times
NewComer200
1 year, 5 months ago
"Cloud Shell is a shell environment for managing resources hosted on Google Cloud and does not provide a scalable infrastructure for running load tests." I agree with this explanation. But "Starting several instances of a container on Cloud Shell is not a highly available or scalable solution for load testing, and may not provide sufficient parallelism or control over the source IP addresses of the traffic." I can't agree with this explanation. Please teach me where this explanation is written. It's normal to launch some compute engine from cloud shell. I think we can increase right load by increasing Compute Engine which do load-test from Cloud Shell step by step. Can the test from GKE cover the condition which is "from multiple source IP addresses.". I think this question's answer is D.
upvoted 1 times
...
...
TNT87
1 year, 9 months ago
Selected Answer: D
nope Answer is D....not C
upvoted 1 times
TNT87
1 year, 9 months ago
https://cloud.google.com/run/docs/about-load-testing
upvoted 1 times
...
...
TNT87
1 year, 9 months ago
Selected Answer: C
To deploy the load testing tasks, you do the following: Deploy a load testing master. Deploy a group of load testing workers. With these load testing workers, you can create a substantial amount of traffic for testing purposes. https://cloud.google.com/run/docs/about-load-testing https://cloud.google.com/architecture/distributed-load-testing-using-gke#build_the_container_image Answer
upvoted 1 times
TNT87
1 year, 9 months ago
This tutorial explains how to use Google Kubernetes Engine (GKE) to deploy a distributed load testing framework that uses multiple containers to create traffic for a simple REST-based API. This tutorial load-tests a web application deployed to App Engine that exposes REST-style endpoints to respond to incoming HTTP POST requests.
upvoted 1 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago