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 US
Mob_nav_barsMENU

Salesforce Certified MuleSoft Developer (Mule-Dev-201) Exam - Topic 12 Question 16 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Developer (Mule-Dev-201) exam
Question #: 16
Topic #: 12
[All Salesforce Certified MuleSoft Developer (Mule-Dev-201) Questions]

An API instance of type API endpoint with API proxy is created in API manager using an API specification from Anypoint Exchange. The API instance is also configured with an API proxy that is deployed and running in CloudHub.

An SLA- based policy is enabled in API manager for this API instance.

Where can an external API consumer obtain a valid client ID and client secret to successfully send requests to the API proxy?

Show Suggested Answer Hide Answer
Suggested Answer: A

* When a client application is registered in Anypoint Platform, a pair of credentials consisting of a client ID and client secret is generated.

* When the client application requests access to an API, a contract is created between the application and that API.

* An API that is protected with a Client ID Enforcement policy is accessible only to applications that have an approved contract.

---------------------------------------------------------------------------------------------------------------------------------------------

Correct Answer: In the organization's public API portal in Anypoint Exchange, from


by Laticia at Sep 17, 2024, 05:31 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified MuleSoft Developer (Mule-Dev-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Peggy
5 months ago
Definitely A, that's the standard process for API access.
upvoted 0 times
...
Craig
5 months ago
Wait, can you really get client secrets from the public API portal?
upvoted 0 times
...
Sheridan
5 months ago
D sounds plausible, but I doubt it's the right place for client IDs.
upvoted 0 times
...
Elly
5 months ago
I think B is a bit misleading, you don't get client credentials there.
upvoted 0 times
...
Justine
6 months ago
A is correct, that's where you get the client ID and secret.
upvoted 0 times
...
Gregoria
6 months ago
I’m confused about whether the client credentials can be generated in Anypoint Studio. I thought it was more about deployment rather than client access.
upvoted 0 times
...
Lyla
6 months ago
I’m leaning towards option A since it mentions the public API portal, which sounds familiar from our study sessions.
upvoted 0 times
...
Terrilyn
6 months ago
I remember practicing a question about API management, and I feel like the answer was related to the Runtime Manager, but that seems off for this one.
upvoted 0 times
...
Maryann
6 months ago
I think the client ID and secret are usually obtained from the API portal, but I'm not entirely sure if it's specifically in Anypoint Exchange.
upvoted 0 times
...
Ivette
6 months ago
This seems pretty straightforward to me. The question clearly states that an SLA-based policy is enabled for the API instance, so the client ID and client secret would be obtained from the organization's public API portal, where approved client applications for the API proxy are managed. I'm confident that option A is the correct answer.
upvoted 0 times
...
Magnolia
6 months ago
Okay, I think I've got this. Since the API instance is configured with an API proxy that's deployed to CloudHub, the client ID and client secret would be available in the Runtime Manager, in the properties tab for the deployed API proxy. That makes sense, since the API proxy is the entry point for external API consumers.
upvoted 0 times
...
Ernie
6 months ago
Hmm, I'm a bit confused about where exactly the client ID and client secret would be available. Is it something that's generated by the APIkit or Rest Connect components in Anypoint Studio? Or is it something that's configured in the Runtime Manager for the deployed API proxy? I'll need to review the details carefully.
upvoted 0 times
...
Buck
7 months ago
This question seems straightforward, but I want to make sure I understand the key details. The API instance is configured with an API proxy, and there's an SLA-based policy enabled. I think the client ID and client secret would be obtained from the organization's public API portal, since that's where approved client applications are managed.
upvoted 0 times
...
Marti
7 months ago
I think the key is understanding when the communication is required to occur. That detail could help me eliminate some of the options.
upvoted 0 times
...
Shelba
2 years ago
I'm going with A. The organization would want to manage the client IDs and secrets in a centralized place like the API portal, rather than letting developers find them in Anypoint Studio or Runtime Manager.
upvoted 0 times
Venita
1 year ago
Tandra: Definitely, it's important to keep sensitive information like client IDs and secrets in a secure location.
upvoted 0 times
...
Tatum
2 years ago
I agree, it would be more secure that way.
upvoted 0 times
...
Tandra
2 years ago
That makes sense, it's better to have them managed in a centralized place.
upvoted 0 times
...
Sueann
2 years ago
I think the client ID and secret can be obtained from the organization's public API portal in Anypoint Exchange.
upvoted 0 times
...
...
Annice
2 years ago
I'm not sure, but I think it could also be D. Maybe the client ID and client secret can be obtained from the properties tab of the deployed API proxy in Runtime Manager. It's worth considering as well.
upvoted 0 times
...
Jesus
2 years ago
Haha, I bet the correct answer is not B or C, since those are about Anypoint Studio, not the API portal or Runtime Manager. This question is testing our knowledge of the Anypoint Platform, not our Anypoint Studio skills.
upvoted 0 times
...
Keneth
2 years ago
Option D seems like a good guess, since the Runtime Manager would have the details of the deployed API proxy. But I'm not sure if that's the right place to get the client ID and client secret.
upvoted 0 times
Sanda
2 years ago
C) In Anypoint Studio, from components generated by Rest Connect for API specification
upvoted 0 times
...
William
2 years ago
B) In Anypoint Studio, from components generated by APIkit for the API specification
upvoted 0 times
...
Lanie
2 years ago
A) In the organization's public API portal in Anypoint Exchange, from an approved client application for the API proxy
upvoted 0 times
...
...
Luann
2 years ago
I agree with Ernie, option A makes the most sense in this scenario. It's important for external API consumers to have a valid client ID and client secret to access the API proxy.
upvoted 0 times
...
Kimberlie
2 years ago
I think the answer is A. The API consumer would need to obtain the client ID and client secret from the organization's public API portal in Anypoint Exchange, as that's where approved client applications for the API proxy are likely to be listed.
upvoted 0 times
Maynard
1 year ago
I don't think that's the right place. The client ID and client secret are usually obtained from the API portal.
upvoted 0 times
...
Corinne
2 years ago
D) In Runtime Manager, from the properties tab of the deployed approved API proxy
upvoted 0 times
...
Kanisha
2 years ago
That makes sense. It's important for the API consumer to get the client ID and client secret from the approved client application.
upvoted 0 times
...
Lynelle
2 years ago
A) In the organization's public API portal in Anypoint Exchange, from an approved client application for the API proxy
upvoted 0 times
...
...
Ernie
2 years ago
I think the answer is A, because the client ID and client secret are usually obtained from an approved client application in the organization's public API portal.
upvoted 0 times
...

Save Cancel