Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam MuleSoft Platform Architect I Topic 7 Question 27 Discussion

Actual exam question for Salesforce's MuleSoft Platform Architect I exam
Question #: 27
Topic #: 7
[All MuleSoft Platform Architect I Questions]

A System API is designed to retrieve data from a backend system that has scalability challenges. What API policy can best safeguard the backend system?

Show Suggested Answer Hide Answer
Suggested Answer: A, C

To accommodate the new requirement of allowing updates to existing quotes, the following actions should be taken:

Update the RAML Definition (Option C):

The RAML specification defines the structure and behavior of the API. Adding a new method (such as PUT or PATCH) for updating quotes requires modifying the RAML to include this new endpoint. This ensures the API specification is up-to-date and accurately reflects the new functionality.

Update the API Implementation (Option A):

Once the RAML is updated, the backend API implementation must also be modified to handle the new update requests. This could involve adding logic to process and validate update requests, connect to necessary backend resources, and apply the changes to existing quotes.

of Incorrect Options:

Option B (removing and creating new clients) is unnecessary; client applications can remain as they are, with no need for complete replacement.

Option D (deprecating existing versions) may not be required if backward compatibility is maintained.

Option E (adding a new policy) does not facilitate functional changes and is unrelated to implementing the update feature.

Reference For more details on updating RAML definitions and API implementations, refer to MuleSoft's API Design documentation on RAML and RESTful API practices.


Contribute your Thoughts:

Lenna
5 days ago
Client ID enforcement sounds like a good option. It'll let us identify individual clients and manage their access accordingly.
upvoted 0 times
...
Linsey
10 days ago
I think IP whitelist could also be a good option to safeguard the backend system.
upvoted 0 times
...
Lemuel
11 days ago
I think SLA-based rate limiting is the way to go. It'll help protect the backend system from being overwhelmed without being too restrictive on users.
upvoted 0 times
...
Justa
12 days ago
I agree with Francisca, SLA-based rate limiting can help manage the scalability challenges.
upvoted 0 times
...
Francisca
13 days ago
I think the best policy would be SLA-based rate limiting.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77