
Answer-first summary for fast verification
Answer: Non-transitive peered networks; where only directly peered networks can communicate, Ability to peer networks that belong to different Google Cloud organizations
The question asks for two security characteristics of VPC peering. Option B is correct because VPC peering is non-transitive, meaning only directly peered networks can communicate, which is a security feature that prevents unintended access through intermediate networks. Option C is correct because VPC peering allows peering across different Google Cloud organizations, enabling secure, private connectivity without exposing traffic to the public internet, which enhances security by keeping traffic within Google's network. Option A is incorrect as central management is not a feature of VPC peering; each VPC manages its own routes and firewalls. Option D is incorrect because firewall rules cannot use tags across peered networks, as confirmed by Google Cloud documentation and community comments. Option E is incorrect as sharing specific subnets is a feature of Shared VPC, not VPC peering. The community discussion strongly supports BC, with high upvotes and references to official documentation, while BD is less supported due to D being false.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Which two security features are associated with using VPC peering to connect two VPC networks? (Choose two.)
A
Central management of routes, firewalls, and VPNs for peered networks
B
Non-transitive peered networks; where only directly peered networks can communicate
C
Ability to peer networks that belong to different Google Cloud organizations
D
Firewall rules that can be created with a tag from one peered network to another peered network
E
Ability to share specific subnets across peered networks
No comments yet.