Free VNX100 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

The Versa Operating System (VOS™) is the specialized, carrier-grade network operating system that provides the core routing, security, and SD-WAN functionalities of the Versa solution. It is designed to run on the control and data plane components of the architecture. Specifically, VOS powers the Versa Controller for control plane management, the Versa SD-WAN CPE (branch appliances), and the Versa SD-WAN Gateways (data center/cloud appliances). These three components form the network fabric that forwards and secures traffic based on centrally managed policies. In contrast, Versa Director and Versa Analytics are management and visibility platforms that run as applications on general-purpose operating systems (e.g., Linux) within virtual machines.

A. Versa Director: This is the management and orchestration platform. It runs as an application on a standard operating system, not the VOS network OS.

C. Versa Analytics: This is the data collection and visibility platform. It runs as an application on a standard operating system, not the VOS network OS.

1. Versa Networks

"Versa Operating System™ (VOS™) Data Sheet": This document states

"Versa Operating System (VOS) is the heart of Versa SASE

powering Versa Secure SD-WAN and Versa SASE Gateways with a broad set of networking and security functions." This confirms VOS runs on the data plane elements (CPE and Gateways). (Reference: Page 1

"Introduction" section).

2. Versa Networks

"Versa Secure SD-WAN Solution Overview": Architectural diagrams in this overview consistently depict the Versa Controller as the "SD-WAN Control Plane" and the branch/hub sites (CPEs/Gateways) as the "Data Plane

" both of which are powered by VOS. The Versa Director and Versa Analytics are shown separately as the "Management

Orchestration

and Visibility" planes

which are distinct software platforms. (Reference: Architectural diagrams

typically found on pages 2-3).

3. Versa Networks

"SASE for Dummies

Versa Special Edition" by L. Chappell: Chapter 3

"Looking at the Versa SASE Architecture

" describes the components. It clarifies that VOS is the software that "runs on the Versa Cloud Gateways and on the CPE at the branch edge." It also describes the Versa Controller as the "brains of the control plane

" which is also a VOS-based instance responsible for routing and policy distribution. The roles of Director and Analytics are defined as management and visibility

separate from the VOS-powered network fabric. (Reference: Chapter 3

"The Versa SASE components" section).

Versa Analytics is the component specifically designed for collecting, storing, and analyzing historical data related to network performance, application usage, and security events. Since the performance issue occurred in the past ("yesterday") and is no longer active, the administrator would use the historical data and trend analysis capabilities within the Versa Analytics dashboards to investigate and identify the root cause of the temporary degradation. It provides the necessary tools for retrospective analysis of logs, flows, and performance metrics.

A. Versa Director troubleshooting tools: These tools, such as ping, traceroute, and packet capture, are used for diagnosing active, real-time network problems, not for investigating issues that have already resolved.

C. Versa Controller logs: Versa Controller logs primarily contain information about control plane activities, such as routing protocol updates and policy distribution, not end-user data plane performance metrics.

D. Versa Director monitoring dashboards: While Versa Director provides real-time monitoring of device and link status, it is not designed for the deep, long-term historical data analysis and correlation that Versa Analytics offers.

1. Versa Networks

"Versa Analytics Datasheet": "Versa Analytics is a big data solution that provides real-time and historical insight

visibility

and security into the network... It provides analysis of historical data and trends for network and security events

enabling network and security administrators to perform historical forensics." (Page 1

"Product Overview" section). This directly supports using Analytics for past issues.

2. Versa Networks

"Versa Director Datasheet": "Versa Director provides the essential management

monitoring and orchestration capabilities... It provides a single-pane-of-glass for configuration

real-time monitoring

and reporting." (Page 1

"Product Overview" section). This highlights its focus on real-time monitoring and management

contrasting with the historical analysis role of Analytics.

3. Versa Networks

"Versa Operating System (VOS™) Datasheet": This document outlines the roles of the different components. It describes the Controller's function as managing "control plane and data plane programming" and the Director's role in "management and orchestration

" while implicitly positioning Analytics as the tool for data collection and analysis derived from VOS. (Page 2

"Versa Secure SD-WAN Components" section).

Versa Director is the centralized management and orchestration platform within the Versa Secure SD-WAN architecture. Its primary function is to provide a single-pane-of-glass for configuration, zero-touch provisioning (ZTP), monitoring, and lifecycle management of the entire SD-WAN fabric. It acts as the orchestrator, pushing policies and configurations to Versa Controllers and Versa Operating System (VOS) appliances. This centralized control simplifies network operations and ensures consistent policy enforcement across the distributed network.

