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 II (Mule-Dev-301) Exam - Topic 3 Question 35 Discussion

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?
A) Create a dedicated endpoint that responds with the API status and reachability of the underlying systems
B) Create a dedicated endpoint that responds with the API status and health of the server
C) Use an existing resource endpoint of the API
D) Create a dedicated endpoint that responds with the API status only

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?

Show Suggested Answer Hide 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:

0/2000 characters
Submit Cancel
Ammie
5 months ago
B is solid, but A gives a fuller picture. Can't go wrong with that!
upvoted 0 times
...
Renay
5 months ago
Option D is too limited. We need more than just API status.
upvoted 0 times
...
Blythe
5 months ago
I agree with A. We need comprehensive monitoring for reliability.
upvoted 0 times
...
Oneida
5 months ago
Option C seems too risky. Existing endpoints might not provide all needed info.
upvoted 0 times
...
Harrison
6 months ago
Definitely need to monitor server health too, so B makes sense.
upvoted 0 times
...
Lemuel
6 months ago
Surprised there's no mention of security for the endpoint!
upvoted 0 times
...
Thaddeus
6 months ago
Why not just use an existing resource? Seems simpler.
upvoted 0 times
...
Jeff
7 months ago
A dedicated endpoint for API status is crucial.
upvoted 0 times
...
Dierdre
7 months 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
7 months 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
7 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
7 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
7 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
8 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
8 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
8 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
8 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
8 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
8 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
9 months ago
I prefer option B. Health of the server is crucial too.
upvoted 0 times
...
Kris
9 months ago
I think option A is the best. It covers both status and reachability.
upvoted 0 times
...
Jacqueline
9 months ago
I think option A is the best choice!
upvoted 0 times
...
Judy
9 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
9 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
10 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
Larue
4 months ago
Definitely A! We need that comprehensive view.
upvoted 0 times
...
Jonell
4 months ago
I like A as well, it covers all bases.
upvoted 0 times
...
Sharee
4 months ago
Option B could work too, but it’s not as thorough.
upvoted 0 times
...
Glennis
5 months ago
Yeah, monitoring both status and reachability is crucial.
upvoted 0 times
...
Timothy
5 months ago
I agree, option A sounds solid.
upvoted 0 times
...
...

Save Cancel