Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Exam - Topic 3 Question 35 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Developer II (Mule-Dev-301) exam

Question #: 35
Topic #: 3

[All Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Questions]

A system API that communicates to an underlying MySQL database is deploying to CloudHub. The DevOps team requires a readiness endpoint to monitor all system APIs.

Which strategy should be used to implement this endpoint?

ACreate a dedicated endpoint that responds with the API status and reachability of the underlying systems

BCreate a dedicated endpoint that responds with the API status and health of the server

CUse an existing resource endpoint of the API

DCreate a dedicated endpoint that responds with the API status only

Show Suggested Answer

Suggested Answer: A

To implement a readiness endpoint to monitor all system APIs, the developer should create a dedicated endpoint that responds with the API status and reachability of the underlying systems. This way, the DevOps team can check if the system API is ready to receive requests and if it can communicate with its backend systems without errors. Reference: https://docs.mulesoft.com/mule-runtime/4.3/deployment-strategies#readiness-probes

by William at Nov 21, 2025, 11:26 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Harrison

3 days ago

Definitely need to monitor server health too, so B makes sense.

upvoted 0 times

...

Lemuel

8 days ago

Surprised there's no mention of security for the endpoint!

upvoted 0 times

...

Thaddeus

27 days ago

Why not just use an existing resource? Seems simpler.

upvoted 0 times

...

Jeff

1 month ago

A dedicated endpoint for API status is crucial.

upvoted 0 times

...

Dierdre

1 month ago

Monitoring the API status and reachability is like checking the engine and fuel levels before a long road trip. Option A is the way to go.

upvoted 0 times

...

Jillian

1 month ago

Haha, using an existing resource endpoint? That's like trying to fit a square peg in a round hole. Option C is a no-go.

upvoted 0 times

...

Justine

2 months ago

Option B is a bit too limited. The DevOps team needs to know more than just the API status and server health.

upvoted 0 times

...

Ronnie

2 months ago

I agree with Krissy. Option A provides the most comprehensive information for the DevOps team to monitor the system's health.

upvoted 0 times

...

Krissy

2 months ago

Option A seems like the best choice to me. Monitoring the API status and reachability of the underlying systems is crucial for ensuring the system's reliability.

upvoted 0 times

...

Amalia

2 months ago

I recall a practice question where we had to choose between just status or status and health. I think option D might be too limited.

upvoted 0 times

...

Edda

2 months ago

I feel like using an existing resource endpoint might not give us the complete picture. Option C seems risky.

upvoted 0 times

...

Cristy

2 months ago

I'm not entirely sure, but I remember something about health checks being crucial. Could option B be the right one?

upvoted 0 times

...

Alpha

3 months ago

I'm leaning towards option A as well. Monitoring both the API status and the underlying systems sounds like the best way to ensure the system is truly ready for deployment.

upvoted 0 times

...

Carmen

3 months ago

Option C could be an interesting approach, but I'm worried it might not give the DevOps team all the information they need. A dedicated endpoint feels like the safer choice.

upvoted 0 times

...

Tresa

3 months ago

I think we discussed the importance of having a dedicated endpoint for monitoring, so maybe option A is the best choice?

upvoted 0 times

...

Gail

3 months ago

I prefer option B. Health of the server is crucial too.

upvoted 0 times

...

Kris

3 months ago

I think option A is the best. It covers both status and reachability.

upvoted 0 times

...

Jacqueline

4 months ago

I think option A is the best choice!

upvoted 0 times

...

Judy

4 months ago

Option D is just the tip of the iceberg. The DevOps team needs more details to effectively monitor the system.

upvoted 0 times

...

Franklyn

4 months ago

I'm a little unsure here. Option B seems simpler, just checking the API status and server health. But I'm not sure if that's enough for the DevOps team's requirements.

upvoted 0 times

...

Chaya

4 months ago

I think I'd go with option A. Creating a dedicated endpoint to monitor the API status and the underlying systems seems like the most comprehensive approach.

upvoted 0 times

...