A youth-soccer desk wants photo checks during a two-week registration rush and has no one to patch a model host afterward. A court-records unit needs the same kind of check, but the images must stay on an isolated custom runtime the unit operates. Which pairing is accurate?
Select an answer to reveal the explanation.
Short Explanation
Think of renting a photo booth for two weeks versus running your own darkroom in a locked basement. The soccer desk wants a managed API and no patching. The court unit needs isolation and a custom runtime, so they self-host. Image checks do not force every team into a closet server.
Full Explanation
The youth-soccer desk needs photo checks for a short registration rush and has no capacity to patch a model host afterward, so a managed API is the fit: consume a ready service, avoid owning patch cycles, and tear down or idle when the rush ends. The court-records unit needs the same kind of visual check but must keep images on an isolated custom runtime it operates, which is a self-hosting requirement driven by isolation and control rather than by the mere fact that images are involved. The accurate pairing matches operational constraints to hosting models, not a one-size image rule.
Requiring both teams to self-host because every image check needs a closet server is false. Managed vision or foundation-model APIs can score photos when data-handling policy allows and when the team cannot staff ongoing host maintenance.
Forcing both onto a managed API because isolation is never a reason to self-host ignores regulated or sensitive workloads. Court images that must remain on an isolated custom runtime are a legitimate reason to operate your own stack.
Having the soccer desk train a new model on each registration while the court unit skips scoring invents busywork and abandons the court requirement. Neither constraint called for continual from-scratch training or for refusing to score images.
Exam caveat: managed versus self-hosted is a workload and governance decision. Image modality alone does not dictate the answer; patching capacity, isolation, and custom runtime needs do.
Operational check: document data residency and retention for soccer registration photos on the managed path, and verify network isolation, access logging, and patch ownership for the court unit's custom runtime before either workflow goes live.