Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Salesforce Exam Salesforce MuleSoft Developer I Topic 8 Question 10 Discussion

Actual exam question for Salesforce's Salesforce MuleSoft Developer I exam
Question #: 10
Topic #: 8
[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

by Earleen at Jul 07, 2024, 07:31 AM

Limited Time Offer

25%

Off

Get Premium Salesforce MuleSoft Developer I Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Xochitl
9 months ago
I'm just glad they didn't ask us to create a blockchain-based Client ID using quantum cryptography. That would be overkill.
upvoted 0 times
...
Pearly
9 months ago
Knowing Mule, B or C would involve way too much cusPearly coding. A is the way to go, keep it simple!
upvoted 0 times
Quentin
9 months ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
upvoted 0 times
...
Zita
9 months 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
...
Aileen
9 months ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
upvoted 0 times
...
...
Julie
9 months ago
Hmm, D might be the most 'idiomatic' since it's part of the API design, but A is probably the quickest solution.
upvoted 0 times
...
Stanford
9 months ago
I agree, A is the most straightforward way to enforce the Client ID policy on the deployed Mule app.
upvoted 0 times
Vivan
8 months ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
upvoted 0 times
...
Bulah
8 months 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
...
Peggy
9 months ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
upvoted 0 times
...
...
Noble
9 months ago
That could work too, but I think using API Manager directly is simpler and more idiomatic.
upvoted 0 times
...
Lai
10 months 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
...
Emerson
10 months ago
I agree with Noble, it makes sense to enforce the policy at the API Manager level.
upvoted 0 times
...
Rosann
10 months ago
A seems like the easiest option, just apply the policy in API Manager where the API is managed.
upvoted 0 times
Raylene
8 months ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
upvoted 0 times
...
Alba
8 months ago
Yes, it's the easiest way to manage the policy for the API.
upvoted 0 times
...
Jovita
8 months ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
upvoted 0 times
...
Audry
9 months ago
That does seem like the most straightforward option.
upvoted 0 times
...
Brice
9 months ago
Yeah, that makes sense. It's all in one place then.
upvoted 0 times
...
Vashti
9 months ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
upvoted 0 times
...
Ardella
9 months ago
I think A is the easiest option, just apply the policy in API Manager where the API is managed.
upvoted 0 times
...
...
Noble
10 months ago
I think the easiest way is to apply a Client ID Enforcement policy in API Manager.
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