Versa Networks Updated VNX301 Exam Questions and Answers by laurie

The correct answer is B . In Versa SD-WAN onboarding, the branch progresses through three staging phases. In Stage 1 , the branch uses its factory-default configuration to start an IKE session with the staging server. After the IKE session comes up, the staging server assigns an IP address to the branch and notifies the branch of the Versa Director IP address. Versa Director is also notified that the branch has come up.

In Stage 2 , Versa Director pushes the stage-two configuration to the branch through the staging server. This stage changes the IPsec profile so that the Controller IP address becomes the remote IP. The branch reboots and then attempts to establish the IKE session with the Controller. If the device successfully completed Stage 1 but never forms the Controller IKE session, the failure point is Stage 2.

Stage 3 is later, when the device receives stage-three configuration, becomes operational, and creates Controller IPsec plus branch-to-branch VXLAN/ESP sessions. Therefore, the described issue is a Stage 2 staging failure.

The correct answers are A, B, and D . For large-scale Versa Secure SD-WAN onboarding, common configuration is reusable through templates and grouping. A device template , also known as a post-staging template, provides the common base configuration that is applied to multiple VOS branch appliances. Versa documentation repeatedly shows configuration tasks being performed under Templates > Device Templates , where an organization is selected and the post-staging template is opened in Appliance view for common configuration.

A device group is also shared by multiple appliances because it groups devices that should receive the same template associations and common service behavior. This is the proper way to profile many branches with similar deployment requirements. Service templates are also shared objects. They are used to apply service-specific configurations, such as SD-WAN traffic steering, application steering, QoS, security, or other common services, across devices. Versa SD-WAN design documentation explains that application-steering templates automate business-intent policies and simplify management by combining application classification, forwarding-class mapping, and SD-WAN policy logic in a reusable template.

A workflow device is device-specific, and device bind data contains site-specific values such as interface addressing, gateways, VLANs, and other per-branch parameters. Therefore, those are not the shared configuration objects.

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 D . In the displayed post-staging template association order, the device template BMBF-TEMPLATE is applied before the QoS service template Ship-CoS-IT . Versa documentation explains that device templates, also called post-staging templates, provide the baseline configuration for devices, while service templates are service-specific configurations that can be applied to device configurations. It also states that service templates are associated with device groups and that, in a device group, the administrator can choose the order in which service templates are applied.

Because the QoS template is later in the shown association order, the final merged device configuration uses the Address object definition from the QoS template when the same object name exists in both templates. It does not automatically create two copies of the same Address object, because the object name is the key for the configuration element. It also should not fail merely because the same object name exists in a later template; the merge behavior resolves the effective configuration according to the template order. Therefore, the onboarded hub device receives the Server Address object version from Ship-CoS-IT, the QoS template.