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:

Christene
1 months ago
I'm going with Auth 2 token enforcement. It may be a bit more complex, but it'll give us granular control over who can access the API. Plus, it's the most 'buzzword-compliant' option. *winks*
upvoted 0 times
...
Rana
1 months ago
SLA-based rate limiting is the way to go, but I bet half the candidates will choose IP whitelisting because it sounds the most secure. *laughs* Little do they know, it's a security nightmare waiting to happen.
upvoted 0 times
Gilma
16 days ago
A: SLA-based rate limiting is definitely the best option to safeguard the backend system.
upvoted 0 times
...
...
Ciara
2 months ago
Auth 2 token enforcement? That's overkill for a simple data retrieval API. Let's keep it simple with IP whitelisting.
upvoted 0 times
Rosalyn
4 days ago
Client ID enforcement could also work, but IP whitelisting is the simplest solution.
upvoted 0 times
...
Stefanie
9 days ago
I agree, using Auth 2 token enforcement might be too much for just retrieving data.
upvoted 0 times
...
Stephaine
22 days ago
IP whitelisting is definitely the way to go. It's simple and effective.
upvoted 0 times
...
...
Lenna
2 months ago
Client ID enforcement sounds like a good option. It'll let us identify individual clients and manage their access accordingly.
upvoted 0 times
Lettie
1 months ago
SLA-based rate limiting can help ensure that the backend system is not overwhelmed with requests.
upvoted 0 times
...
Amie
1 months ago
IP whitelist could also be useful to restrict access to only approved IP addresses.
upvoted 0 times
...
Gladys
2 months ago
I agree, having client IDs will help us track and control access to the backend system.
upvoted 0 times
...
Sharita
2 months 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
2 months ago
I think IP whitelist could also be a good option to safeguard the backend system.
upvoted 0 times
...
Lemuel
2 months 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
Haydee
30 days ago
I think IP whitelist could also be a good option to restrict access to only trusted sources.
upvoted 0 times
...
Candra
1 months ago
I agree, SLA-based rate limiting is a good choice. It can help manage the traffic to prevent overload.
upvoted 0 times
...
...
Justa
2 months ago
I agree with Francisca, SLA-based rate limiting can help manage the scalability challenges.
upvoted 0 times
...
Francisca
2 months ago
I think the best policy would be SLA-based rate limiting.
upvoted 0 times
...

Save Cancel