A customer has purchased 10 Versa SD-WAN licenses. In this scenario, which statement is correct?
Answer : C
The correct answer is C. In Versa Secure SD-WAN, licensing and device management are centralized through Versa Director, not directly through the Controller. During zero-touch provisioning and staging, the branch device is brought under centralized management, and Director pushes the required staging and operational configuration. Versa staging documentation explains that during Stage 2 and Stage 3, Versa Director pushes configuration to the branch device, and after Stage 3 the branch becomes fully operational as part of the customer SD-WAN network.
Versa monitoring documentation also shows that the Director node provides license visibility, specifically stating that the Director monitoring view includes a License pane that displays information about the licenses installed on the VOS devices managed by the Director node. This confirms that license administration is handled from Director, not from the Controller. The Controller is responsible for SD-WAN control-plane functions and tunnel connectivity, but it is not the primary system for managing customer license subscriptions.
Option A is incomplete because the practical operational model is not simply receiving individual soft licenses. Option B incorrectly implies licenses are preloaded on physical CPEs as the key licensing method. Option D is incorrect because ZTP management and license subscription handling are not performed by the Controller.
A tenant has two internet circuits and one LTE backup circuit. The forwarding profile lists the internet circuits with priority 1 and LTE with priority 2. The next-hop selection method is Load Balance. What is the expected behavior while both internet circuits are healthy?
Answer : A
The correct answer is A. In Versa SD-WAN forwarding profiles, next-hop priorities define which circuits are preferred. When the Load Balance next-hop selection method is used and two circuits share the same priority, sessions can be distributed across those equal-priority paths as long as they are usable and SLA-compliant. A lower priority number represents a more preferred group than a higher priority number. Therefore, two circuits with priority 1 are preferred over LTE with priority 2.
In this scenario, both internet circuits are healthy and both have priority 1. The VOS device should load-balance sessions across those two circuits. LTE remains available as a lower-priority backup path and would normally be considered only when the preferred internet circuits are unavailable, fail path checks, or no longer meet the applicable policy conditions.
Traffic is not replicated because replication is a separate feature and not implied by Load Balance. The branch does not drop traffic while valid paths exist. LTE is not preferred merely because its priority number is higher; in path selection, priority 1 is preferred over priority 2.
A tenant uses CGNAT for internet breakout. You want to verify whether CGNAT rules, pools, static NAT entries, subscribers, and endpoint-independent mapping entries are programmed in the vsmd daemon for a tenant. Which command should you use after connecting to vsmd?
Answer : A
The correct answer is A. Versa CGNAT troubleshooting documentation provides commands to inspect CGNAT state inside the vsmd daemon. To view summary information about configured tenants, the document instructs administrators to issue show cgnat tenants. The sample output shows each tenant ID and counters such as the number of configured rules, pools, DS-Lite service chains, 6RD service chains, static NAT entries, subscribers, endpoint-independent mapping entries, endpoint-independent filtering entries, and softwires.
This command is especially useful when CGNAT configuration appears correct in Director but translation is not happening, because it confirms whether the runtime dataplane process actually has the tenant CGNAT state.
show interfaces brief shows interface status and IP addressing. show alarms shows event notifications, and show system uptime shows how long the system has been running. These are useful operational commands but do not show CGNAT tenant programming inside vsmd.
Examine the exhibit below. As an administrator of a Versa Secure SD-WAN, you are asked to find the current bandwidth of each WAN circuit used for SD-WAN connectivity in a branch, but the Director is not displaying any information for the WAN circuits. In this scenario, what should be done to get the graph populated for all WAN circuits?
Answer : B
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.
You are asked to ensure symmetric traffic flows between two SD-WAN branches. Which feature should be enabled to achieve this objective?
Answer : A
Symmetric Forwarding is the correct Versa SD-WAN feature for ensuring that return traffic between SD-WAN branches follows the same SD-WAN path on which the forward traffic was received. Versa documentation for SD-WAN traffic steering describes Symmetric forwarding as the option that specifies the path for reverse-direction traffic, meaning whether traffic returning from the destination branch to the originating branch should be sent on the same path on which it arrived. It further states that enabling symmetric traffic forwarding determines the reverse path for traffic returning from the destination branch to the originating branch.
This is different from Symmetric Routing, which is a routing design goal or behavior, not the Versa SD-WAN forwarding-profile feature named in the product documentation. Equal-Cost Multipath can distribute flows across equal-cost routes, but it does not specifically guarantee that both directions of the same SD-WAN session use the same path. Packet Striping is used to split or distribute packets across multiple links for performance, not to enforce bidirectional path symmetry. Therefore, the verified Versa feature to enable is Symmetric Forwarding.
While troubleshooting the SD-WAN data path, you run show vsf tunnel access-circuits ... detail and see the following encapsulation chain: VMLH, MPLS-over-GRE, IPsec-ESP, and VXLAN. What does this output primarily confirm?
Answer : B
The correct answer is B. Versa's SD-WAN data-path troubleshooting documentation shows that show vsf tunnel access-circuits ... detail can display the access-circuit state and encapsulation chain used for tunnel forwarding. In the example, the output lists multiple encapsulations, including VMLH, MPLS-over-GRE, IPsec-ESP, and VXLAN. It also shows transport details such as source IP, destination IP, UDP transport, tunnel MTU, SPI values, and SLA state.
This confirms that the VOS data plane has built the SD-WAN tunnel encapsulation stack required to forward overlay traffic across the underlay. IPsec-ESP in the chain indicates encrypted tunnel handling, while VXLAN and other encapsulation components are part of the SD-WAN overlay forwarding structure.
The output does not indicate simple bridging, plain-text-only GRE, or bypass of the VOS data plane. Instead, it proves that the packet path is being processed through the VOS tunnel forwarding framework and that the administrator is looking at the SD-WAN access-circuit tunnel state.
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?
Answer : A
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.