VNX301 Versa Certified SD-WAN Specialist (VNX300) Questions and Answers

The correct answer is B . Versa documentation for internet speed tests explains that when you run an internet speed test from a Director node, it creates approximately 200 sessions . This is useful for measuring aggregate throughput, but it does not represent the behavior of a single application flow. The same documentation states that you can run a speed test with a single session from the device CLI, and that this is useful for simulating file transfer rates when using SCP or FTP .

Therefore, when the goal is to understand how a single file transfer behaves, the CLI-based single-session test is the best option. A default Director-based test may produce higher aggregate results because multiple sessions can use parallelism and better fill the pipe.

show interfaces brief is useful for interface status and addressing, but it does not measure file-transfer throughput. SLA latency is useful for path-quality monitoring, but latency alone does not show single-session TCP throughput.

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 C . Versa documentation states that for Releases 22.1.3 and later , the speed test factors in network latency to derive results. In these releases, the speed test is performed in three stages : a ping test, an upload test, and a download test. The ping test calculates link latency, and the speed test uses that latency data while performing the upload and download portions.

The same documentation notes that the speed test can measure bandwidth speeds up to 1 Gbps, with actual measurement depending on factors such as in-path shapers and latency. It also states that the test may use up to 45 MB of data per upload or download in the best case and 90 MB for a complete test.

Older releases behave differently. For Releases 21.2 and earlier, the speed test is performed in two stages: upload and download. Therefore, because the question specifically states Release 22.1.3 on both client and server, the correct sequence is ping, upload, and download.

The correct answer is LOCAL_PREF . In BGP, the Local Preference attribute is used inside an autonomous system to influence which exit path is preferred for outbound traffic. In this scenario, the Versa Secure SD-WAN CPE receives routes from two upstream service providers, SP1 and SP2. To prefer routes learned from AS 64515 over routes learned from AS 64519, you would apply a BGP import or route policy that assigns a higher local preference to routes received from SP1. Versa SD-WAN design guidance shows this exact routing concept: an import policy can manipulate the Local-Pref attribute to prefer one advertised route path over another. The Versa output examples also display “Local Preference” as a BGP route attribute used in route selection.

MULTI_EXIT_DISC, or MED, is generally used to influence how a neighboring AS enters your AS, not how your CPE prefers routes learned from different upstreams. ORIGIN is part of BGP best-path selection but is not normally the administrative tool used to prefer one provider. NEXT_HOP identifies the next-hop address and does not directly define route preference.

The correct answer is A . Versa monitoring documentation states that when an administrator selects a provider organization in Director and opens the Summary tab, the screen displays several panes. The Asset Inventory pane displays the number of tenants, SD-WAN branches, SD-WAN Controller nodes, vCPEs, SD-WAN hubs, uCPEs, Director nodes, and Analytics nodes in the organization.

This pane is useful for quickly validating the managed estate and confirming whether expected infrastructure objects exist under the provider organization. It also provides a Details button to display asset information in tabular format, which can help during audits or operational checks.

Package Information shows software package details for the selected node, not organization-wide inventory. Uptime shows how long a node and its software have been running. High Availability shows Director HA information. These panes are useful, but they do not provide the organization-level asset count requested in the question.

The correct answer is A . Versa documentation states that from a Director node, administrators can monitor the Director node itself, provider organizations, tenants, and VOS devices. The procedure begins by selecting the Monitor tab in the top menu bar. When a Director node is selected, the monitor screen displays panes such as System Detail , Recent Events , Package Information , Uptime , High Availability , and License .

This view is intended for operational monitoring and troubleshooting. It allows administrators to see system resource status, recent alarms and events, software package details, uptime, HA configuration, and licenses installed on managed VOS devices.

Workflows are used for provisioning and template-based configuration, not monitoring these system panes. Analytics Search is useful for querying logs and flow records, but it is not the Director system-monitoring screen described in the question. Administration > Connectors relates to integration and resource connectivity rather than Director node health and license monitoring. Therefore, the correct location is the Monitor tab.

