# Free 3V0-25.25 practice questions

> 10 free 3V0-25.25 practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/vmware-3v0-25-25/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/vmware-3v0-25-25/

### Question 1 of 10

A service provider is designing VCF 9.0 VPC connectivity for a tenant. Workloads in private VPC subnets must reach the internet through source NAT, and the tenant also needs gateway firewall rules on north-south traffic. Which Transit Gateway connectivity design meets these requirements?

- A. Distributed connectivity using a distributed VLAN connection, so that each ESX host routes VPC traffic directly to the physical VLAN gateway
- B. Distributed connectivity with public VPC subnets only, relying on the physical firewall upstream of the VLAN to translate the private address ranges
- C. Centralized connectivity without an Edge cluster, because the Transit Gateway always implements NAT and firewalling in the host distributed router
- D. Centralized connectivity through a gateway connection to a Tier-0 gateway hosted on an NSX Edge cluster, with default outbound NAT enabled

**Answer:** D

**Explanation:** NAT and gateway firewalling are centralized stateful services that run on an NSX Edge service router, so centralized Transit Gateway connectivity through a Tier-0 on an Edge cluster is required, with default outbound NAT providing SNAT for private subnets. Distributed connectivity lets traffic leave the hosts directly on a VLAN without Edges, which gives up these Edge-based stateful services. Moving NAT to an upstream physical firewall drops the NSX gateway firewall requirement. Centralized connectivity cannot exist without an Edge cluster, because the distributed router does not perform stateful NAT.

### Question 2 of 10

A VI workload domain cluster runs both tenant VMs and the NSX Edge VMs. Hosts have two 25 GbE uplinks. The architect wants Edge north-south traffic and host overlay traffic to share the uplinks with a predictable, deterministic path for each Edge BGP peering. Which design is recommended?

- A. Attach the Edge VM interfaces to VDS trunk port groups and pin each uplink VLAN segment with named teaming policies
- B. Configure LACP on the host uplinks and run each Edge BGP peering over the LAG so that the physical switch hashes each session
- C. Connect the Edge VM data interfaces directly to the host physical NICs with DirectPath I/O, bypassing the VDS for all Edge traffic
- D. Connect the Edge VM data interfaces to overlay segments, so that Edge uplink traffic is encapsulated and spread by the host TEPs

**Answer:** A

**Explanation:** The validated design connects Edge VM interfaces to VDS trunk port groups, and inside the Edge uses named teaming policies so that each uplink VLAN segment and BGP session follows one physical path. Edge uplinks are VLAN-based and are not placed on overlay segments. BGP peering of Edge VMs over a host LAG is not recommended, because the hashing makes the path to each peer unpredictable. DirectPath I/O removes the ability to share the NICs with host traffic and is not the recommended Edge VM design.

### Question 3 of 10

A Tier-0 gateway in active-active mode has two Edges, en01 and en02. Each Edge has one uplink to ToR-A and one to ToR-B. ToR-A fails, and en01 also loses its uplink to ToR-B. Which Tier-0 feature lets en01 keep forwarding the flows that the host DRs still send to it?

- A. Standby relocation, which moves the en01 service router to a spare Edge node that still has working uplinks
- B. Inter-SR routing, which builds iBGP between the Tier-0 SRs so en01 can reach the physical network via en02
- C. Route summarization on the Tier-0, which aggregates the routes from both ToR switches into a single prefix
- D. Graceful restart helper mode, which keeps the routes from ToR-A in the forwarding table of en01 until ToR-A returns

**Answer:** B

**Explanation:** Inter-SR routing builds iBGP sessions between the Tier-0 service routers over an internal overlay segment, so an SR that has lost its uplinks can forward traffic to a peer SR that still has external routes. Graceful restart only preserves routes during a control plane restart, not after a link failure. Standby relocation applies to standby service routers of active-standby gateways. Summarization does not provide a new path.

