Exercise 3: Legitimate Reasons to Choose Hybrid Cloud — Possible Solution
====================================================================

Two legitimate reasons, drawn from the chapter's own list plus
reasoning through them:

1. COMPLIANCE REQUIREMENTS. Some industries or jurisdictions require
   certain categories of data (financial records, health data,
   government data) to remain on infrastructure the organization
   directly controls, or within specific physical/legal boundaries
   that a shared public cloud environment may not satisfy on its own.
   A hybrid setup lets an organization keep those specific, regulated
   workloads on private infrastructure while still using public cloud
   for everything else that doesn't carry the same regulatory
   constraint -- getting the benefits of public cloud (Chapter 1's
   elasticity, cost model, speed) without violating a compliance
   requirement for the sensitive portion of their systems.

2. LEGACY SYSTEMS THAT AREN'T PRACTICAL TO MIGRATE. Some
   organizations run older systems -- built on outdated architectures,
   tightly coupled to specific on-prem hardware, or simply too
   business-critical and risky to migrate without extensive rework --
   where a full migration to public cloud would be expensive, risky,
   or simply not worth the effort relative to the benefit. Hybrid
   cloud lets an organization modernize NEW workloads on public cloud
   while leaving the legacy system running where it already works,
   rather than forcing an all-or-nothing migration decision.

(A third valid reason, also from the chapter: LATENCY-SENSITIVE
WORKLOADS that need to run physically close to a specific facility or
user base in a way that's better served by dedicated, local
infrastructure than a public cloud region.)

WHY THIS WORKS AS AN ANSWER
------------------------------
Each reason reflects the chapter's own framing that hybrid cloud is a
DELIBERATE choice made for specific, real reasons -- not a sign of
indecision or an incomplete migration. Both reasons given above show
an organization getting the best of both models for a GENUINE
constraint (a legal/regulatory boundary, or a practical
migration-risk boundary) rather than simply failing to fully commit to
one approach.