The correct answer is A . Versa branch troubleshooting documentation states that the provider organization should have MP-BGP configured for SD-WAN deployments so that notifications for all relevant branch events are delivered to the Versa Director node. This is significant during onboarding because branch lifecycle events, such as branch-connect and branch-disconnect, help Director determine where the branch is in the staging process and whether the next configuration push should occur.

MP-BGP does not replace IKE or IPsec. The branch still establishes IKE/IPsec to the staging server or Controller depending on the staging phase. MP-BGP also has nothing to do with URL filtering category updates. While BGP can be used in LAN or WAN routing designs, the specific issue described here concerns provider-organization SD-WAN control-plane event delivery.

Therefore, if branch lifecycle events are not appearing properly, validating provider-organization MP-BGP configuration is part of the correct troubleshooting workflow, especially in addition to checking data-path and IPsec connectivity.

The correct answers are A and C . Versa supports upgrading deployed VOS branch devices either directly on the VOS appliance or centrally through Versa Director. The Director-based method is performed from the Administration > Appliances area: Versa documentation says to select one or more Controller nodes or VOS devices, click the Upgrade Selected Appliances icon, choose the software image package, and proceed with the appliance upgrade. The same upgrade procedure is referenced for remaining VOS branch devices, including the option to upgrade branches individually or all at once.

A CLI-based upgrade using a software .bin package is also a valid operational method when the image is copied to the device and installed locally, particularly for controlled or recovery-style maintenance. Option B is not the best answer for already deployed branch upgrades because the Preferred Software Version field applies to zero-touch provisioning; Versa states that during ZTP, Director upgrades a branch to the preferred version if applicable. That setting influences onboarding behavior, not the normal upgrade workflow for already deployed branches. Option D is incorrect because System > Director Upgrade is used to upgrade the Versa Director node itself, not VOS branch appliances.

The correct answer is B . In the exhibit, Versa Director shows multiple branch interfaces and a Live Data column. To populate the bandwidth graph with current real-time statistics for all WAN circuits, Live Data must be selected for each WAN circuit that should be monitored. Versa documentation states that from a Director node, administrators can monitor VOS devices, provider organizations, tenants, events, and alarms. It also explains that Versa Director, together with Versa Analytics, can poll VOS devices in real time to provide visibility into what is happening on those devices and to assist with troubleshooting.

Because the requirement is to find the current bandwidth of each WAN circuit, simply refreshing the page is not enough. Refreshing only reloads the dashboard; it does not enable real-time polling for interfaces that are not selected. Selecting Live Data only for MPLS circuits would populate only MPLS-related data and would not satisfy the requirement for all WAN circuits. Unselecting and reselecting only the INET circuit affects only that one circuit. Therefore, the correct operational step is to enable Live Data for all WAN circuits shown in the branch interface dashboard.

In Versa SD-WAN, a Spoke-to-Hub-Only topology is specifically designed for deployments where spoke branches communicate only with hub resources and not with other spokes. Versa’s SD-WAN design documentation states that in a spoke-to-hub-only topology, the default behavior is that only hub routes are advertised, and spoke routes are not re-advertised by the hub branch. It also explains that this topology is used when spokes do not have to communicate with each other.

Even though the hub in the exhibit advertises a default route, that does not change the topology behavior into spoke-to-spoke communication. The default route can attract unknown traffic from the spokes toward the hub, but the Spoke-to-Hub-Only policy prevents the spoke prefixes from being redistributed or imported in a way that allows spoke-to-spoke reachability. Versa documentation further shows that spoke routes are filtered using BGP communities and import policies, and that the spoke route table contains only destinations behind the hubs, not other spoke routes.

The correct answer is B . The DoS profile in the exhibit is a Classified Profile using Source IP Only as the classification key. For TCP flood protection, the profile is enabled and shows an Alarm Rate of 5000 packets per second , an Activate Rate of 7000 packets per second , a Maximum Rate of 100000 packets per second , a Drop Period of 300 seconds , and an action of Random . This means the first threshold, 5000 pps, is used to trigger alarm behavior, while the second threshold, 7000 pps, activates the configured mitigation action. Since the selected action is Random , packets are randomly dropped when the TCP rate reaches the activate threshold.