### Question 4 of 10

An administrator wants the Tier-0 gateway to advertise the subnets of overlay segments connected to its Tier-1 gateways to the physical routers over BGP. Which combination of settings is required?

- A. Static routes on the Tier-0 for each segment subnet, and BFD enabled on the Tier-0 BGP neighbors toward both ToR switches
- B. NAT IP advertisement on the Tier-0, and an IP prefix list allowing 0.0.0.0/0 on each BGP neighbor
- C. Route summarization on the Tier-1 gateways, and OSPF enabled on the Tier-0 external interfaces
- D. Connected segment advertisement on each Tier-1, plus Tier-1 subnets in the Tier-0 route redistribution

**Answer:** D

**Explanation:** Tier-1 gateways must advertise their connected segments to the Tier-0, and the Tier-0 must redistribute Tier-1 connected subnets into BGP before the physical routers learn them. Static routes and BFD are not required for this. Route summarization on Tier-1 does not exist in that form, and OSPF is not needed when BGP is used. NAT IP advertisement and a default-route prefix list do not advertise segment subnets.

### Question 5 of 10

Tenant VPC App-VPC has a Private - Transit Gateway subnet 10.50.1.0/24 and a Private - VPC subnet 192.168.10.0/24. A second VPC, DB-VPC, in the same project is attached to the same Transit Gateway. Which reachability is expected without any NAT rules?

- A. DB-VPC can reach both subnets, because all VPCs on one Transit Gateway share a single routing table for every subnet
- B. DB-VPC can reach 192.168.10.0/24 only, because Private - Transit Gateway subnets are hidden from other VPCs
- C. DB-VPC can reach 10.50.1.0/24, but cannot reach 192.168.10.0/24 because Private - VPC subnets stay inside App-VPC
- D. DB-VPC can reach neither subnet, because traffic between two VPCs always requires a public subnet and NAT

**Answer:** C

**Explanation:** Private - Transit Gateway subnets are routable between VPCs attached to the same Transit Gateway, while Private - VPC subnets are reachable only within their own VPC unless NAT is used. Private - VPC subnets are not shared across the Transit Gateway. Inter-VPC traffic does not require public subnets. Private - Transit Gateway subnets are designed to be visible to other VPCs on the Transit Gateway.

### Question 6 of 10

A segment for a legacy application must preserve the gateway IP 10.20.30.1/24 while the workloads are migrated from a VLAN into NSX. During the migration some VMs remain on VLAN 230 and some move to the overlay segment. Which configuration provides layer 2 adjacency during the migration?

- A. Create a VLAN segment for VLAN 230 in the overlay transport zone so that both groups share one broadcast domain
- B. Enable proxy ARP on the Tier-0 gateway so that VMs on both sides answer ARP for each other's addresses
- C. Attach an Edge bridge profile to the overlay segment that bridges it to VLAN 230 through an Edge cluster
- D. Configure the overlay segment with a gateway of 10.20.30.1/24 on a Tier-1 and add a static route on the physical router

**Answer:** C

**Explanation:** An Edge bridge extends an overlay segment into a VLAN through Edge nodes, so VMs on VLAN 230 and the overlay segment share one layer 2 domain during migration, and the gateway can stay on the physical router until cutover. Configuring the same gateway on a Tier-1 while the physical router still owns it causes a duplicate gateway rather than adjacency. VLAN segments belong to VLAN transport zones, not overlay ones. Proxy ARP on Tier-0 does not join two broadcast domains.

### Question 7 of 10

An application team needs inbound access from the internet to a web server at 172.16.10.20 behind a Tier-1 gateway, using public IP 203.0.113.25. Which configuration meets the requirement?

