A 311 application should automatically extract text from photos of handwritten citizen complaint forms. Which evolving cloud capability best matches at Cloud+ awareness depth?
Select an answer to reveal the explanation.
Short Explanation
Those scribbled complaint photos need a smart reader, not a brand-new chip factory. Cloud OCR / text-recognition APIs pull the words out for you so the 311 system can file them. Cloud+ cares that you know the capability exists — not that you become an ML researcher overnight.
Full Explanation
Cloud machine-learning text recognition and OCR services extract text from images without requiring the city to train models from scratch or build specialized silicon. A 311 application that should automatically read handwritten citizen complaint photos matches that Cloud+ awareness-level capability: call a managed vision or OCR API and store the resulting text for routing and search. Building a custom ASIC fab for exclusive city chip design is vastly out of scope and unrelated to consuming managed cloud AI services. Replacing all storage with write-once optical discs in a vault does not perform recognition. Disabling image uploads avoids the problem instead of meeting citizen intake needs for photographed complaint forms. Exam caveat: Cloud+ expects recognition of when to consume managed AI services versus building bespoke ML platforms—especially for common tasks such as OCR, translation, and speech. Operational check: send sample complaint photos through the OCR service, measure accuracy on real handwriting, keep human review for low-confidence results, restrict PII in logs and training opt-out settings per policy, and integrate extracted text into the 311 workflow with retention and redaction controls.