A records office keeps highly sensitive systems on-premises for policy reasons but wants SaaS email. Which posture best describes that plan?
Select an answer to reveal the explanation.
Short Explanation
Keep the sensitive vaults local; put the inbox in SaaS. That split is a hybrid service posture—different tools, different homes—not an all-cloud or all-basement mandate.
Full Explanation
A hybrid service posture keeps selected workloads on-premises for policy or sensitivity reasons while other services use cloud SaaS. A records office that retains highly sensitive systems locally yet adopts SaaS email is making exactly that split: local control where required, cloud productivity where appropriate. That mixed posture is the correct fundamentals description.
Public cloud only fails because retaining on-premises systems means the office is not “public cloud only.” Private cloud only fails because Microsoft 365 email is a multi-tenant SaaS service commonly used alongside local systems. Platform as a service only fails conceptually: municipal email is consumed as SaaS, not deployed as custom code on a managed runtime for this scenario.
Exam caveat: hybrid email and local records systems still need consistent identity, retention, and information-protection policies so sensitive content is not casually emailed without controls. Operational check: document which systems remain on-premises and why, confirm Exchange Online licensing and mail flow, and align DLP/retention with the records classification scheme before cutover. Record the choice in the municipal service catalog so help-desk scripts stay consistent.