MuleSoft Certified Platform Architect - Level 1 MAINTENANCE
Last Update Feb 6, 2023
Total Questions : 80
Why Choose ClapGeek
Average Score In Real
Exam At Testing Centre
Questions came word by
word from this dump
Try a free demo of our MuleSoft MCPA-Level-1-Maintenance PDF and practice exam software before the purchase to get a closer look at practice questions and answers.
We provide up to 3 months of free after-purchase updates so that you get MuleSoft MCPA-Level-1-Maintenance practice questions of today and not yesterday.
We have a long list of satisfied customers from multiple countries. Our MuleSoft MCPA-Level-1-Maintenance practice questions will certainly assist you to get passing marks on the first attempt.
ClapGeek offers MuleSoft MCPA-Level-1-Maintenance PDF questions, web-based and desktop practice tests that are consistently updated.
ClapGeek has a support team to answer your queries 24/7. Contact us if you face login issues, payment and download issues. We will entertain you as soon as possible.
Thousands of customers passed the MuleSoft Designing MuleSoft Azure Infrastructure Solutions exam by using our product. We ensure that upon using our exam products, you are satisfied.
What is a best practice when building System APIs?
Correct Answer: Model all API resources and methods to closely mimic the operations of the backend system.
>> There are NO fixed and straight best practices while opting data models for APIs. They are completly contextual and depends on number of factors. Based upon those factors, an enterprise can choose if they have to go with Enterprise Canonical Data Model or Bounded Context Model etc.
>> One should NEVER expose the technical details of API implementation to their API clients. Only the API interface/ RAML is exposed to API clients.
>> It is true that the RAML definitions of APIs should be as detailed as possible and should reflect most of the documentation. However, just that is NOT enough to call your API as best documented API. There should be even more documentation on Anypoint Exchange with API Notebooks etc. to make and create a developer friendly API and repository..
>> The best practice always when creating System APIs is to create their API interfaces by modeling their resources and methods to closely reflect the operations and functionalities of that backend system.
A new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity.
The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms.
If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API's desired SLA?
Correct Answer: Set a timeout of 100ms; that leaves 400ms for other two downstream APIs to complete
Key details to take from the given scenario:
>> Upstream API's designed SLA is 500ms (median). Lets ignore maximum SLA response times.
>> This API calls 3 downstream APIs sequentially and all these are of similar complexity.
>> The first downstream API is offering median SLA of 100ms, 80th percentile: 500ms; 95th percentile: 1000ms.
Based on the above details:
>> We can rule out the option which is suggesting to set 50ms timeout. Because, if the median SLA itself being offered is 100ms then most of the calls are going to timeout and time gets wasted in retried them and eventually gets exhausted with all retries. Even if some retries gets successful, the remaining time wont leave enough room for 2nd and 3rd downstream APIs to respond within time.
>> The option suggesting to NOT set a timeout as the invocation of this API is mandatory and so we must wait until it responds is silly. As not setting time out would go against the good implementation pattern and moreover if the first API is not responding within its offered median SLA 100ms then most probably it would either respond in 500ms (80th percentile) or 1000ms (95th percentile). In BOTH cases, getting a successful response from 1st downstream API does NO GOOD because already by this time the Upstream API SLA of 500 ms is breached. There is no time left to call 2nd and 3rd downstream APIs.
>> It is NOT true that no timeout is possible to meet the upstream APIs desired SLA.
As 1st downstream API is offering its median SLA of 100ms, it means MOST of the time we would get the responses within that time. So, setting a timeout of 100ms would be ideal for MOST calls as it leaves enough room of 400ms for remaining 2 downstream API calls.
An Anypoint Platform organization has been configured with an external identity provider (IdP) for identity management and client management. What credentials or token must be provided to Anypoint CLI to execute commands against the Anypoint Platform APIs?
Correct Answer: The credentials provided by the IdP for identity management