A library consortium needs common computer-vision checks on uploaded photos and wants strong performance with minimal GPU fleet operations. What should the architect prefer?
Select an answer to reveal the explanation.
Short Explanation
If the vision job is a common one, don’t stand up a GPU ranch—use Rekognition and save the ops. DIY GPUs wait for custom models that managed APIs can’t cover. Deep Archive yearly jobs and Config rules aren’t real-time vision engines.
Full Explanation
Purpose-built AI services such as Amazon Rekognition deliver performant vision capabilities without customers operating GPU fleets. Architects should choose managed services for common tasks and reserve self-managed GPU instances for requirements those services cannot meet. Archival-only offline processing and configuration-compliance services are not substitutes for online vision inference.