Cyber Monday 2024! 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 5 Question 15 Discussion

Actual exam question for Salesforce's MuleSoft Platform Architect I exam
Question #: 15
Topic #: 5
[All MuleSoft Platform Architect I 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 Answer : 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:

Vallie
2 months ago
Haha, good one Verda! This question is making my head spin. Maybe we should just ask the API to tell us the answer.
upvoted 0 times
...
Verda
2 months ago
I don't know, guys. Isn't this just a fancy way of saying 'Use the force, Luke'? I'm going to need more technical details to make a decision here.
upvoted 0 times
...
Glendora
2 months ago
I'm gonna go with B. Modifying a Mule 3 or 4 app with custom Java code gives you more flexibility to handle the policy enforcement.
upvoted 0 times
Nenita
7 days ago
That's a valid point. It really depends on the specific requirements of the organization.
upvoted 0 times
...
Junita
12 days ago
I would go with C. Using an API specification in a Mule 4 application can also be a good approach.
upvoted 0 times
...
Broderick
14 days ago
Yeah, I agree. It's important to have flexibility when enforcing security policies.
upvoted 0 times
...
Tiffiny
24 days ago
I think B is the best option too. Custom Java code can provide more control.
upvoted 0 times
...
...
Marylyn
2 months ago
I agree with Brynn. C seems like the most straightforward way to handle this use case. Mule 4 applications with API specs are designed for this kind of thing.
upvoted 0 times
Tracey
1 months ago
B: That makes sense, using an API spec would definitely help enforce the Client ID policy
upvoted 0 times
...
Shawn
1 months ago
C: A Mule 4 application with an API specification
upvoted 0 times
...
Elouise
1 months ago
B: A Mule 3 or Mule 4 application modified with custom Java code
upvoted 0 times
...
...
Cecil
2 months ago
I'm not sure, but I think embedding the policy directly in the application's JVM could lead to more complex and harder to maintain code.
upvoted 0 times
...
Kirk
3 months ago
I agree with Alline. Enforcing the Client ID policy in the API proxy makes sense for better security.
upvoted 0 times
...
Alline
3 months ago
I think the answer is C) A Mule 4 application with an API specification.
upvoted 0 times
...
Hubert
3 months ago
Hmm, I'm not sure about that. Wouldn't a Non-Mule application (D) be a better choice to avoid embedding the policy directly in the application's JVM?
upvoted 0 times
...
Brynn
3 months ago
I think the answer is C. Using a Mule 4 application with an API specification makes the most sense to enforce the Client ID Enforcement policy.
upvoted 0 times
Kip
2 months ago
D) A Non-Mule application
upvoted 0 times
...
Kristine
2 months ago
C) A Mule 4 application with an API specification
upvoted 0 times
...
Gearldine
2 months ago
B) A Mule 3 or Mule 4 application modified with custom Java code
upvoted 0 times
...
Solange
2 months ago
A) A Mule 3 application using APIkit
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