A housing chatbot must reject oversized uploads and limit how many files each caseworker can send per day. Which gateway control best matches that requirement?
Select an answer to reveal the explanation.
Short Explanation
Think of the housing bot like a drop box with a slot size and a daily stamp limit. Input size and quantity quotas keep one account from stuffing giant files or flooding the gateway. You'll still miss the requirement if you're capping output size, limiting hourly sessions, or sharing one quota across accounts because you aren't rejecting oversized inputs or stopping extra daily uploads per caseworker.
Full Explanation
Enforcing input size and daily quantity quotas per caseworker account is the AI gateway control that matches a housing chatbot that must reject oversized uploads and cap how many files each caseworker can send per day. Quotas act before prompts reach the model: a maximum file or request size stops context-stuffing and cost spikes from giant attachments, while a per-account daily quantity limit prevents one caseworker identity from flooding the municipal housing assistant. Binding those limits to the caseworker account keeps enforcement identity-aware and auditable for civic casework.
Enforcing output size and daily quantity quotas per caseworker account fails by direction because it caps the size of model responses, not the size of input uploads, so it does not reject an oversized file even though the per-account daily quantity part matches. Enforcing input size and hourly session quotas per caseworker account fails on the quantity window because it limits sessions per hour, not how many files each caseworker can send per day; an hourly session cap does not enforce the required daily cap or block a sixth upload of the day. Enforcing input size and daily quantity quotas per shared service account fails on scope because a shared quota lets one caseworker consume the allowance for everyone and does not cap how many files each caseworker can send; it is not identity-aware per-caseworker enforcement.
Exam caveat: CY0-style items map a stated requirement (size plus daily quantity) to the matching gateway control. Prefer per-account input quotas over citywide bans, open-sourcing weights, or banner text when the stem asks what best matches the requirement.
Operational check: On the housing chatbot gateway, set max upload size and max daily files per caseworker account, attempt an oversized filing and a sixth upload after a five-file daily cap, confirm both are rejected with logged account identifiers, and verify unrelated document portals still accept legitimate uploads.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.