Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam - Topic 7 Question 27 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) exam

Question #: 27
Topic #: 7

[All Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) 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?

AIPwhitelist

BSLA-based rate limiting

CAuth 2 token enforcement

DClient ID enforcement

Show Suggested 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.

by Belen at Mar 20, 2025, 08:28 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Katheryn

4 months ago

Totally agree with SLA-based rate limiting, it’s essential for scalability!

upvoted 0 times

...

Paulina

4 months ago

Wait, can you really rely on Auth 2 tokens for this? Seems risky.

upvoted 0 times

...

Jennifer

5 months ago

Client ID enforcement? Not sure that’s enough to protect against overload.

upvoted 0 times

...

Malika

5 months ago

I think IP whitelist could work too, but it's not as flexible.

upvoted 0 times

...

Jonell

5 months ago

SLA-based rate limiting is definitely the way to go!

upvoted 0 times

...

Camellia

5 months ago

Client ID enforcement sounds familiar, but I’m not convinced it’s the best for safeguarding against scalability challenges. I might lean towards rate limiting instead.

upvoted 0 times

...

Leslee

5 months ago

I practiced a similar question where rate limiting was emphasized as a way to manage traffic. I feel like it’s the right choice for this scenario too.

upvoted 0 times

...

Wilda

6 months ago

I'm not entirely sure, but I remember something about IP whitelisting being useful for security. However, it might not address scalability issues directly.

upvoted 0 times

...

Raymon

6 months ago

I think SLA-based rate limiting could be the best option here since it helps control the number of requests and protects the backend from being overwhelmed.

upvoted 0 times

...

Ligia

6 months ago

I've got a good feeling about this one. IP whitelisting would limit access to authorized clients, while Auth 2 token enforcement and client ID enforcement provide additional security layers. But for scalability, SLA-based rate limiting seems like the way to go.

upvoted 0 times

...

Arlen

6 months ago

Okay, let's see. The backend system has scalability challenges, so we need a policy that can handle high traffic without overloading the system. I'm leaning towards SLA-based rate limiting as the best option.

upvoted 0 times

...

Audrie

6 months ago

Hmm, I'm a bit unsure about this one. I'll need to think through the different API security policies and how they impact scalability. Gotta make sure I pick the right answer.

upvoted 0 times

...

Jessenia

7 months ago

This seems like a straightforward API security question. I'll focus on identifying the policy that best protects the backend system from scalability challenges.

upvoted 0 times

...

Christene

11 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

11 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

Rosann

10 months ago

C: Client ID enforcement could also be a good option to consider for added security measures.

upvoted 0 times

...

Elmira

10 months ago

B: I agree, IP whitelisting might seem secure but it can cause more harm than good.

upvoted 0 times

...

Gilma

11 months ago

A: SLA-based rate limiting is definitely the best option to safeguard the backend system.

upvoted 0 times

...

Ciara

12 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

10 months ago

Client ID enforcement could also work, but IP whitelisting is the simplest solution.

upvoted 0 times

...

Stefanie

10 months ago

I agree, using Auth 2 token enforcement might be too much for just retrieving data.

upvoted 0 times

...

Stephaine

11 months ago

IP whitelisting is definitely the way to go. It's simple and effective.

upvoted 0 times

...

Lenna

1 year 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

12 months ago

SLA-based rate limiting can help ensure that the backend system is not overwhelmed with requests.

upvoted 0 times

...

Amie

12 months ago

IP whitelist could also be useful to restrict access to only approved IP addresses.

upvoted 0 times

...

Gladys

12 months ago

I agree, having client IDs will help us track and control access to the backend system.

upvoted 0 times

...

Sharita

12 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

1 year ago

I think IP whitelist could also be a good option to safeguard the backend system.

upvoted 0 times

...

Lemuel

1 year 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