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

Salesforce Exam MuleSoft Platform Architect I Topic 2 Question 26 Discussion

Actual exam question for Salesforce's MuleSoft Platform Architect I exam
Question #: 26
Topic #: 2
[All MuleSoft Platform Architect I Questions]

A Mule 4 API has been deployed to CloudHub and a Basic Authentication - Simple policy has been applied to all API methods and resources. However, the API is still accessible

by clients without using authentication.

How is this possible?

Show Suggested Answer Hide Answer
Suggested Answer: B

When a Basic Authentication policy is applied to an API on CloudHub but clients can still access the API without authentication, the likely cause is a missing Autodiscovery element. Here's how this affects API security:

Autodiscovery in MuleSoft:

The Autodiscovery element is essential for linking an API implementation deployed in CloudHub with its API instance defined in API Manager. This connection allows the policies applied in API Manager, such as Basic Authentication, to be enforced on the deployed API.

Why Option B is Correct:

Without Autodiscovery, the deployed application does not 'know' about the policies configured in API Manager, resulting in unrestricted access. Adding Autodiscovery enables the API to enforce the policies correctly.

of Incorrect Options:

Option A (incorrect Exchange version) would not cause bypassing of security policies.

Option C (missing client applications) does not impact authentication policy enforcement.

Option D (worker restart) is irrelevant to policy enforcement.

Reference Refer to MuleSoft documentation on Autodiscovery configuration and linking API Manager policies for additional information on setting up secure API policies.


Contribute your Thoughts:

Dottie
2 days ago
I agree with Tayna, that could be the reason why authentication is not working.
upvoted 0 times
...
Bok
3 days ago
I don't think the APE Router component or the Autodiscovery element are the issue here. The most likely explanation is that no client applications have been created, so the API is still open to the public. C is my pick.
upvoted 0 times
...
Tayna
4 days ago
I think the issue might be with the Autodiscovery element missing.
upvoted 0 times
...
Sue
6 days ago
Hmm, this is a tricky one. I'm leaning towards D - one of the CloudHub workers restarted, which could have caused the authentication to stop working.
upvoted 0 times
...
Alpha
11 days ago
Wait, the API is still accessible without authentication? That's a big security risk! I'm pretty sure the correct answer is C - no client applications have been created for this API.
upvoted 0 times
...

Save Cancel