A. Versa Analytics is the dedicated component for log collection, storage, analysis, and forwarding, not Versa Director.

C. Versa Controllers handle the control plane functions, including acting as BGP route reflectors for SD-WAN overlay routing.

D. VPN concentration is a data plane function handled by Versa Operating System (VOS) instances on hub or gateway devices.

1. Versa Networks

"Versa Director Data Sheet": "Versa Director is the single-pane-of-glass for centralized orchestration and management of Versa Secure SD-WAN." (Page 1

"Product Overview" section). This document explicitly defines the Director's role as the orchestrator.

2. Versa Networks

"Versa Secure SD-WAN Solution Brief": This document outlines the architecture

stating

"Versa Controller...establishes and maintains all the secure control plane connections with all the CPEs...Versa Analytics...is the real-time big data solution for visibility

reporting

and security forensics." (Page 4

"Versa Secure SD-WAN Components" section). This reference clarifies the distinct roles of the Controller (control plane/BGP) and Analytics (logs)

differentiating them from the Director.

3. Versa Networks

"Configuring System Basics

Release 21.2.2": "Versa Director is the orchestration point for the entire Versa Networks system." (Page 13

"Versa Director" section). This official configuration guide reinforces that orchestration is the Director's core purpose.

The Versa Operating System (VOS™), also known as FlexVNF, is a comprehensive software platform that integrates a wide range of networking and security functions. Among its extensive feature set, VOS explicitly includes Carrier-Grade NAT (CGNAT) for large-scale address translation, full support for IP Multicast routing protocols (such as PIM-SM, PIM-SSM, and IGMP), and the ability to function as a Network Time Protocol (NTP) server to provide time synchronization for other devices within the network. These features are integral to its routing, security, and network services capabilities.

A. HTTP Proxy: VOS provides Secure Web Gateway (SWG) functionality which transparently proxies web traffic for security inspection, but it is not offered as a traditional, standalone HTTP Proxy service.

B. CDN: A Content Delivery Network (CDN) is a geographically distributed network of servers. This is a type of service, not an integrated feature of a single network operating system like VOS.

1. Versa Networks

"Versa VOS™ (FlexVNF) Software Datasheet":

Page 2

"Network Services" section: Lists "NAT (NAT44

NAT64

NPTv6

CGNAT)" as a supported feature. This validates option C.

Page 2

"Advanced Routing" section: Lists "Multicast (PIM-SM

PIM-SSM

IGMP v1/v2/v3)" as a supported feature. This validates option D.

2. Versa Networks

"VOS 21.2.2 Configuration and Administration Guide":

Section: "Configuring NTP": Details the command hierarchy set system services ntp server

A Device Template in the Versa Networks platform is a standardized, reusable configuration applied to multiple branch devices to ensure consistency. The template workflow involves defining the fundamental characteristics of the device's role, which includes assigning functions to its physical interfaces (e.g., WAN or LAN ports) and configuring core SD-WAN services and policies, such as how to handle Direct Internet Access (DIA) for local internet breakout. These settings are central to the template's purpose of standardizing branch deployments.

B. Device Group: A Device Group is a logical container to which a template is applied, but the group itself is not an attribute configured within the template.

C. serial number: A serial number is a unique identifier for a specific physical device. Templates are generic and reusable, so they cannot contain device-specific unique information like a serial number.

1. Versa Networks

"Versa Director Configuration Guide" (Version 21.2.2):

Section: Device Templates

Page 112: The guide details the process of creating a device template. It explicitly shows steps for "Configuring Interfaces

" where an administrator assigns roles like WAN or LAN to the physical ports of the selected device model. This directly supports option A.

Section: Configuring Services in a Template

Page 125: This section describes how to enable and configure services within the template. It specifically mentions "Direct Internet Access (DIA)" as a service that is configured here

including the creation of associated policies. This supports option D.

2. Versa Networks

"Zero Touch Provisioning Deployment Guide" (Version 21.2.2):

Section: Onboarding a Device

Page 28: This document outlines the device onboarding workflow. It states

"During onboarding

the device is identified by its serial number and assigned to a Device Group. A pre-configured Device Template is then applied to the device." This clearly separates the serial number (C) and Device Group (B) as elements of the onboarding and assignment process

distinct from the content of the template itself.

