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 Salesforce MuleSoft Developer I Topic 5 Question 20 Discussion

Actual exam question for Salesforce's Salesforce MuleSoft Developer I exam
Question #: 20
Topic #: 5
[All Salesforce MuleSoft Developer I Questions]

An API was designed in API Designer, published to Anypoint Exchange, then imported into API Manager.

A Mule application implements this API and is deployed to CloudHub. API Manager manages this deployed API implementation.

What is the easiest and most idiomatic (used for its intended purpose) way to enforce a Client ID Enforcement policy on this Mule application?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Tyra
12 days ago
Haha, I bet the person who came up with Option C is the same one who suggested we use a forklift to move a paperclip. API Manager is the way to go, no doubt about it.
upvoted 0 times
Karol
2 days ago
Option C does seem a bit overkill. API Manager is definitely the easiest way to enforce a Client ID Enforcement policy.
upvoted 0 times
...
...
Francisca
25 days ago
Hold up, Option D? Putting the policy in the API spec? Isn't that a bit backwards? API Manager is the way to go here.
upvoted 0 times
Xenia
9 days ago
That could work too, but I still think using API Manager for Client ID Enforcement is the easiest and most idiomatic way.
upvoted 0 times
...
Arlen
16 days ago
But wouldn't it be more flexible to code a custom policy in Anypoint Studio and add it to Runtime Manager?
upvoted 0 times
...
Fannie
17 days ago
I agree, API Manager is designed to handle those types of policies efficiently.
upvoted 0 times
...
Novella
19 days ago
I think Option A is the best choice. Applying the policy in API Manager makes the most sense.
upvoted 0 times
...
...
Gearldine
1 months ago
Option C? Really? Coding a custom policy just to enforce Client ID? That's way too much effort for a simple requirement.
upvoted 0 times
Maybelle
11 days ago
D) In API Designer, add Client ID Enforcement policy requirements to the API specification
upvoted 0 times
...
Izetta
14 days ago
B) In Anypoint Studio, code a custom policy for Client ID Enforcement and then add the custom policy to Runtime Manager for the Mule application deployment
upvoted 0 times
...
Ilona
26 days ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
upvoted 0 times
...
...
Michell
1 months ago
I agree with Wilbert. It makes sense to enforce the policy at the API Manager level.
upvoted 0 times
...
Wilbert
1 months ago
I think the easiest way is to apply a Client ID Enforcement policy in API Manager.
upvoted 0 times
...
Ulysses
1 months ago
I don't know, Option B sounds like a lot of extra work. Why reinvent the wheel when API Manager has the feature we need?
upvoted 0 times
Gilma
14 days ago
User1: Definitely, let's go with Option A for enforcing the Client ID policy.
upvoted 0 times
...
Georgene
25 days ago
User3: Option B does seem like unnecessary extra work when there's a simpler solution available.
upvoted 0 times
...
Altha
29 days ago
User2: Yeah, I think it makes sense to use the built-in feature in API Manager.
upvoted 0 times
...
Brittni
1 months ago
User1: I agree, Option A seems like the easiest way to enforce the Client ID policy.
upvoted 0 times
...
...
Laura
2 months ago
Option A seems like the obvious choice here. Why complicate things when API Manager can do the job for us?
upvoted 0 times
Karima
1 months ago
Yeah, it just makes everything easier to manage in the long run.
upvoted 0 times
...
Armando
1 months ago
I agree, it's always best to use the built-in features whenever possible.
upvoted 0 times
...
Lennie
2 months ago
Option A seems like the obvious choice here. Why complicate things when API Manager can do the job for us?
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