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

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

Question #: 3
Topic #: 1

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

A company deploys 10 public APIs to CloudHub. Each API has its individual health endpoint defined. The platform operation team wants to configure API Functional Monitoring to monitor the health of the APIs periodically while minimizing operational overhead and cost.

How should API Functional Monitoring be configured?

AFrom one public location with each API in its own schedule

BFrom one private location with all 10 APIs in a single schedule

CFrom one public location with all 10 APIs in a single schedule

DFrom 10 public locations with each API in its own schedule

Show Suggested Answer

Suggested Answer: C

To configure API Functional Monitoring to monitor the health of 10 public APIs periodically while minimizing operational overhead and cost, the developer should use one public location with all 10 APIs in a single schedule. A public location is a worker that runs in a CloudHub shared environment, which is cheaper and easier to maintain than a private location. A single schedule allows running all 10 APIs tests at the same time and frequency, which reduces complexity and resource consumption. Reference: https://docs.mulesoft.com/functional-monitoring/fm-create-monitor#create-a-monitor

by Clay at May 20, 2024, 03:18 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

Martina

3 months ago

Option C is definitely the way to go for minimizing overhead.

upvoted 0 times

...

Geoffrey

3 months ago

I like option D for its thoroughness, but it could get costly.

upvoted 0 times

...

Dierdre

3 months ago

Surprised that option B is even a choice, it sounds risky!

upvoted 0 times

...

Stanford

4 months ago

I disagree, I think option A gives better control over each API's schedule.

upvoted 0 times

...

Yolande

4 months ago

Option C seems the most efficient for monitoring all APIs together.

upvoted 0 times

...

Michell

4 months ago

I’m a bit confused about the benefits of public vs. private locations. I wonder if option D might be overkill with 10 separate schedules.

upvoted 0 times

...

Vincenza

4 months ago

I practiced a similar question where we had to choose between public and private locations, and I think option B could be a good compromise for monitoring without too much cost.

upvoted 0 times

...

William

4 months ago

I'm not entirely sure, but I feel like having each API in its own schedule could lead to higher operational overhead, which makes me lean away from option A.

upvoted 0 times

...

Lenora

5 months ago

I remember we discussed the importance of minimizing costs, so I think option C might be the best choice since it consolidates monitoring.

upvoted 0 times

...

Tess

5 months ago

I'm leaning towards option D. Monitoring each API individually from a public location might be more reliable, even if it costs a bit more.

upvoted 0 times

...

Annice

5 months ago

Option C looks good to me - monitoring all 10 APIs from a single public location should be efficient and cost-effective.

upvoted 0 times

...

Taryn

5 months ago

I'm a bit confused about the difference between public and private locations. I'll need to think this through more carefully.

upvoted 0 times

...

Brandee

5 months ago

Hmm, I'm not sure. Monitoring from a public location could be more expensive. Maybe option B with a single private location would be better for cost optimization.

upvoted 0 times

...

Gilma

5 months ago

This seems straightforward. I'd go with option A to monitor each API individually from a public location.

upvoted 0 times

...

Annabelle

5 months ago

Hmm, I'm a bit unsure about this one. I'll need to carefully read through the options and see which ones align with the Ibstpi instructor competencies I've learned about.

upvoted 0 times

...

Joni

5 months ago

I'm a bit confused here. The question mentions the tester couldn't find the numbers on the website, but then it says the catalog was published there. Does that mean the numbers are still on the website somewhere? I'm not sure if the web archive is the best option.

upvoted 0 times

...

Gabriele

5 months ago

Hmm, this seems like a tricky one. I'll need to think carefully about the implications of the "Clear Projects" action and how it affects the user's project repository.

upvoted 0 times

...

Arletta

2 years ago

Monitoring APIs? Sounds like a job for the cloud ninjas! I'd go with option B - no need to overcomplicate things when a single private location can get the job done. Plus, it'll save the company some serious cash, am I right?

upvoted 0 times

...

Britt

2 years ago

Well, well, look at all these options! I bet the developers had a field day coming up with these. Anyway, I'm leaning towards option C. Monitoring all 10 APIs from a single public location just seems like the most straightforward solution to me.

upvoted 0 times

...

Sommer

2 years ago

Hmm, I'm not too sure about that. Personally, I think option D is the best choice. Monitoring each API from a public location ensures individual health checks and maximum visibility.

upvoted 0 times

Angelo

2 years ago

I see your point, but having separate schedules for each API can provide more detailed insights into their individual health statuses.

upvoted 0 times

...

Hyman

2 years ago

But wouldn't it be more cost-effective to monitor all 10 APIs from a single public location?

upvoted 0 times

...

Stephaine

2 years ago

I agree with you, option D seems like the most efficient choice for monitoring the health of each API.

upvoted 0 times

...

Benton

2 years ago

Option B is the way to go! Monitoring all 10 APIs from a single private location is the most cost-effective and efficient solution. Minimizing the number of monitoring locations is key.

upvoted 0 times