MCIA - Level 1 Exam QuestionsBrowse all questions from this exam

MCIA - Level 1 Exam - Question 14


Refer to the exhibit. One of the backend systems invoked by an API implementation enforces rate limits on the number of requests a particular client can make.

Both the backend system and the API implementation are deployed to several non-production environments in addition to production.

Rate limiting of the backend system applies to all non-production environments. The production environment, however, does NOT have any rate limiting.

What is the most effective approach to conduct performance tests of the API implementation in a staging (non-production) environment?

Show Answer
Correct Answer: B

To conduct effective performance tests in a non-production environment that has rate limits, creating a mocking service that replicates the backend system's production performance characteristics is the best approach. This allows the API implementation to be tested under conditions that closely match the production environment, without being hindered by the rate limits. This method ensures that the performance tests realistically simulate the actual production environment, providing accurate performance metrics.

Discussion

11 comments
Sign in to comment
Pavan_NagineniOption: B
Aug 27, 2021

B. Create a mocking service that replicates the backend system's production performance characteristics Then configure the API implementation to use the mocking service and conduct the performance tests

KazzmanOption: B
Aug 6, 2021

Correct answer should be B

sanni27Option: C
Jan 11, 2022

Should be C, because the scale down performance test always happens in production identical environment. Here it is staging environment.

Outdoor25Option: B
Dec 29, 2021

Should be B.

rodriguescontOption: B
Jun 27, 2022

Sounds B, but I just not figured out how the mocking service feature could help regarding the lack of rating limit on the backend in production

godricravenclaw
Feb 9, 2023

Agree that it is B. As for the mocking service, it will behave like in production since the mocking service will not have rate limiting.

madgeezerOption: B
Aug 4, 2022

B. Create a mocking service that replicates the backend system's production performance characteristics Then configure the API implementation to use the mocking service and conduct the performance tests

majda091983Option: C
Nov 22, 2022

could not be B because it implies to touch the API implementation

godricravenclawOption: C
Feb 9, 2023

D requires a code change which is not advisable because it will not be deployed in production and will affect the performance results (even though it might be milliseconds only).

anupamgogoiOption: C
Apr 25, 2023

It should be C. We should have a PRODLIKE environment where we can test the functionality. Mock is not a good idea

vikas_muleOption: C
Feb 13, 2024

C is correct, The production environment, however, does NOT have any rate limiting. so no need to conduct rate limiting performance test in staging.

AlandtOption: B
Jun 18, 2024

ChatGPT: The most effective approach is: B. Create a mocking service that replicates the backend system's production performance characteristics. Then configure the API implementation to use the mocking service and conduct the performance tests. This approach ensures realistic performance testing by bypassing non-production rate limits, simulating production-like conditions, and providing control and flexibility to accurately assess the API implementation's performance.