Versa Analytics provides a comprehensive reporting engine that allows administrators to gain insights into network and security events. Within the reporting views, users have the capability to create highly custom reports (E) by selecting specific widgets, filters, and time ranges. These reports can be scheduled for automatic, periodic generation (C) (e.g., daily, weekly, monthly). Furthermore, the scheduling feature includes an option to automatically distribute the generated reports to specified recipients via e-mail (B), ensuring stakeholders receive timely updates without manual intervention.

A. to export logs to an external reporting server: This is incorrect. Exporting raw logs to external systems like a SIEM is a log forwarding function configured at the system or collector level, not an action performed within a reporting view.

D. to create reports for license compliance: This is incorrect. License management and compliance status are typically monitored and managed within Versa Director, not generated as a standard report type from a Versa Analytics reporting view.

1. Versa Networks

"Versa Analytics 21.2.2 User Guide":

Section: Creating a Custom Report (supports E): This section details the process of building a new report from scratch by adding and configuring various widgets. It states

"You can create a custom report by selecting the required widgets and adding them to the report."

Section: Scheduling a Report (supports B and C): This section describes the functionality for automating report generation. It explicitly shows options for setting a schedule (e.g.

"Repeats: Daily

Weekly") and for distributing the output

stating

"In the Email Recipients field

enter the email addresses of the recipients." This confirms both periodic generation and email delivery.

The Versa Networks SD-WAN control plane is fundamentally built on Multi-Protocol BGP (MP-BGP). The Versa Controllers act as route reflectors, and the branch appliances (FlexVNFs/CSGs) establish internal BGP (iBGP) peerings with them. This MP-iBGP framework is used to discover and maintain the SD-WAN topology.

To transport SD-WAN-specific overlay information—such as Transport Locators (TLOCs), encryption keys, and site IDs—Versa utilizes a proprietary BGP address family. This allows the standard BGP protocol to carry the necessary custom information required to build the SD-WAN fabric, effectively using a "Private Address Family" for topology advertisement.

A. SD-WAN topology is discovered using eBGP.

The relationship between branch appliances and controllers is within a single autonomous system, mandating the use of internal BGP (iBGP), not external BGP (eBGP).

D. NETCONF advertises topology changes.

NETCONF is a management plane protocol used by Versa Director to push configuration to devices. It does not dynamically advertise topology changes; that is the role of the control plane protocol, MP-BGP.

1. Versa Networks

"Versa Operating System (VOS™) 21.2.2 SD-WAN and SASE Configuration Guide

" Chapter: BGP for SD-WAN

Section: "BGP for SD-WAN Overview." This section states

"The Versa solution uses Multi-Protocol BGP (MP-BGP) as the control plane protocol to exchange reachability information between the branch CPEs and the controllers... The peering between the CPEs and the controllers is an iBGP peering." This supports option B and refutes option A.

2. Versa Networks

"Versa Operating System (VOS™) 21.2.2 SD-WAN and SASE Configuration Guide

" Chapter: BGP for SD-WAN

Section: "SD-WAN Routes." This section details the use of a specific address family for SD-WAN routes: "Versa Networks uses a proprietary BGP address family to exchange SD-WAN-specific information... The address family is SD-WAN (AFI 16396

SAFI 254)." This directly supports option C.

3. Versa Networks

"Versa Director Configuration and Administration Guide 21.2.2

" Chapter: Versa Director Overview

Section: "Versa Director Architecture." This document clarifies the role of NETCONF: "Versa Director uses the NETCONF protocol to configure and manage the Versa devices (Controllers

Analytics

and FlexVNFs)." This confirms NETCONF is for management

refuting its role in advertising topology changes as suggested in option D.

The exhibit displays a classic hub-and-spoke network topology. The arrows explicitly illustrate the traffic path originating from Spoke 1, traveling to the central Hub, and then being forwarded to Spoke 2. In this configuration, the hub acts as a central transit and policy enforcement point for all communication between the spoke sites. This method of routing inter-branch traffic through a central location is defined as "spoke-to-spoke via hub." This design is often used to centralize security services and simplify routing logic, as spokes only need to maintain a connection to the hub.

A. spoke-to-spoke only: This option is too general and ambiguous; it fails to specify whether the communication path is direct or indirect (via a hub), which is the key detail shown in the exhibit.

C. spoke-to-spoke direct: This topology would show a direct communication link or tunnel between Spoke 1 and Spoke 2, bypassing the hub entirely. The exhibit clearly shows traffic traversing the hub.

D. spoke-hub-hub-spoke: This describes a more complex multi-hub or hierarchical topology where traffic passes through two hubs to get between spokes, which is not depicted in the single-hub diagram.

