The city CISO requires logs of model ID, endpoint, and caller identity for every civic inference call. What infrastructure capability is being mandated?
Select an answer to reveal the explanation.
Short Explanation
If you cannot say which model, endpoint, and caller made a civic inference, you are flying blind. Log those three. Instant deletes, sampling-only logs, and one shared bot identity erase accountability.
Full Explanation
The city CISO requiring logs of model ID, endpoint, and caller identity for every civic inference call is mandating telemetry that attributes GenAI infrastructure use to models, endpoints, and callers. Accountable municipal GenAI needs who called which model on which serving endpoint—for incident response, abuse investigation, chargeback, and policy enforcement. Sampling parameters alone do not establish that accountability chain.
Deleting inference logs within sixty seconds to minimize storage bills destroys the audit trail the mandate requires and hampers investigations. Logging only temperature and top-p records generation settings without actor or target identity. Attributing all calls to a shared “city-bot” service account forever collapses distinct callers into one principal and defeats attribution across departments and applications.
Exam caveat: logging must balance retention, privacy minimization, and prompt-content redaction policies—attribute infrastructure use without unnecessarily retaining full prompt bodies when municipal policy forbids storing resident text at that tier. Operational check: sample inference logs for 311 or permitting calls and confirm each record includes model identifier, endpoint, and authenticated caller, with alerts on missing attribution fields and retention aligned to records policy.