Versa documentation shows that DoS policies can match traffic using source, destination, service, application, schedule, IP version, DSCP, and other conditions, and that a DoS policy can set either an aggregate or classified DoS profile. It also documents that DoS policies support enforcement actions and logging through LEF profiles for DoS events. Therefore, 7000 pps does not merely generate an alarm, and it does not mean complete dropping. Complete dropping is not selected in the exhibit.

The correct answer is A . The exhibit shows that the IPsec VPN is being configured with Tunnel Routing Instance: XIAN-Control-VR . However, the question states that the tunnel is toward a non-SD-WAN site over the INET-Transport-VR . For a site-to-site IPsec tunnel, the tunnel routing instance must match the routing instance used to reach the peer public IP address. In this case, the remote non-SD-WAN peer is 10.1.1.1 , and the intended underlay transport is INET-Transport-VR , not the Control VR.

Versa troubleshooting documentation explains that routing instances are used to define where traffic is sourced and forwarded. For example, configuration examples select routing instances when enabling services or initiating tests, and traffic must use the correct WAN or transport routing instance to reach the remote endpoint. Versa branch troubleshooting also emphasizes that after transport connectivity is available, the branch establishes IKE-based IPsec connectivity; if that connectivity fails, the IPsec-related interface remains down.

Changing the routing instance to global would not be correct because the intended path is specifically INET-Transport-VR. A higher precedence value is not required to establish the tunnel. The policy selector shown already defines local-to-remote interesting traffic, and the key failure is the incorrect tunnel routing instance.

The correct answers are A and C . The route table shown in the Versa SD-WAN design documentation includes a default route, 0.0.0.0/0 , with next hop 169.254.0.2 and exit interface tvi-0/603.0 . A default route is used when no more specific route exists in the routing table, so any unknown IPv4 unicast destination will follow that active default route through the tvi-0/603 interface. This directly supports option C.

The same design context describes local or central internet breakout, where Director workflows create TVI-based connectivity for breakout or gateway-style forwarding. In Versa SD-WAN, TVI interfaces are commonly used as internal virtual tunnel interfaces between routing instances, such as between a tenant LAN VR and a transport or breakout VR. The documentation also describes virtual TVI interface pairs being created by Director workflows between VRs for gateway routing use cases. Therefore, option A is also correct: tvi-0/603 is paired with another interface in another VR to support the default-route forwarding path.

The IP address is not shown as misconfigured; 169.254.x.x addressing is commonly used for point-to-point internal TVI links. The route is also not a blackhole route, because it has an active next hop and an exit interface.

The correct answer is A . Versa SD-WAN data-path troubleshooting documentation shows the VSM local-tunnel-site output and includes a legend in which BN means Behind NAT . In the WAN local link details, the output also displays a field named WAN lcl link behind NAT , with values such as 1 or 0, and link flags including [ BN CT PT SLA-P ] when the WAN link is behind NAT.

This information is important because NAT status affects how SD-WAN tunnel endpoints are discovered and how public and private transport addresses are represented. The same output includes both public and private WAN link addresses, making it useful for troubleshooting sites behind NAT, stale tunnel endpoints, or incorrect public-address learning.

WAN lcl vrf-id identifies the local transport routing instance ID, not NAT status. Tenant ID identifies the tenant context. Neighbour site type identifies whether the remote endpoint is a Controller, hub, or SD-WAN site. None of those fields specifically confirms whether the local WAN transport is behind NAT.

The correct answers are C and D . Versa templates are designed to reuse common configuration while still allowing per-device customization. Template variables allow the same template to be deployed to multiple appliances while using device-specific values such as addresses, VLAN IDs, DHCP information, or other bind-data values. Versa documentation for deploying templates describes assigning values to variables contained in a main template that are specific to the device. This makes option C correct.

Option D is also correct because Versa workflows are used to create templates for VOS device configuration. Versa documentation states that workflows are used to create templates to configure VOS devices, and also to create templates for application steering, spoke groups, and service chains.

Option A is not correct in the normal Versa Director onboarding model because a group of devices is associated with one staging template and one post-staging template, rather than multiple device templates being stacked per appliance. Option B is also incorrect because service templates are optional reusable service-specific fragments. Versa documentation states that service templates can be used by multiple device templates and device groups, but it does not require every appliance to have one.