MENU
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?
30 comments · newest first
MA
Martina
11 months ago
Option C is definitely the way to go for minimizing overhead.
GE
Geoffrey
11 months ago
I like option D for its thoroughness, but it could get costly.
DI
Dierdre
12 months ago
Surprised that option B is even a choice, it sounds risky!
ST
Stanford
12 months ago
I disagree, I think option A gives better control over each API's schedule.
YO
Yolande
1 year ago
Option C seems the most efficient for monitoring all APIs together.
MI
Michell
1 year 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.
VI
Vincenza
1 year 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.
WI
William
1 year 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.
LE
Lenora
1 year ago
I remember we discussed the importance of minimizing costs, so I think option C might be the best choice since it consolidates monitoring.
TE
Tess
1 year 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.
AN
Annice
1 year ago
Option C looks good to me - monitoring all 10 APIs from a single public location should be efficient and cost-effective.
TA
Taryn
1 year ago
I'm a bit confused about the difference between public and private locations. I'll need to think this through more carefully.
BR
Brandee
1 year 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.
GI
Gilma
1 year ago
This seems straightforward. I'd go with option A to monitor each API individually from a public location.
AN
Annabelle
1 year 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.
JO
Joni
1 year 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.
GA
Gabriele
1 year 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.
AR
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?
BR
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.
SO
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.
AN
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.
HY
Hyman
2 years ago
But wouldn't it be more cost-effective to monitor all 10 APIs from a single public location?
ST
Stephaine
2 years ago
I agree with you, option D seems like the most efficient choice for monitoring the health of each API.
BE
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.
QU
Quentin
2 years ago
I agree, it definitely helps in minimizing operational overhead and cost.
LI
Lindsey
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.
SO
Solange
2 years ago
Minimizing the number of monitoring locations is key.
AU
Audra
2 years ago
I agree, monitoring all 10 APIs from one private location makes it easier to manage.
JA
Jarod
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.
RE
Reta
2 years ago
Option B is definitely the best choice. It's efficient and cost-effective.