Objective: classify without collapsing distinctions
Use the outcome-and-constraint method from unit one to describe a workload in three dimensions: responsibility, location, and communication. A platform service can reduce infrastructure work while still requiring a deliberate region choice and a secure path to dependencies. Calling an application “cloud native” does not specify any of these. Write a separate sentence for each dimension before combining them into an architecture recommendation. This practice prevents a convenient label from hiding an unanswered requirement.
Locations are logical deployment choices
A region is a geographic area containing zones. A zone is a deployment area within a region and should be treated as a single failure domain. These terms are logical abstractions over physical resources. Do not assume that every zone always occupies its own independent physical data center: the captured Google documentation identifies exceptions during regional expansion. Multiple zones can help with zonal failure, but a region-wide recovery requirement needs its own design and plan. Also check whether the selected service is zonal, regional, or managed across regions.
Providers and private dependencies
A hybrid arrangement connects public-cloud and private or on-premises computing. Multicloud describes using services from more than one public cloud provider. These tests can both be true: private infrastructure linked to two public providers can be hybrid and multicloud. Neither description states whether a particular workload uses infrastructure, platform, or software as a service. Count providers only when evaluating multicloud, and inspect connected private infrastructure when evaluating hybrid. Avoid claiming that either arrangement automatically reduces cost or meets a legal obligation.
Worked example
Fictional case: a distributor keeps a private inventory system and connects it to an application on public provider A. Its analytics team also uses public provider B. First, the private-to-public connection supports the hybrid description. Second, the two public providers support multicloud. Third, neither fact tells you who patches an application guest OS; inspect its actual service model. Finally, record which components communicate and who may initiate the connection. If a Cloud Run service is chosen, its access policies and ingress settings must match the intended audience; a deployed endpoint is not evidence that every dependency can reach it.
Changed condition and a common error
Remove provider B while keeping the connected private inventory system. The hybrid description still applies, but the stated arrangement no longer demonstrates more than one public provider. Moving two applications to different regions of provider A would not restore the multicloud description. This is a classification change rather than a judgment that one architecture is better. Separately, placing those applications in two zones does not show that their shared database or network dependency can survive a regional outage.
Transfer check
A research team uses two public providers and no private environment is mentioned. State what is supported and what is unknown. Check: multicloud is supported; hybrid is not established by these facts. Service responsibilities, resource locations, and permitted communication paths still require investigation. For retrieval practice, classify one arrangement by provider count and another by failure domain before turning over this unit’s cards. Next, use the storage lesson to identify where the workload’s data should live; location labels alone cannot select the data service.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
Shared responsibilities and shared fate on Google Cloud | Cloud Architecture Center | Google Cloud DocumentationGeography and regions | Get started | Google Cloud DocumentationWhat is Cloud Run | Google Cloud DocumentationWhat Is multicloud? Definition and benefits | Google CloudWhat Is Hybrid Cloud? Benefits and Networking | Google Cloud