1. Versa Networks

Versa Operating System SD-WAN Configuration Guide

Release 21.2.2. In the "Topologies" chapter

the "Hub-and-Spoke Topology" section describes this model where "spokes connect to one or more hubs" and the hub manages the data plane traffic between spokes. This confirms the hub's role as an intermediary.

2. Versa Networks

Versa Secure SD-WAN For Dummies

2nd Versa Networks Special Edition. Chapter 3

"Exploring the Key Capabilities of Versa Secure SD-WAN

" under the "Flexible and full-featured topologies" section (page 29)

explains the hub-and-spoke model where all traffic from a spoke site is directed to the hub site

which then routes it to the final destination

including other spokes.

The Versa Controller is the central brain of the SD-WAN control plane. Its primary function is to act as a control plane node (B), establishing secure connectivity with all Versa Secure SD-WAN Edge devices and distributing routing information and policies using MP-BGP. Through this central role, it provides visibility into the real-time state of the network overlay and enforces centralized policies, thus providing visibility and control (D). The Controller can also be configured to operate as an on-premises staging server to facilitate the Zero Touch Provisioning (ZTP) process for new branch appliances (E).

A. It does CPE lifecycle management.

This is incorrect. CPE lifecycle management, including onboarding, configuration templating, and software upgrades, is a primary function of the Versa Director.

C. It is a data plane node.

This is incorrect. The Versa Controller is a dedicated control plane component. Data plane functions, such as packet forwarding, are performed by the Versa Secure SD-WAN Edge devices.

1. Versa Networks

"Versa Secure SD-WAN Solution Guide

Release 21.2.2"

For Answer B & D: In Section 2.3

"Versa Controller

" it states

"Versa Controller is the control plane of the Versa SD-WAN solution... It is responsible for collecting state information from the CPEs and distributing routing and policy information to the CPEs." This confirms its role as a control plane node that provides visibility (state information) and control (policy distribution).

For refuting A: In Section 2.1

"Versa Director

" it is described as the "single point for centralized management and orchestration" and is responsible for "provisioning and lifecycle management of the VOS instances."

For refuting C: The guide consistently distinguishes the Controller's control plane function from the data plane function of the "VOS (CPE)" described in Section 2.4.

2. Versa Networks

"Versa Secure SD-WAN Zero Touch Provisioning Deployment Guide

Release 21.2.2"

For Answer E: In Section 3.2

"On-Premises Staging Server

" the document states

"You can configure a Versa Controller as a staging server... The on-premises staging server provides the initial bootstrap configuration to the CPE device." This explicitly confirms the Controller can function as a staging server.

Versa Director is the centralized management, orchestration, and visibility platform for the Versa Secure SD-WAN fabric. It provides a graphical user interface (GUI) that allows network operators to monitor the entire network from a single pane of glass. To view live data for a specific CPE interface, an operator would navigate to the Monitor tab in Versa Director, select the appropriate appliance, and then view the real-time statistics for its interfaces, including traffic rates, packets, and errors.

A. using Versa Controller: The Versa Controller is a control-plane component responsible for routing and policy distribution; it is not the primary tool for live operational monitoring by a network operator.

C. using Versa Analytics: Versa Analytics is a platform for long-term storage, analysis, and reporting of historical data and logs, not for viewing real-time, live interface statistics.

D. using the Versa CPE GUI: While the local CPE GUI can show live data, it is not the standard or scalable method for a network operator managing multiple sites. Centralized monitoring is performed via Versa Director.

1. Versa Networks

"Versa Director Administrator’s Guide": The guide details the monitoring capabilities of Versa Director. In the "Monitoring the Network" chapter

the section on "Monitoring Appliances" explicitly describes the procedure to select a device and view live

real-time operational data for its interfaces through the Director GUI. This establishes Director as the designated tool for this task.

2. Versa Networks

"VOS™ (formerly FlexVNF) SD-WAN Configuration and Administration Guide": This document outlines the roles of the different Versa components. It specifies that Versa Director provides centralized management and visibility

while Versa Analytics provides historical data analysis. This distinction confirms that Director is for live monitoring and Analytics is for historical trends.

3. Versa Networks

"Versa Secure SD-WAN Platform" Official Datasheet: The datasheet describes Versa Director as the "single-pane-of-glass for management

monitoring

and orchestration

" reinforcing its role as the primary interface for network operators to perform tasks like live monitoring.

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').