Module 4: Virtual Machines and Networks in the Cloud

Looking for ‘Google Cloud Fundamentals: Core Infrastructure Module 4 Answers’?

In this post, I provide complete, accurate, and detailed explanations for the answers to Module 4: Virtual Machines and Networks in the Cloud of Course 2: Google Cloud Fundamentals: Core Infrastructure – Preparing for Google Cloud Certification: Cloud Developer Professional Certificate

Whether you’re preparing for quizzes or brushing up on your knowledge, these insights will help you master the concepts effectively. Let’s dive into the correct answers and detailed explanations for each question!

Quiz

Graded Assignment

1. In Google Cloud VPCs, what scope do subnets have?

  • Zonal
  • Regional ✅
  • Global
  • Multi-regional

Explanation:
In Google Cloud VPC (Virtual Private Cloud), subnets are regional—this means they span all zones within a region. Unlike traditional networking, where subnets are often tied to specific zones, Google Cloud subnets allow resources in different zones within the same region to communicate without needing external routing.

2. What is the main reason customers choose Preemptible VMs?

  • To improve performance.
  • To reduce cost. ✅
  • To use custom machine types.
  • To reduce cost on premium operating systems.

Explanation:
Preemptible VMs (now called Spot VMs) are short-lived, low-cost virtual machines that Google Cloud can shut down at any time if resources are needed elsewhere. They are ideal for cost-saving in workloads that can tolerate interruptions, such as batch processing, machine learning training, and fault-tolerant distributed computing.

3. For which of these interconnect options is a Service Level Agreement available?

  • Dedicated Interconnect ✅
  • Standard Network Tier
  • Direct Peering
  • Carrier Peering

Explanation:
A Dedicated Interconnect provides a private, high-bandwidth connection between a customer’s on-premises network and Google Cloud. It offers a Service Level Agreement (SLA) for guaranteed availability and performance.
Other options, such as Direct Peering and Carrier Peering, do not have SLAs since they rely on third-party networks.

4. How does Cloud Load Balancing allow you to balance HTTP-based traffic?

  • Across multiple Compute Engine regions. ✅
  • Across multiple virtual machine instances in a single Compute Engine region.
  • Across multiple Google Cloud Platform services.
  • Across multiple physical machines in a single data center.

Explanation:
Cloud Load Balancing in Google Cloud is fully distributed and global. For HTTP-based traffic, it can balance requests across multiple Compute Engine regions to optimize availability, latency, and performance.
Other options like balancing across a single region or specific virtual machines are more limited in scope.

Related contents:

Module 2: Introducing Google Cloud
Module 3: Resources and Access in the Cloud
Module 5: Storage in the Cloud
Module 6: Containers in the Cloud
Module 7: Applications in the Cloud
Module 8: Prompt Engineering

You might also like:

Course 3:

Leave a Reply