Versa Networks VNX301 Exam Questions

The correct answer is A. Versa throughput troubleshooting documentation includes a specific section titled Check that Packets Are not Dropped by CoS. It states that if a CoS shaper or rate limiter is configured on the VOS device, it may drop packets when traffic exceeds the configured shaping rate. To check whether CoS is dropping packets, Versa recommends commands including show class-of-services interfaces brief and show class-of-services interfaces detail interface-name.

The detailed interface output displays traffic statistics such as TX packets, TX packets dropped, TX bytes, TX bytes dropped, and per-traffic-class drops. This is exactly the evidence needed to confirm whether shaping or QoS enforcement is causing the observed loss.

show alarms last-n 10 may reveal major events but will not provide per-interface CoS drop counters. show system uptime only indicates how long the system has been running. show cgnat tenants is relevant for NAT state and tenant CGNAT resources, not QoS drops.

In the exhibit, the Add Associate Interface/Network window has Interface selected, and the interface name is set to vni-0/0. The DSCP rewrite option is not available because rewrite behavior is intended to be applied at the network association level for the WAN network, not directly while associating only the physical/logical interface. For WAN-facing CoS, the scheduler and shaping parameters can be attached to an interface, but DSCP rewrite policies are applied to remark traffic as it exits through a network context.

Versa SD-WAN design documentation explains that QoS rewrite rules rewrite packet QoS attributes as packets leave the VOS device, and that rewrite rules can modify IEEE 802.1p bits, IPv4 TOS/DSCP bits, and IPv6 traffic class bits. It also explains that a rewrite policy is commonly applied on a WAN network to remark traffic based on the forwarding class and loss priority assigned by QoS or App QoS policies. In the design example, Versa explicitly describes applying a QoS propagation or rewrite policy on the MPLS WAN network to remark traffic to a DSCP value. Therefore, the issue is the association type: it is set to Interface, not Network.

The correct answer is A. Versa's handy troubleshooting CLI command reference lists show system package-info as the command used to view information about the VOS software image running on the CPE.

This command is useful before upgrade planning because it confirms the installed software package and helps validate whether the device is on the expected release. Administrators can compare the running version against the target upgrade image, verify upgrade prerequisites, and ensure that branch and Controller releases are compatible with required features such as internet speed testing, SD-WAN policy behavior, or security services.

show system uptime only tells how long the system has been running. show interfaces brief provides operational and administrative interface status, MAC address, tenant, VRF, and IP address information. show class-of-services interfaces brief helps troubleshoot QoS or shaping behavior. None of those commands directly identifies the VOS software package. Therefore, for checking the running image before an upgrade, the correct command is show system package-info.

The correct answer is A. In Versa Secure SD-WAN onboarding, the branch moves through three staging phases before becoming fully operational. Versa documentation states that in Stage 3, Versa Director pushes the stage-three configuration to the branch device over the IKE session and reboots the branch. After this stage, the branch becomes fully operational and is part of the customer SD-WAN network. At this point, IKE and IPsec sessions are created between the branch and Controller, and VXLAN and ESP sessions are created between branch to branch.

This distinction is important because the Controller connection is used for SD-WAN control-plane functions, while branch-to-branch overlay communication uses tunnel encapsulation for data forwarding. The documentation also notes that branch-to-branch ESP is maintained using a lightweight DH key-pair proprietary protocol.

Options B, C, and D are incorrect. HTTPS to Director alone does not represent the complete SD-WAN operational tunnel state. BGP to Analytics is not the required operational tunnel set. GRE-only tunnels without IPsec do not match the Versa Stage 3 SD-WAN tunnel behavior described in the staging documentation.

The correct answer is B. The exhibit shows the branch interface summary in Versa Director with a Live Data column. To populate real-time bandwidth graphs for WAN circuits, the administrator must select Live Data for the WAN interfaces that need to be monitored. Versa monitoring documentation states that, from a Director node, you can monitor VOS devices and organizations, and that Director, together with Versa Analytics, can poll VOS devices in real time to understand what is happening on the devices. This real-time information can be displayed to assist with troubleshooting.

Because the question asks for the current bandwidth of each WAN circuit, historical analytics alone is not sufficient. The dashboard must poll live statistics from the selected WAN circuits. In the exhibit, not all WAN interfaces appear to have Live Data selected; therefore, the graph is not populated for all circuits. Refreshing the page does not enable polling and will not solve the missing data condition. Selecting only MPLS would populate only the MPLS circuit, not all WAN circuits. Unselecting and reselecting only the INET circuit would affect only that one interface. Therefore, Live Data must be selected for all WAN circuits whose current bandwidth should be displayed.