Your team is developing a web application that will be deployed on Google Kubernetes Engine (GKE). Your CTO expects a successful launch and you need to ensure your application can handle the expected load of tens of thousands of users. You want to test the current deployment to ensure the latency of your application stays below a certain threshold. What should you do?
To ensure your application can handle the expected load and that latency remains below a certain threshold, you should use a load testing tool to simulate the expected number of concurrent users and total requests to your application, and then inspect the results. Load testing provides actionable insights into how your application performs under stress, allowing you to identify and address performance bottlenecks before the actual deployment.
21 NEw Qs - July 12, 2021 # 15. An application development team has come to you for advice.They are planning to write and deploy an HTTP(S) API using Go 1.12. The API will have a very unpredictable workload and must remain reliable during peaks in traffic. They want to minimize operational overhead for this application. What approach should you recommend? a. Use a Managed Instance Group when deploying to Compute Engine b. Develop an application with containers, and deploy to Google Kubernetes Engine (GKE) c. Develop the application for App Engine standard environment d. Develop the application for App Engine Flexible environment using a custom runtime Answer C, , please share you answers
C is ok.
Answer A
Sorry C
Answer is C
C. Unpredictable workload. Flexible does not scale nearly as fast as standard.
Anyone can tell please if at the new exam there are also questions from the old set(before question 115)?
old ones are not removed
really ? the old ones are are still on exam ? from 1-100 ? how about old case study questions ?
The correct answer is: A. Use a load testing tool to simulate the expected number of concurrent users and total requests to your application, and inspect the results. A load testing tool can be used to simulate the expected number of concurrent users and total requests to your application. This will allow you to test how your application handles the expected load and to identify any potential problems. Enabling autoscaling on the GKE cluster and enabling horizontal pod autoscaling on your application deployments will not help you to test the latency of your application. This will only help to ensure that your application can handle the expected load.
The question specifically asks that your CTO expects a successful launch and you need to ensure your application can handle the expected load of tens of thousands of users. In A, you are just testing and not taking an action. In B, you are not only testing with curl commands to check for latency but also taking action to enable the cluster to acquire more resources. So, I will go with B.
Also, there is no expected numbers, the users can be tens of thousands so whatever testing you do with A may not be sufficient so it's better to keep autoscaling for whatsoever load comes in and curl test ensures autoscaling happens when required
Admin should really deleting the wrong answers.. I think 90% of people here just copying explanations and really have no idea what they are talking about. every second question has different answer with different "voting"answer..
I was going for B. However analyzing question it says "test the current deployment to ensure the latency" The only test answer is the stress test / performance test simulating the users workload.
Ans A: the question asks you want to test
A is the correct, no load ==> no latency checking
A is ok
A is the correct answer
is curl returns latency info?
It is A. You want to TEST the deployment, not changing anything (yet).
Using Curl seems weird, how is Curl going to inject the load? Curl would be fine if we just wanted to test the underlying latency of the system.
IMO, something here should be a multiple-choice option, and the examinee should have selected A and B. Otherwise, I am picking option A.
A is correct, jmeter, k6
Test current status, load test tools only purpouse is to test load and consider success/failure based on latency / response times.