In SD-WAN policy rules, two parts used to steer traffic are Schedules and Applications. Schedules allow administrators to define when certain policy rules should be active, effectively determining the timing for when traffic steering decisions should be applied. Applications, on the other hand, enable traffic steering decisions based on the type of application traffic being detected. This allows for more granular control and optimization of traffic flows based on application requirements and characteristics​​.

The policy shown in the exhibit appears to match traffic flows based on multiple conditions involving the source zone and the application. Given the information in the screenshot:

The policy is configured with multiple zones as source zones: Intf-LAN1-Zone and Intf-WLAN-Zone .

An application is specified: SHAREPOINT .

The policy is likely to be applied to traffic originating from either of the specified zones and specifically related to the SharePoint application. This implies that both conditions related to the source zones are not mutually exclusive but rather a union; the same goes for the application condition.

Given this interpretation, the correct set of conditions that match the policy shown would be:

B. Traffic flows that meet any of the following two conditions:

Source Zone - Intf-LAN1 Zone

Source Zone - Intf-WLAN-Zone

In addition, the below condition must also match:

Application - SharePoint

This means that traffic will match the policy if it comes from either the Intf-LAN1-Zone or the Intf-WLAN-Zone and is SharePoint application traffic.

However, to be more precise in the context of Versa SD-WAN configurations, it's important to note that policies are usually applied when all conditions within a single rule are met. If the configuration in the screenshot intends to express that traffic is matched if it comes from either of the two zones and is for the SharePoint application, then the correct answer should reflect this logic. If the configuration system is set up to require all conditions in a rule to be met, then the answer could potentially be different. Since the user interface design can sometimes vary, it’s important to understand the specific logic of the system in question.

Versa Analytics and Versa Director support REST APIs, which allow integration with third-party applications and systems. The REST APIs provided by these components enable automation and programmability for various network management and analytics functions. Versa Controller and Versa CPE are not referenced in the provided documents as supporting REST APIs directly, although they interact with Versa Director, which does. ​

Versa Director acts as an orchestrator within the Versa SD-WAN ecosystem, providing centralized configuration management and monitoring of controllers, branch sites, and hub sites. It does not function as a log forwarder, BGP route reflector, or VPN concentrator. As an orchestrator, it manages the lifecycle of Versa VOS instances, enabling zero-touch provisioning and other orchestration functionalities through a single pane of glass.

In a remote Versa branch, the Control Virtual Router (Control VR) is the routing instance that has the default route to reach the Versa head-end components. This Control VR is typically dedicated to carrying control plane traffic between branch nodes and the SD-WAN controller, facilitating secure communications essential for the management and operation of the SD-WAN network.

The Versa Operating System (VOSTM) is the software platform that provides routing, advanced SD-WAN, and SD-Security in a single software package. The VOS software is deployed in the branch, hub, cloud, and data center. Specifically, it is utilized within the Versa Controller, the Versa SD-WAN CPE, and the Versa SD-WAN Gateway, which are the components that use VOS to deliver their networking and security functions. Versa Director, on the other hand, is a centralized provisioning and management application that manages the VOS software instances but does not run the VOS itself. Versa Analytics is an analytics engine that provides insights into network traffic and events and also does not run the VOS itself. ​

The SLA profile shown in the exhibit appears to be set with thresholds for various metrics such as jitter, packet loss, and latency. These thresholds determine the acceptable performance criteria for the network. The profile is configured with specific maximums for packet loss, both in the forward and reverse directions, and for latency. If any of these configured values are exceeded, the SLA profile is triggered, indicating a breach of the desired service level agreement parameters. Therefore, if the packet loss value exceeds the maximum set in the profile, it will trigger an event or alert, which can then be used for remediation or for activating pre-defined traffic steering rules to maintain application performance.

To apply a new URL filtering profile across all of the SD-WAN CPEs in response to a security event, you would use the Next Generation Firewall (NGFW) Template. This template is specifically designed to handle security functions, including application control, intrusion prevention, and URL filtering. By using the NGFW Template, you can enforce URL filtering policies that block or allow traffic based on URLs and categories, which is integral to controlling access to websites and ensuring network security​​.