Which two statements are true about the differences between a stateful firewall and a next-generation firewall (NGFW) in a Versa solution? (Choose two.)
The correct answers are A and D. A Versa stateful firewall primarily enforces security by tracking connection state and matching packet/session information such as source, destination, zones, services, protocol, and L3/L4 attributes. Versa's CLI configuration guide shows stateful firewall access-policy match options for source and destination addresses, services, IP version, IP flags, DSCP, TTL, and also optional application and URL-category match fields when enhanced services are available.
A Versa NGFW extends this inspection model by adding deeper Layer 7 and UTM capabilities, such as IDS/IPS, antivirus, URL filtering, file or data filtering, and application-aware enforcement. Versa's SD-WAN design guide specifically describes internet security using the Versa next-generation firewall with unified threat management features, including IDS/IPS and antivirus inspection for DIA traffic. Licensing is also a valid distinction: Versa's SD-WAN licensing overview describes NGFW features as part of solution tiers, so the availability of advanced security functions depends on the licensed tier or subscription
A branch has correct underlay speed and no asymmetric SD-WAN paths, but users still report packet loss during large transfers. You suspect QoS shaping is dropping traffic. Which command is most appropriate to verify interface-level CoS drops?
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.
Examine the exhibit below. You are configuring Class of Service on a WAN-facing network interface, and you want to perform DSCP rewrite on the packets that are forwarded to the WAN. However, you are not able to turn on DSCP rewrite. Referring to the exhibit, what is the cause of this issue?
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.
You need to determine the VOS image currently running on a branch CPE before scheduling a software upgrade. Which command provides this information?
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.
A branch device has completed Stage 3 onboarding. Which set of tunnels or sessions should exist after the device becomes fully operational in the customer SD-WAN network?
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.
Magnus Esposito
8 hours agoAdnan Farooqi
8 days agoShruti Nair
25 days agoAstrid Ferrari
1 month agoClara Gonzalez
1 month agoMing Sato
2 months agoJohn King
2 months agoVikram Pandey
2 months ago