Notifications
Clear all
Topic starter
One of your customers used to have a private data center. While within their data center itself, they were consuming some Google services via API calls and other public, well-known addresses published by Google. Now they're evacuating their private data center and are moving to Google Cloud.
Could they improve some of their existing architecture with respect to security?
- A . Use VPC Peering with the Google Cloud organization so that you can directly use services using only private IPs.
B . Use private addresses only. No additional configuration is required. All Google services will be accessible within Google Cloud on private addresses.
C . Use Shared VPCs with the Google Cloud organization so that you can directly use services using only private IPs.
D . Enable Private Google Access so that they can remove public IP addresses.
Suggested Answer: D
Explanation:
"VM instances that only have internal IP addresses (no external IP addresses) can use Private Google Access. They can reach the external IP addresses of Google APIs and services. f you disable Private Google Access, the VM instances can no longer reach Google APIs and services; they can only send traffic within the VPC network."
Explanation:
"VM instances that only have internal IP addresses (no external IP addresses) can use Private Google Access. They can reach the external IP addresses of Google APIs and services. f you disable Private Google Access, the VM instances can no longer reach Google APIs and services; they can only send traffic within the VPC network."
Graphical user interface, text, application
Description automatically generated
https://cloud.google.com/vpc/docs/private-google-access
Posted : 10/02/2023 6:42 pm