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 4 Question 13 Discussion

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

Kattie
2 months ago
C is the way to go! I mean, who wants to mess with their app's JVM, am I right? That's like trying to fix a flat tire by replacing the whole car.
upvoted 0 times
...
Shantell
3 months ago
Hmm, I'm tempted to say B, but that would involve custom Java code, which might be overkill for this use case. I'll stick with C as the best choice.
upvoted 0 times
Viola
2 months ago
Yeah, it's a more streamlined approach compared to modifying with custom Java code.
upvoted 0 times
...
Carissa
2 months ago
I agree, using an API specification in a Mule 4 application is a good way to enforce the Client ID Enforcement policy.
upvoted 0 times
...
Stevie
2 months ago
I think C is the best choice because it involves an API specification.
upvoted 0 times
...
...
Ressie
3 months ago
Option D sounds interesting, but I'm not sure a non-Mule application would be the recommended approach here. I'll go with C.
upvoted 0 times
Tesha
2 months ago
Definitely, enforcing security measures like Client ID Enforcement is crucial for protecting the organization's APIs.
upvoted 0 times
...
Lon
2 months ago
It's important to ensure only known partners can access the APIs.
upvoted 0 times
...
Cordie
2 months ago
I agree, using a Mule 4 application with an API specification is the recommended approach.
upvoted 0 times
...
Mohammad
2 months ago
I think C is the best option for enforcing the Client ID Enforcement policy.
upvoted 0 times
...
...
Gilma
3 months ago
I'm not sure, but I think B) A Mule 3 or Mule 4 application modified with custom Java code could also work.
upvoted 0 times
...
Alishia
3 months ago
I agree with Clemencia. Using an API specification makes it easier to enforce the Client ID Enforcement policy.
upvoted 0 times
...
Alva
3 months ago
I think the correct answer is C. A Mule 4 application with an API specification. Adding the proxy layer makes sense to enforce the client ID policy without modifying the application code directly.
upvoted 0 times
Vincenza
3 months ago
Yes, it's a good way to enforce the Client ID policy without directly modifying the application code.
upvoted 0 times
...
Asuncion
3 months ago
I agree, using a Mule 4 application with an API specification is the recommended approach.
upvoted 0 times
...
...
Clemencia
4 months ago
I think the answer is C) A Mule 4 application with an API specification.
upvoted 0 times
...

Save Cancel