Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial enterprise operates four 100-Gbps Dedicated Interconnect connections across two metropolitan areas and two Google Cloud regions to support real-time disaster recovery replication and multi-terabyte analytics. The connections are active with existing unencrypted VLAN attachments. You must encrypt traffic between the on-premises edge routers and Google's peering edge routers while meeting these requirements:
Which encryption strategy should you implement?
MACsec for Cloud Interconnect implements the IEEE 802.1AE standard to provide hardware-accelerated, Layer 2 encryption and integrity verification for Ethernet frames traveling between your on-premises edge routers and Google's peering edge routers. All 100-Gbps and 400-Gbps Dedicated Interconnect circuits support MACsec by default.
GCM-AES-256-XPN (Extended Packet Numbering) prevents dropped packets on high-bandwidth links when the control plane is heavily loaded.failOpen to false enforces a fail-closed posture that drops all traffic if a MACsec Key Agreement (MKA) session fails to establish. MACsec also supports hitless key rotation for up to five pre-shared keys (CAK/CKN pairs).AES_256_CMAC for CAK derivation, a 28,800-second SAK rekey interval, and Secure Channel Identifier (SCI) support.Compared to HA VPN over Cloud Interconnect or self-managed VM-based VPNs, MACsec with GCM-AES-256-XPN delivers deterministic 100-Gbps line-rate performance at zero incremental cost while enforcing strict fail-closed link security on existing Dedicated Interconnect infrastructure.
HA VPN over Cloud Interconnect is a Google-managed Layer 3 IPsec encryption solution that establishes HA VPN tunnels across Cloud Interconnect VLAN attachments. It provides end-to-end IPsec encryption between on-premises VPN gateways and VPC networks without traversing the public internet, making it suitable for compliance requirements over third-party Partner Interconnect networks.
You needed end-to-end Layer 3 IPsec encryption across a third-party Partner Interconnect provider network or into the VPC fabric, with throughput per attachment below 50 Gbps and tolerance for minor IPsec latency and MTU overhead.
A self-managed VPN gateway uses Compute Engine virtual machines running third-party or open-source IPsec software—such as strongSwan—assigned internal IP addresses inside a VPC network. On-premises VPN devices establish IPsec tunnels to these VM appliances across existing Dedicated Interconnect VLAN attachments.
You required end-to-end Layer 3 encryption terminating directly inside a VPC network with custom third-party network virtual appliance (NVA) security features and had throughput well below hardware line rate.
This approach activates IEEE 802.1AE MACsec on existing 100-Gbps Dedicated Interconnect links using the standard GCM-AES-256 cipher suite (without Extended Packet Numbering) and enables fail-open behavior (failOpen: true), allowing traffic to fall back to unencrypted forwarding if key negotiation fails.
GCM-AES-256 is supported on Cloud Interconnect, it uses a 32-bit packet number space that forces frequent Secure Association Key (SAK) rekeying under heavy traffic. On high-bandwidth 100-Gbps links sustaining 60 Gbps and 1 million+ pps, this can overload the control plane and cause dropped packets.failOpen to true permits Google's edge routers and your on-premises routers to pass unencrypted cleartext traffic whenever an MKA session cannot be established (such as during a key mismatch or protocol error), directly violating the requirement to drop all traffic if key negotiation fails.GCM-AES-256-XPN uses 64-bit Extended Packet Numbering to prevent packet-number exhaustion and control-plane overload on 100-Gbps and 400-Gbps circuits.failOpen is true, LACP links remain ACTIVE and unicast packet counters increment even when macsec.operational is false, masking security failures unless monitored explicitly.The cipher suite were changed to GCM-AES-256-XPN and failOpen were set to false (fail-closed), with VLAN attachments drained before activation.
Even with the proper cipher suite, production environments should avoid failOpen: true and instead use MACsec's hitless key rotation (up to five keys) to update CAK/CKN pairs without interrupting encrypted sessions.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated