A company is running workloads in a dedicated server room. They must only be accessed from within the private company network. You need to connect to these workloads from Compute Engine instances…

Question

Options

• AConfigure the project with Cloud VPN.
• BConfigure the project with Shared VPC.
• CConfigure the project with Cloud Interconnect.
• DConfigure the project with VPC peering.
• EConfigure all Compute Engine instances with Private Access.

• A
  80% (40)
• B
  4% (2)
• D
  10% (5)
• E
  6% (3)

Explanation

Cloud VPN (A) and Cloud Interconnect (C) are correct because both establish private, hybrid connectivity between an on-premises network and GCP - exactly what's needed to reach workloads in a dedicated server room without exposing them to the public internet. Cloud VPN does this over an encrypted IPsec tunnel, while Cloud Interconnect uses a dedicated or partner-managed physical link for higher bandwidth and lower latency.

Shared VPC (B) is wrong because it shares a GCP VPC network across multiple GCP projects - it has nothing to do with on-premises connectivity. VPC Peering (D) is also wrong for the same reason: it connects two GCP VPC networks together, not GCP to an on-premises environment. Private Google Access (E) allows VMs without public IPs to reach Google APIs and services, not your own on-premises servers.

Memory tip: When the question involves a dedicated server room, data center, or on-premises network, the answer will always be one of the two hybrid connectivity options - VPN (encrypted tunnel over internet) or Interconnect (dedicated physical link). If the options involve Shared VPC, VPC Peering, or Private Access, those are all cloud-to-cloud or cloud-to-Google-services solutions and can be safely eliminated for on-premises scenarios.

No community discussion yet for this question.