QuestionQ341

Designing and planning a cloud solution architecture

For this question, refer to the KnightMotives Automotive case study. As part of its cloud strategy, KnightMotives wants to migrate its virtual machines (VMs) to Google Cloud. The VMs host applications, database instances, and file servers. In the future, KnightMotives plans to modernize its landscape by adopting cloud-native technologies on Google Cloud. During modernization, minimal latency and operational overhead between the old and new landscapes will be crucial. You need to design the cloud architecture for the VM environment on Google Cloud while ensuring that a future modernization path will meet the technical requirements. What should you do?

  • A Create a Shared Virtual Private Cloud (VPC). and migrate the VMs to Compute Engine in a new project. During modernization, deploy each modernized workload in a dedicated Google Cloud project with its own VPC. Connect the two VPCs via an on-premises VPN.
  • B Create a Shared Virtual Private Cloud (VPC). Migrate the VMs to Compute Engine in a new project. During modernization, deploy each modernized workload in a dedicated Google Cloud project using the Shared VPC.
  • C Create a single private cloud on Google Cloud VMware Engine. Migrate the VMs using VMware HCX. During modernization, deploy the modernized workloads in a single Google Cloud project using a single VPC.
  • D Create a single private cloud on Google Cloud VMware Engine. Migrate the VMs using VMware HCX. During modernization, deploy each modernized workload in a dedicated Google Cloud project with its own VPC.
Explanation

Shared VPC enables resources in multiple service projects to use a common VPC network and communicate efficiently through internal IP addresses, while network administration, routes, and firewall policies remain centrally managed. Migrating the existing VMs to Compute Engine establishes a direct Google Cloud platform, and placing each modernized workload in its own service project on the same Shared VPC preserves project-level isolation without introducing separate-VPC VPN connectivity, associated latency, or additional operational overhead.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!