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 operates a high-throughput parallel storage workload using Google Cloud Managed Lustre in an existing VPC network configured with the default 1,460-byte MTU. To reduce CPU overhead and maximize throughput for large sequential transfers, you must enable the maximum supported jumbo frame MTU on this VPC network while keeping all guest operating systems synchronized to prevent packet drops or suboptimal transmission rates.
The VPC hosts two types of Compute Engine instances using gVNIC driver v1.3+:
Which configuration and procedure should you implement?
Configuring a VPC network MTU of 8,896 bytes enables the maximum supported jumbo frame size in Google Cloud, allowing Compute Engine instances using gVNIC v1.3+ to transmit significantly larger IP payloads per Ethernet frame while synchronizing every guest OS interface to the exact network boundary.
8,896 bytes): High-throughput storage systems like Google Cloud Managed Lustre benefit directly from the maximum 8,896-byte VPC MTU, cutting packet volume by more than half compared to 1,460 bytes, reducing CPU interrupt overhead, and increasing throughput by up to 10%.--mtu=8896 via gcloud or the API prevents mid-flight mismatches and hypervisor desynchronization.8,896 bytes via DHCP Option 26.1,460-byte MTU and do not honor DHCP Option 26, updating both the OS IP interface (netsh or Set-NetIPInterface) and the adapter driver's Init.MTUSize registry property (devmgmt.msc or Set-NetAdapterAdvancedProperty) ensures full 8,896-byte alignment.8,896-byte MTU across the VPC and all guest NICs prevents packet drops for both TCP and UDP flows.Unlike 1,460 or 1,500 bytes, 8,896 bytes maximizes payload efficiency within Google Cloud's valid 1,300–8,896 byte VPC range, and following the stop-update-start workflow with OS-specific Windows driver updates is the only supported method to synchronize an existing heterogeneous VPC without packet discards.
In traditional on-premises data centers and specialized Bare Metal Solution private networks, 9,000-byte jumbo frames are standard, leading administrators to attempt configuring 9,000 bytes on a Google Cloud VPC through the web console.
1,300 bytes and 8,896 bytes inclusive; attempting to configure 9,000 bytes is rejected by the Compute Engine API and gcloud.gcloud compute networks update CLI command or the Compute Engine REST API (networks.patch).9,000 bytes locally, the value cannot match the VPC network ceiling of 8,896 bytes, risking packet discards on outbound frames larger than 8,896 bytes.1,300 to 8,896 bytes (1,460 default, 1,500 standard Ethernet, 8,244 for specific A3 GPU header-split configurations, and 8,896 maximum).8,896 bytes (rather than 9,000) to reserve room for virtualized network encapsulation overhead.You were configuring a private network on Google Cloud Bare Metal Solution (such as for Oracle RAC clusters), where 9,000-byte jumbo frames are supported and configured on bonded server interfaces.
Always verify workload-specific MTU recommendations before provisioning: while Managed Lustre, Cloud TPU, and A3 Ultra/A4 VMs use 8,896 bytes, A3 Mega, A3 High, and A3 Edge GPU VMs recommend 8,244 bytes.
Modifying the network interface MTU strictly inside the guest operating system instructs the local TCP/IP stack and virtual NIC driver to emit larger IP packets without altering the underlying VPC network MTU boundary enforced by Google Cloud's virtualized switching fabric.
1,460 bytes, any packet exceeding that limit emitted by a guest OS configured for 8,896 bytes is dropped by Google Cloud.ip link on Linux is non-persistent across reboots and conflicts with DHCP Option 26 leases.The VPC network MTU had already been raised to 8,896 bytes during creation or a maintenance window, and you only needed to align a custom OS image or Windows Server guest interface downward or up to match the VPC network's 8,896-byte ceiling.
For a Compute Engine instance to transmit and receive jumbo frames, its virtual NIC must connect to a VPC network whose configured MTU is equal to or larger than the guest NIC's MTU.
Running gcloud compute networks update changes the VPC network MTU property at the control-plane level, while an in-guest OS reboot restarts the operating system kernel without cycling the underlying Compute Engine hypervisor virtual NIC allocation.
1,460-byte MTU and ignore DHCP Option 26 for MTU assignment, leaving Windows VMs stuck at suboptimal frame sizes.TERMINATED (stopped) state prior to altering the VPC MTU.1,460 bytes while Linux storage VMs operate at 8,896 bytes degrades Windows-to-Linux throughput and risks drops for non-TCP traffic.No such live-update procedure is supported safely; to achieve zero-downtime MTU transitions on active workloads, you must instead create a new VPC network with an 8,896-byte MTU and migrate workloads incrementally rather than modifying the existing VPC in place.
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