A tax assessor compares keeping file servers in the civic data room versus hosting the citizen portal in a cloud region. What distinction should the team apply?

When a tax assessor compares file servers in the civic data room to a citizen portal hosted in a cloud region, the core distinction is placement and operational model: on-premises keeps servers locally under municipal facilities and operations, while cloud places workloads in a provider region that the municipality consumes as a service. Networking, identity, and operations still matter in both models, but the fundamental contrast in the stem is where the workloads live and who operates the underlying region.

Cloud regions always require Layer 2 stretching of every municipal VLAN fails by concept—cloud connectivity commonly uses routed VPNs, private interconnects, or public HTTPS without stretching every LAN VLAN. On-premises and cloud differ only by cable color standards, not placement fails because cable color is irrelevant to the architectural contrast; placement and responsibility change. SOHO topology always mandates spine-leaf fabrics for three PCs fails as a distractor that misapplies data-center fabric ideas to tiny topologies and does not address on-prem vs cloud.

Exam caveat: On-prem vs cloud questions test placement and operating model, not a requirement to extend Layer 2 everywhere. Be wary of absolutes like "always require L2 stretch."

Operational check: Document which workloads remain in the civic data room versus which run in the provider region, how users reach each (LAN vs VPN/private link/public URL), and who patches the underlying hosts. If the "cloud" portal is actually still a VM solely in the civic basement, the team has not applied the distinction the comparison asked for.