A baptism-register scan project wants every face searchable from a typed name. What should the candidate ask before treating that as a default feature?
Select an answer to reveal the explanation.
Short Explanation
A searchable face pile is not a free bonus feature. Ask who can look someone up and whether families agreed—privacy first, then search.
Full Explanation
A baptism-register scan project that wants every face searchable from a typed name should ask who may query those faces and whether sitters or families agreed to a face index before treating search as a default feature. Access control and consent gate biometric search in civic records—not only embedding dashboards.
Asking only whether CLIP cosine scores look neat on a dashboard fails the governance question. Asking only whether diffusion can regenerate missing pages faster fails privacy and authenticity scope. Asking whether NeMo Guardrails from another exam must front the search box fails by importing off-list product mandates as the only question.
Exam caveat: face indexes are sensitive. Consent and query authorization come before “default searchable” features.
Operational check: define authorized queriers; capture consent/legal basis; disable open name-to-face search until the municipal records board approves; log access. In municipal trustworthy-AI stewardship, record the disclosure, consent, or bias decision and the rejected shortcuts in the gallery change log so future stewards protect residents from undisclosed synthesis and stereotyped generation. Re-audit labels, consent records, and bias samples after the next model or exhibit update to keep the city's public trust intact.