Exam MCIA - Level 1 topic 1 question 14 discussion

Actual exam question from Mulesoft's MCIA - Level 1

Question #: 14
Topic #: 1

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?

A. Use MUnit to simulate standard responses from the backend system Then conduct performance tests to identify other bottlenecks in the system
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
C. Conduct scaled-down performance tests in the staging environment against the rate limited backend system Then upscale performance results to full production scale
D. Include logic within the API implementation that bypasses invocations of the backend system in a performance test situation, instead invoking local stubs that replicate typical backend system responses Then conduct performance tests using this API implementation

Show Suggested Answer

Suggested Answer: B 🗳️

by Kazzman at Aug. 6, 2021, 6:50 a.m.

Comments

Submit Cancel

Pavan_Nagineni

Highly Voted 3 years, 10 months ago

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

upvoted 7 times

...

Alandt

Most Recent 1 year ago

Selected Answer: B

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.

upvoted 1 times

...

vikas_mule

1 year, 4 months ago

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

upvoted 1 times

...

anupamgogoi

2 years, 2 months ago

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

upvoted 1 times

...

godricravenclaw

2 years, 4 months ago

Selected Answer: C

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).

upvoted 1 times

...