MENU
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?
Suggested Answer: A
Get Premium Salesforce Certified MuleSoft Developer (Mule-Dev-201) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
36 comments · newest first
NI
Nieves
11 months ago
D seems off, you can't enforce policies just by adding them to the spec.
BE
Belen
11 months ago
A is the way to go, no doubt about it.
MA
Mammie
12 months ago
Wait, can you really do that in API Manager? Sounds too easy!
TH
Thora
12 months ago
I think B is better, custom policies give more control.
BA
Basilia
1 year ago
Definitely A, that's the simplest way to enforce it!
FA
Fausto
1 year ago
I recall that adding requirements in API Designer is more about defining the API, not enforcing policies. So, I don't think that's the right choice here.
SH
Shawn
1 year ago
I’m a bit confused about the options. I feel like coding a custom policy in Anypoint Studio might be overcomplicating things for this scenario.
RA
Rashad
1 year ago
I remember a practice question where we had to implement a policy, and I think applying it in API Manager was the right approach there too.
QU
Quentin
1 year ago
I think the easiest way would be to apply the Client ID Enforcement policy directly in API Manager, but I'm not completely sure.
GE
Georgiann
1 year ago
I'm pretty confident that option A is the way to go here. API Manager is specifically designed to manage and enforce policies on deployed APIs, so that seems like the most straightforward and idiomatic solution. The other options seem a bit more complicated and not as well-suited for this particular scenario.
PO
Portia
1 year ago
Hmm, I'm a bit unsure about this one. I know we can apply policies in API Manager, but I'm not sure if that's the most idiomatic approach since the API was originally designed in API Designer. Maybe option D, where we add the policy requirements directly to the API specification, would be a better fit?
SC
Scarlet
1 year ago
This looks like a straightforward question about applying a Client ID Enforcement policy to a Mule application. I think the easiest and most idiomatic way would be to apply the policy directly in API Manager, as described in option A.
JO
Joanne
1 year ago
Okay, let me think this through. The question says the API was published to Anypoint Exchange, so I'm guessing we can't just add the policy in API Designer anymore. And coding a custom policy in Anypoint Studio or Anypoint Design Center seems like overkill for a simple Client ID Enforcement. I'm going to go with option A - applying the policy in API Manager.
DE
Desmond
1 year ago
I'm pretty confident I know the answer to this one. Imported modules are in strict mode whether you declare them as such or not. That's option C.
XO
Xochitl
2 years ago
I'm just glad they didn't ask us to create a blockchain-based Client ID using quantum cryptography. That would be overkill.
PE
Pearly
2 years ago
Knowing Mule, B or C would involve way too much cusPearly coding. A is the way to go, keep it simple!
QU
Quentin
2 years ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
ZI
Zita
2 years 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
AI
Aileen
2 years ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
JU
Julie
2 years ago
Hmm, D might be the most 'idiomatic' since it's part of the API design, but A is probably the quickest solution.
ST
Stanford
2 years ago
I agree, A is the most straightforward way to enforce the Client ID policy on the deployed Mule app.
VI
Vivan
2 years ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
BU
Bulah
2 years 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
PE
Peggy
2 years ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
NO
Noble
2 years ago
That could work too, but I think using API Manager directly is simpler and more idiomatic.
LA
Lai
2 years ago
But wouldn't it be more flexible to code a custom policy in Anypoint Studio and add it to Runtime Manager?
EM
Emerson
2 years ago
I agree with Noble, it makes sense to enforce the policy at the API Manager level.
RO
Rosann
2 years ago
A seems like the easiest option, just apply the policy in API Manager where the API is managed.
RA
Raylene
2 years ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
AL
Alba
2 years ago
Yes, it's the easiest way to manage the policy for the API.
JO
Jovita
2 years ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
AU
Audry
2 years ago
That does seem like the most straightforward option.
BR
Brice
2 years ago
Yeah, that makes sense. It's all in one place then.
VA
Vashti
2 years ago
A) In API Manager, apply a Client ID Enforcement policy for the API instance
AR
Ardella
2 years ago
I think A is the easiest option, just apply the policy in API Manager where the API is managed.
NO
Noble
2 years ago
I think the easiest way is to apply a Client ID Enforcement policy in API Manager.