A public works CIO proposes public FAQs in the cloud and sensitive case-file assistance on local models. What hosting pattern is that?
Select an answer to reveal the explanation.
Short Explanation
Put the tourist-brochure answers in the flexible cloud; keep the sensitive case files on local models. That’s hybrid hosting—matching each workload to the privacy and scale it actually needs.
Full Explanation
Public FAQs in the cloud plus sensitive case-file assistance on local models is hybrid hosting: workloads are split by privacy and scale needs rather than forced into a single extreme. Public works can elastically serve low-sensitivity FAQs from managed cloud while keeping confidential case-file text on city-controlled local models, matching each risk profile to an appropriate host. Exclusive public-cloud for all data regardless of sensitivity ignores classification boundaries and may violate privacy commitments for case materials. Exclusive air-gapped local for even trivial public FAQs forgoes elasticity and managed capacity where residual risk is low and traffic may spike. Random model routing with no sensitivity classification fails governance, blocks audits, and makes incident response guesswork. Exam caveat: hybrid is a deliberate sensitivity-aware pattern with documented routing rules—not informal ‘sometimes cloud, sometimes local’ without policy. Operational check: publish a data-classification matrix that maps FAQ versus case-file content to allowed hosts, enforce routing in the application layer, monitor for misrouted sensitive prompts, review vendor DPAs for the cloud FAQ tier separately from local case-file controls, and re-validate the split when new generative features are proposed.