New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam - Topic 5 Question 38 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) exam
Question #: 38
Topic #: 5
[All Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Questions]

An organization wants to make sure only known partners can invoke the organization's APIs. To achieve this security goal, the organization wants to enforce a Client ID Enforcement policy in API Manager so that only registered partner applications can invoke the organization's APIs. In what type of API implementation does MuleSoft recommend adding an API proxy to enforce the Client ID Enforcement policy, rather than embedding the policy directly in the application's JVM?

Show Suggested Answer Hide Answer
Suggested Answer: D

Correct Answe r: A Non-Mule application

*****************************************

>> All type of Mule applications (Mule 3/ Mule 4/ with APIkit/ with Custom Java Code etc) running on Mule Runtimes support the Embedded Policy Enforcement on them.

>> The only option that cannot have or does not support embedded policy enforcement and must have API Proxy is for Non-Mule Applications.

So, Non-Mule application is the right answer.


Contribute your Thoughts:

0/2000 characters
Glory
4 days ago
I'm going with B. Modifying the Mule 3 or Mule 4 application with custom Java code could also work.
upvoted 0 times
...
Chaya
9 days ago
Definitely C. Embedding the policy directly in the application's JVM seems like a bad idea.
upvoted 0 times
...
Sharen
14 days ago
I think the answer is C. A Mule 4 application with an API specification makes the most sense for enforcing the Client ID Enforcement policy.
upvoted 0 times
...
Thaddeus
19 days ago
I recall that using an API proxy is generally recommended for non-Mule applications, but I can't remember if that applies here. Maybe option D?
upvoted 0 times
...
Fabiola
25 days ago
I’m a bit confused about the differences between Mule 3 and Mule 4 applications in this context. Does it really matter which version we choose?
upvoted 0 times
...
Lenora
30 days ago
I practiced a similar question where we had to decide on API proxies versus embedding policies. I feel like it might be related to option C.
upvoted 0 times
...
Kerry
1 month ago
I think I remember something about API proxies being more flexible for security policies, but I'm not sure which option fits that best.
upvoted 0 times
...
Eladia
1 month ago
I've got a strategy - I'll carefully read through each answer option and think about the tradeoffs of the different API implementation types. That should help me identify the one where MuleSoft recommends using a proxy.
upvoted 0 times
...
Yuette
2 months ago
Based on my understanding, the proxy approach is recommended when you want to centralize the enforcement of the policy, rather than having it distributed across multiple applications. I think that's the key distinction here.
upvoted 0 times
...
Nickolas
2 months ago
I'm a bit confused by the wording of the question. What's the difference between embedding the policy directly in the application's JVM and using an API proxy? I'll need to review that concept.
upvoted 0 times
...
Louvenia
2 months ago
Okay, let me see. The question is asking about the type of API implementation where we should use a proxy to enforce the Client ID Enforcement policy. I think I need to consider the differences between the Mule 3, Mule 4, and non-Mule options.
upvoted 0 times
...
Deonna
2 months ago
Hmm, this seems like a security-related question. I'll need to think carefully about the different API implementation types and where MuleSoft recommends adding the proxy.
upvoted 0 times
...

Save Cancel