- A. A No-SNAT rule on the Tier-0 for the subnet 172.16.10.0/24, with the Tier-1 connected segments advertised to BGP
- B. A DNAT rule on the Tier-1 that translates 203.0.113.25 to 172.16.10.20, with NAT IPs advertised on the Tier-1 and redistributed on the Tier-0
- C. A reflexive NAT rule on the Tier-1 distributed router, which needs no Edge cluster and translates both directions
- D. An SNAT rule on the Tier-1 that translates 172.16.10.20 to 203.0.113.25, with NAT IPs advertised on the Tier-1

**Answer:** B

**Explanation:** Inbound access to a published IP needs DNAT from 203.0.113.25 to the internal address on a Tier-1 that has a service router, and the NAT IP must be advertised by the Tier-1 and redistributed by the Tier-0 so that the physical network can route to it. SNAT translates outbound source addresses only. NAT always needs a service router on an Edge, not the distributed router. A No-SNAT rule only exempts traffic from SNAT and does not publish the server.

### Question 8 of 10

An operations team wants to see which applications talk to each other across NSX segments, including flow volumes over the past 30 days, to plan micro-segmentation. Which VCF tool provides this?

- A. VCF Operations for networks, using flow analytics collected from NSX
- B. The NSX Manager dashboard, using the transport node status counters
- C. VCF Operations for logs, using the NSX content pack event dashboards
- D. NSX Traceflow, which records each flow between VMs for later review

**Answer:** A

**Explanation:** VCF Operations for networks collects flow data from NSX and vSphere, so it can show application dependencies, flow volumes over time, and micro-segmentation planning views. VCF Operations for logs analyses log events, not flow records. Traceflow injects a single synthetic packet to trace a path. The NSX Manager dashboard shows health and status, not historical flows.

### Question 9 of 10

A newly created segment Web-02 is connected to Tier-1 T1-Prod, but the physical network does not learn its subnet. Other segments on T1-Prod are reachable. What is the MOST likely cause?

- A. Web-02 is in a different overlay transport zone than T1-Prod, which hides its route from the physical routers
- B. Web-02 has a DHCP server profile assigned, which prevents the segment subnet from being advertised
- C. Web-02 uses the default IP discovery profile, which blocks the gateway address from being learned
- D. Web-02 was created with a subnet outside the IP prefix list or route map allowed on the Tier-0 BGP redistribution

**Answer:** D

**Explanation:** If other segments on the same Tier-1 are advertised, Tier-1 advertisement and Tier-0 redistribution are working, so a prefix list or route map that does not permit the new subnet is the most likely cause. DHCP profiles do not affect route advertisement. IP discovery profiles concern VM address learning. A segment in a different transport zone than the gateway's Edges and hosts could not be connected in that way and would show connectivity errors rather than only a missing route.

### Question 10 of 10

After an MTU change on the physical network, VMs on different hosts can ping each other with small packets but large file transfers between them stall. Which test from an ESX host best confirms an overlay MTU problem between TEPs?

- A. ping -s 1572 <remote VM IP> from the guest OS, with fragmentation allowed on the path
- B. traceroute from NSX Manager to the remote TEP IP, using the default packet size
- C. vmkping -I vmk0 -s 8972 <remote host management IP>, without the do-not-fragment flag
- D. vmkping ++netstack=vxlan -d -s 1572 <remote TEP IP>, sourced from the host TEP vmkernel interface

**Answer:** D

**Explanation:** vmkping on the vxlan netstack with the do-not-fragment flag and a 1572-byte payload (1600 bytes with headers) tests whether the TEP-to-TEP path really carries the overlay MTU. A guest ping with fragmentation allowed can succeed despite a TEP MTU problem. Testing over vmk0 checks the management network, not the TEP network, and without the do-not-fragment flag it hides MTU drops. NSX Manager is not on the TEP network, and a default-size traceroute does not test MTU.

Ready for a timed run? Take the free 15-question 3V0-25.25 mini exam: https://devopscodelab.com/app/exams/vmware-3v0-25-25/mini/

DevOpsCode Lab is not affiliated with VMware. 3V0-25.25 and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
