Exam Cloud Digital Leader topic 1 question 65 discussion

"privately and securely" doesnt fit with peering.... Answer is B

Answer is C: Peer your on-premises data center to Googles Edge Network https://cloud.google.com/blog/products/networking/understanding-google-cloud-network-edge-points Scroll down to or Find "Cloud Interconnect POPs" where it says the following: "Dedicated Interconnect provides direct physical connections between your on-premises network and Google's network. Dedicated Interconnect enables you to efficiently transfer large amounts of data between networks."

Correct answer is- B. Create a VPC between your on-premises data center and your Google resources. Explanation: Creating a Virtual Private Cloud (VPC) allows you to establish a secure and private connection between your on-premises data center and Google Cloud resources. This setup minimizes latency by providing a direct, low-latency path for data transfer, ensuring that workloads can access on-premises data efficiently. A VPC also offers the flexibility to configure firewall rules and network settings to enhance security, making it an ideal solution for accessing sensitive data.

B. Create a VPC between your on-premises data center and your Google resources Here’s why: Private Connectivity: Creating a Virtual Private Cloud (VPC) with a dedicated connection like Cloud Interconnect (which can be either Dedicated Interconnect or Partner Interconnect) provides a secure and high-performance network link between your on-premises data center and Google Cloud. This setup ensures that your data travels through a private network, minimizing exposure to the public internet and thus increasing security. Low Latency: Using Cloud Interconnect, you can achieve low-latency connections between your on-premises infrastructure and Google Cloud resources, which is crucial for workloads that require fast and reliable data access.

I vote B for correct answer

Direct Peering documentation mostly talk about use-cases where on-prem resources need to hit Google services and in fact specifically calls out that it "Does not provide direct access to VPC network resources that have only internal IP addresses." Therefore, the correct answer is B.

B is correct

I think it should be C. As there is large amiunt of data that require low latency for which C is correct.

C IS RIGHT

B is correct

create a VPC between your on-premises data center and your Google resources. This can be achieved by using Private Google Access for on-premises hosts, which provides a way for on-premises systems to connect to Google APIs and services by routing traffic through a Cloud VPN tunnel or a VLAN attachment for Cloud Interconnect. This solution should minimize latency as traffic is routed through a Cloud VPN tunnel or a VLAN attachment for Cloud Interconnect, instead of traversing the public internet.

"privately and securely"

Creating a Virtual Private Cloud (VPC) between your on-premises data center and Google Cloud allows for a private and secure network connection. It provides a dedicated network environment for your organization, allowing your compute workloads in Google Cloud to privately and securely access your on-premises data. This option helps minimize latency and ensures a direct and controlled connection between your on-premises infrastructure and Google Cloud resources.

The correct answer is C. This cant't be B for these two reasons. VPC alone doesn't provide a secure connection. It requires a VPN. Then, the question also state to minimize latency which is actually the main weakness of any VPN. Therefore, B is not an option

Like jexmtropicscheatchatya

Option C is incorrect because peering your on-premises data center to Google's Edge Network is only used to improve the network performance between your on-premises network and Google's cloud services. It does not provide a secure way to access on-premises data from Google Cloud. A Virtual Private Cloud (VPC) with a VPN or Cloud Interconnect provides a secure way to privately access on-premises data from Google Cloud.

VPC is a virtual version of a physical network that is implemented inside of Google's production network.