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 is migrating workloads across 10 Shared VPC networks to Google Cloud and plans to deploy Palo Alto Networks VM-Series virtual firewalls. Your security architecture must meet the following requirements:
Which firewall architecture should you implement?
nic0) sits behind the regional external passthrough Network Load Balancer, place the trust interface (nic2) behind an internal passthrough Network Load Balancer in a hub VPC, and connect the 10 Shared VPCs via VPC Network Peering with custom route exchange.This topology deploys Palo Alto Networks VM-Series network virtual appliances (NVAs) inside Managed Instance Groups (MIGs) across multiple zones, using VPC Network Peering in a hub-and-spoke layout rather than attaching dedicated NICs to every workload VPC. Each firewall VM only requires three network interfaces: untrust (nic0), management (nic1), and trust (nic2).
nic0 (the primary Compute Engine interface). Because Google Cloud external load balancers forward backend traffic exclusively to nic0, this swap enables the regional external passthrough Network Load Balancer to distribute inbound internet traffic directly to the firewall dataplane while preserving the original client source IP addresses.Compared to multi-NIC direct attachment, hub-and-spoke peering eliminates VM redeployment when adding VPCs and preserves full per-NIC throughput. Compared to an active/passive HA pair, MIGs scale horizontally beyond a single VM's throughput ceiling, and compared to native Cloud NGFW alone, VM-Series preserves unified Panorama governance.
In a multi-NIC deployment, a virtual firewall appliance attaches individual virtual network interfaces directly to separate VPC networks, acting as a Layer 3 router and Layer 7 inspection bridge between them without requiring VPC Network Peering.
The environment had five or fewer static VPC networks that never needed to grow, required direct NIC attachment to reach Private Services Access (PSA) services across peered boundaries, and did not need horizontal MIG autoscaling.
In large multi-VPC designs, architects use a hub-and-spoke VPC Network Peering topology with internal passthrough Network Load Balancers to decouple firewall scaling from the number of protected workload VPCs.
Cloud Next Generation Firewall (Cloud NGFW) Enterprise is Google Cloud's fully managed, distributed firewall service. Enforced directly at the hypervisor/VM boundary regardless of guest OS state, it supports organization-, folder-, and network-level policies, IAM-governed Tags, FQDN/geolocation filtering, Google Threat Intelligence, intrusion prevention (IPS), and TLS inspection.
The organization did not require Panorama policy consistency with on-premises appliances and wanted to minimize operational overhead by adopting a fully managed, serverless, distributed firewall with native IPS and TLS inspection.
In practice, organizations often adopt a defense-in-depth strategy that combines native Cloud NGFW rules for distributed micro-segmentation with third-party NGFW NVAs at transit boundaries when vendor-specific deep packet inspection or Panorama consistency is mandatory.
nic0 as the management interface, nic1 as the untrust interface behind the regional external passthrough Network Load Balancer, and nic3 for session synchronization.An active/passive high-availability (HA) deployment places two VM-Series appliances in separate unmanaged instance groups across two zones. Only the primary active firewall processes traffic via load balancer health checks, while an HA1 interface (nic1) synchronizes configuration and an HA2 interface (nic3) replicates active session state to the standby firewall.
nic0 as the management interface prevents the regional external passthrough Network Load Balancer from delivering inbound internet traffic to the untrust dataplane interface (nic1). Google Cloud external load balancers always forward backend traffic to nic0, so a management interface swap must be executed at deployment to make untrust nic0; otherwise, the VMs must be completely redeployed.nic0 and nic1 at boot, external passthrough and application load balancers cannot reach the firewall's untrust dataplane.The organization did not need horizontal autoscaling, required stateful session continuity during failover or direct IPsec tunnel termination on the appliance, and performed a management interface swap so nic0 served as the untrust interface.
Many engineers assume nic1 can act as an external load balancer backend simply by selecting that subnet during setup, but Compute Engine backend services always route external load-balanced packets to the instance's primary nic0 interface.
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