Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial services company wants to deploy new, modernized applications in the public cloud while keeping its existing legacy workloads in its on-premises data center. The company has the following business and technical requirements:
Which infrastructure model and Google Cloud approach best fits this scenario?
A cloud-first hybrid architecture is an infrastructure strategy in which an organization deploys all new workloads in a public cloud environment (such as Google Cloud) while keeping existing legacy workloads in their current on-premises environment. To bridge these two environments, an API management platform like Apigee modernizes legacy services by wrapping them in standardized API interfaces, unlocking their functionality and data for consumption by modern cloud applications.
Unlike full public cloud migrations that violate on-premises data residency and compliance constraints, or purely private deployments that miss out on public cloud scalability and managed services, a cloud-first hybrid model balances innovation with regulatory control. By combining Google Cloud for new workloads with Apigee for cross-environment integration, the company achieves immediate modernization without rewriting its core systems.
A multicloud architecture distributes workloads across more than one public cloud provider (such as Google Cloud and another cloud vendor). Combining this with a rehost (lift and shift) migration approach means moving existing on-premises applications directly to virtual machines in those public clouds with little to no modification to the underlying application code.
This approach would be suitable if the company had no regulatory restrictions keeping data on-premises, wanted to rapidly evacuate its data center without refactoring code, and needed to run workloads across multiple public cloud providers to meet specific interoperability or business continuity goals.
Distinguishing between hybrid and multicloud infrastructures is essential when analyzing business use cases. A hybrid cloud combines a private environment (on-premises or colocation) with a public cloud, whereas multicloud involves utilizing two or more public cloud platforms.
A private hosting environment, such as a colocation facility, is an infrastructure model where an organization outsources foundational physical infrastructure duties—including physical security, power, cooling, and network cabling—to an external service provider. However, the organization retains full responsibility for managing the virtualization platform, hypervisors, virtualized infrastructure, and all application resources running on top of that hardware.
This approach would be appropriate if the organization wanted to exit the business of managing building security, cooling, and power in its own on-premises data center, but regulatory or technical constraints made a public cloud deployment impossible and required the team to retain full control over the virtualization hypervisors.
Organizations often confuse private hosting environments with public cloud environments. In a public cloud like Google Cloud, the provider manages both the physical infrastructure and the resource virtualization hypervisor, allowing teams to focus on high-value application logic and fully managed services.
A rebuild migration (often referred to as remove and replace or rip and replace) is a modernization strategy in which an organization completely decommissions an existing legacy application and redesigns and rewrites it from scratch as a fully cloud-optimized application on Google Cloud. This model aims to eliminate legacy technical debt and rely entirely on public cloud infrastructure.
This strategy would be the right choice if the existing legacy application no longer satisfied current business requirements, relied on end-of-life third-party technology, incurred uneconomical licensing fees, and had no regulatory compliance barriers preventing its data from moving entirely to Google Cloud.
While IT modernization and hybrid cloud adoption are closely linked, organizations do not need to rewrite every legacy workload to benefit from the cloud. Using a hybrid architecture allows enterprises to preserve stable on-premises investments while innovating in Google Cloud.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated