The Versa Networks solution exposes northbound REST APIs primarily through its management and analytics platforms. Versa Director, as the central management, orchestration, and provisioning component, provides a comprehensive REST API for integration with third-party systems like OSS/BSS for automation. Versa Analytics, the platform for data collection, log storage, and reporting, also offers a REST API. This allows external applications and tools to programmatically query the vast amount of performance, security, and historical data collected from the network for custom dashboards, reporting, and further analysis.

A. Versa Controller: This component manages control plane connections and routing information with the CPEs; it does not serve as a primary northbound API endpoint for orchestration.

C. Versa CPE: The CPE (FlexVNF) is the branch device. It is managed centrally by Versa Director and does not expose a REST API for network-wide orchestration.

1. Versa Networks

Versa Director REST APIs Guide

Release 21.2.2

Document Version 1.0

Page 10

Section "About Versa Director REST APIs". This document states

"Versa Director provides a set of RESTful APIs for northbound integration with Operation Support Systems (OSS) and Business Support Systems (BSS)."

2. Versa Networks

Versa Analytics REST API Guide

Release 21.2.2

Document Version 1.0

Page 9

Section "About Versa Analytics API". This guide details the API for the Analytics platform

stating

"The Versa Analytics platform provides a RESTful API that you can use to query the data that is stored in the Versa Analytics platform."

3. Versa Networks

Versa Secure SD-WAN Configuration and Administration Guide

Release 21.2.2

Document Version 1.0

Page 31

Section "Versa Solution Components". This guide describes the Versa Controller's role in establishing control channels with CPEs and the Director's role as the "single pane of glass for configuration

" reinforcing that the Director is the management interface

not the Controller or CPE.

The Versa Secure SD-WAN architecture is designed for deployment flexibility. Versa Analytics, the platform for visibility, reporting, and security analysis, can be deployed as a virtual appliance on-premises in an enterprise data center, in a service provider Point of Presence (POP), or in the cloud. This allows organizations to maintain data locality and control. Similarly, the Versa Controller, which manages the control plane, is a software component deployed as a virtual machine (VM) on commercial off-the-shelf (COTS) hardware. This VM can be hosted in an on-premises data center, a private cloud, or a public cloud environment, providing versatile deployment options to fit various network architectures.

A. Versa Controller supports multiple deployment models, including on-premises and private/public cloud, not exclusively cloud-based installations.

C. Versa Analytics is not limited to a cloud-based installation; it fully supports on-premises deployment in an enterprise data center.

1. Versa Networks

"Versa Secure SD-WAN Configuration and Administration Guide

Release 22.1"

Page 15

Section: Versa Analytics: "Versa Analytics is a virtual appliance that provides real-time and historical data analytics... It can be deployed in the service provider POP

in the enterprise data center

or in the cloud." (Supports Answer B

refutes C).

Page 14

Section: Versa Controller: "The Versa Controller is a virtual machine that serves as the SDN controller in the Versa Secure SD-WAN solution." (Supports Answer D

refutes A).

2. Versa Networks

"Versa Networks Head-End Components Data Sheet" (Document ID: DS-HEC-R21-1)

Page 1

Section: Overview: "Versa head-end components can be deployed on-premises in an enterprise data center or service provider POP

in a public or private cloud

or hosted and managed by Versa." (This statement supports both correct answers B and D

and refutes incorrect answers A and C).

The Versa Networks Quality of Service (QoS) framework on its CPEs is fundamentally built upon three core functions. First, Classification identifies and categorizes traffic based on various criteria like application, IP address, or DSCP markings. Second, Ingress Policing is applied to rate-limit traffic entering an interface, ensuring it conforms to a specified bandwidth profile by dropping excess packets. Third, Hierarchical Queuing, a key feature of Versa's Hierarchical QoS (H-QoS), manages network congestion at egress by scheduling packets through a multi-level queue structure. This provides granular control over bandwidth allocation and prioritization for different traffic classes, ensuring service level agreements (SLAs) are met.

A. admission control: This is a more specific mechanism, like Call Admission Control (CAC) for VoIP, not a foundational QoS function in the general Versa framework.

C. egress policing: Versa's architecture predominantly uses egress shaping and hierarchical scheduling to manage outbound traffic, while policing is the primary mechanism for rate-limiting at ingress.

1. Versa Networks VOS™ Quality of Service (QoS) Configuration Guide (Release 22.1):

Section: QoS Overview

Page 7: This section outlines the basic QoS workflow

stating

"The basic QoS process is to classify incoming packets and then apply a QoS policy to them... The actions include policing the traffic... and queuing the traffic for transmission." This confirms Classification

Policing

and Queuing as core components.

Section: Hierarchical QoS

Page 10: This section details the H-QoS model

explaining

"Versa VOS supports hierarchical QoS (H-QoS)

which allows you to apply queuing and shaping at multiple levels of a hierarchy." This directly supports Hierarchical Queuing (B).

Section: Configuring Policers

Page 45: This chapter describes the function and configuration of policers

specifying their use for rate-limiting. The examples and context consistently apply policers to input/ingress traffic

supporting Ingress Policing (E).

Section: Configuring Classifiers

Page 29: This chapter details the process of identifying traffic flows based on various fields

which is the definition of Classification (D).

Versa Secure SD-WAN is architected with a carrier-grade, multi-tenant software platform, Versa Operating System (VOS™), which inherently supports segmenting the network for different departments or customers. This is managed with granular Role-Based Access Control (RBAC) to define specific user permissions.

The entire solution is managed, provisioned, and monitored through Versa Director, which provides a "single-pane-of-glass" for centralized control over the entire network fabric. This platform is tightly integrated with Versa Analytics, which offers real-time and historical data, providing deep visibility and insights into network performance and security directly within the management interface.

A. An open programming language compiler is a software development tool, not a native feature of the Versa SD-WAN networking and security platform.

C. "On-demand resource pooling" is a term that primarily describes Infrastructure-as-a-Service (IaaS) cloud computing models, not a core feature of the Versa SD-WAN solution itself.

1. Versa Networks

"Versa Director Data Sheet":

Page 1

"Key Features" section: States

"True Multi-Tenancy: Versa Director is a carrier-grade multi-tenant platform that provides complete separation of management

control

and data between tenants."

Page 1

"Key Features" section: Lists "Role-Based Administration" as a key feature

which is synonymous with RBAC.

Page 1

Overview: Describes Versa Director as providing "single-pane-of-glass for provisioning

management

and monitoring of the entire Versa Secure SD-WAN and SASE fabric."

2. Versa Networks

"Versa Analytics Data Sheet":

Page 1

Overview: Explains that Versa Analytics is a "real-time analytics engine that provides visibility and control for Versa Secure SD-WAN and Versa SASE." It highlights the integration for a single management view.

3. Versa Networks

"Versa Operating System (VOS™) Data Sheet":

Page 1

"Key Features" section: Lists "Multi-Tenancy" as a foundational feature

stating VOS "provides complete data

control

and management plane separation for multiple tenants on the same physical hardware."

When configuring Direct Internet Access (DIA) using the automated workflow in Versa Director, the system creates a dedicated VRF for internet traffic (Internet VR). To enable communication between this new VRF and the existing LAN VRF, the workflow automatically provisions Tunnel Virtual Interfaces (tvi) in each VRF. An external BGP (eBGP) session is then established over these tvi interfaces. This eBGP peering is used to advertise a default route (0.0.0.0/0) from the Internet VRF to the LAN VRF, thereby directing internet-bound traffic from the LAN out the local internet circuit.

A. static routing: While static routes can be configured manually for inter-VRF routing, the automated DIA workflow defaults to the more dynamic and scalable BGP protocol.

B. OSPF: OSPF is an Interior Gateway Protocol (IGP) typically used for routing within a single VRF or routing domain, not as the default for route exchange between separate VRFs in this context.

D. VRRP: The Virtual Router Redundancy Protocol (VRRP) is a first-hop redundancy protocol used to provide a virtual, highly available gateway IP address; it is not a routing protocol.

1. Versa Networks

"Versa Secure SD-WAN Configuration Guide": In the section detailing Direct Internet Access (DIA) configuration via workflows

the guide specifies the automated creation of an Internet VRF and the establishment of an eBGP session. It states

"The workflow automatically configures eBGP peering between the service VRF and the newly created Internet VRF over the tvi interfaces to exchange routes." (Typically found in chapters related to 'Workflows' or 'Routing Configuration').

2. Versa Networks

"VOS™ BGP Configuration Guide": This document explains the use of BGP for advanced routing scenarios

including inter-VRF route leaking. The principles described for connecting different routing instances (VRFs) on the same node align with the DIA workflow's use of eBGP over a logical interface like a tvi. (Refer to sections on 'VRF Route Leaking' or 'Inter-AS BGP Peering').