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.
Your organization uses HA VPN over Cloud Interconnect with IPv4 gateway interfaces to encrypt traffic across dedicated VLAN attachments. In the Cloud VPN Monitoring tab and Cloud Logging, you observe periodic throughput drops during Phase 2 CHILD_SA rekeying and silent drops for 1,400-byte UDP packets with the DF bit set.
Your current environment includes:
AES-GCM-16-256 and AES-CBC-256 (HMAC-SHA2-512-256)Which set of actions should you take to enforce proper MTU sizing, stabilize tunnel performance, and resolve the packet drops?
AES-CBC-256 with HMAC-SHA2-512-256 for a 1,386-byte payload MTU, and lower the VPC network MTU to 1,300 bytes without modifying firewall rules.This option relies on post-encapsulation fragmentation at the peer gateway, selects a non-AEAD cipher suite (AES-CBC-256 with HMAC-SHA2-512-256), and lowers the entire VPC network MTU to 1,300 bytes to avoid adding firewall rules.
AES-CBC-256 with HMAC-SHA2-512-256 (a non-AEAD combination) on an IPv4 HA VPN over Cloud Interconnect tunnel results in a 1,354-byte payload MTU, not 1,386 bytes. Only AEAD ciphers (such as AES-GCM-16-128, 192, or 256) achieve the 1,386-byte payload ceiling.HMAC-SHA2-512-256 consumes 32 bytes more overhead than AEAD), yielding 1,354 bytes (IPv4) or 1,334 bytes (IPv6) over Interconnect.No such configuration is valid for Cloud VPN, because post-encapsulation fragmentation is never supported and non-AEAD ciphers with HMAC-SHA2-512-256 cannot yield a 1,386-byte payload MTU.
AES-GCM-16-256 for a 1,406-byte payload MTU, and disable Path MTU Discovery on the Compute Engine VMs.This option applies standard internet-based HA VPN MTU values (1,460-byte gateway MTU and 1,406-byte payload MTU), attempts an in-place cipher edit on existing tunnels, and disables Path MTU Discovery (PMTUD) on the sending VMs.
DF-bit drops: Without prefragmentation on the peer and an ingress ICMP firewall rule for PMTUD, applications emitting 1,400-byte UDP packets with the DF bit set will continue to experience silent packet drops.| Connectivity Type | Gateway MTU | IPv4 AEAD Payload MTU | IPv6 AEAD Payload MTU |
|---|---|---|---|
| Standard HA VPN | 1,460 bytes | 1,406 bytes | 1,386 bytes |
| HA VPN over Interconnect | 1,440 bytes | 1,386 bytes | 1,366 bytes |
vpnTunnel resource.The architecture used standard HA VPN over the public internet (without Cloud Interconnect) and the tunnels were recreated from scratch while preserving ICMP ingress rules for PMTUD.
AES-GCM-16-256) for a deterministic 1,386-byte payload MTU, and add an ingress VPC firewall rule allowing ICMP traffic to the Compute Engine VMs.This solution aligns every layer of the HA VPN over Cloud Interconnect data path—the outer gateway encapsulation boundary, the inner IPsec cryptographic overhead, and the Path MTU Discovery (PMTUD) signaling path—to eliminate packet drops and cipher-induced MTU shifts.
CHILD_SA rekeying, which can cause negotiated ciphers to switch between AES-GCM-16-256 (AEAD) and AES-CBC-256 with HMAC-SHA2-512-256 (non-AEAD). Recreating the IKEv2 tunnels (since ciphers cannot be edited in place) to propose and accept only AES-GCM-16-256 locks the payload MTU at 1,386 bytes on IPv4 interfaces instead of fluctuating down to 1,354 bytes.DF-bit drops: When a Compute Engine VM sends a 1,400-byte UDP packet with the DF bit set over a 1,386-byte payload MTU tunnel, Cloud VPN drops the packet and sends an ICMP Fragmentation Needed message back to the sender. Adding an ingress allow firewall rule for ICMP ensures the VM receives this feedback and lowers its packet size via PMTUD.36,000 seconds Phase 1, 10,800 seconds Phase 2).Unlike modifying VPC-wide MTUs or using non-AEAD cipher suites that shrink the payload ceiling, this approach directly addresses the 1,440-byte gateway MTU, enforces a single high-efficiency AEAD cipher, and completes the ICMP feedback loop required for PMTUD.
AES-CBC-256 with HMAC-SHA2-512-256 ahead of AES-GCM-16-256.This option attempts to eliminate encapsulation fragmentation by raising the encrypted transport MTU to 1,500 bytes, relying on host-level TCP MSS clamping, and prioritizing a non-AEAD cipher suite ahead of an AEAD cipher in the IKEv2 proposal.
SYN and SYN-ACK headers during TCP handshakes (which Cloud VPN already handles automatically). It has no effect on UDP datagrams with the DF bit set, and without an ingress ICMP firewall rule, PMTUD still fails.AES-CBC-256 with HMAC-SHA2-512-256) ahead of an AEAD cipher (AES-GCM-16-256) violates Cloud VPN mixed-cipher rules (AEAD ciphers must be listed first) and retains a multi-cipher list that invites negotiation drift. Moreover, AES-CBC-256 with HMAC-SHA2-512-256 shrinks the HA VPN over Cloud Interconnect IPv4 payload MTU to 1,354 bytes, worsening fragmentation.Standard unencrypted Cloud Interconnect VLAN attachments were being configured to match a 1,500-byte VPC MTU for TCP-only workloads, without an IPsec overlay.
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