VNX301 Exam Preparation Material | Versa Certified Administrator - SD-WAN Specialist

Explanation:
The correct answers are A, B, and E. Versa Director supports multiple notification and event-publishing mechanisms. For email-style system and alarm notifications, Versa Director supports SMTP configuration. The Director documentation lists Configure SMTP Notifications and explains that email templates require SMTP notifications to send test emails or operational messages.
Versa Director also supports webhook notifications. The Director GUI overview states that Notification Configuration includes webhook-based notifications for alarms, and the Director documentation includes a dedicated workflow for configuring webhook notifications for alarms.
Kafka is also a supported event-notification method. Versa’s Kafka Notifications documentation states that Versa Director can publish event notifications to an Apache Kafka server when events occur on a Director node or a VOS device. It also lists notification topics for device events, Director events, Director task notifications, and object-change event notifications.
MMS is not a Versa Director system event notification method. SMS can be configured for text messaging in some notification contexts, but for the three methods listed for system event notifications in this answer set, the verified options are SMTP, Webhook, and Kafka.

Explanation:
In the exhibit, the Add Associate Interface/Network window has Interface selected, and the interface name is set to vni-0/0. The DSCP rewrite option is not available because rewrite behavior is intended to be applied at the network association level for the WAN network, not directly while associating only the physical/logical interface. For WAN-facing CoS, the scheduler and shaping parameters can be attached to an interface, but DSCP rewrite policies are applied to remark traffic as it exits through a network context.
Versa SD-WAN design documentation explains that QoS rewrite rules rewrite packet QoS attributes as packets leave the VOS device, and that rewrite rules can modify IEEE 802.1p bits, IPv4 TOS/DSCP bits, and IPv6 traffic class bits. It also explains that a rewrite policy is commonly applied on a WAN network to remark traffic based on the forwarding class and loss priority assigned by QoS or App QoS policies. In the design example, Versa explicitly describes applying a QoS propagation or rewrite policy on the MPLS WAN network to remark traffic to a DSCP value. Therefore, the issue is the association type: it is set to Interface, not Network.

Explanation:
The correct answer is A. Versa link-bandwidth troubleshooting documentation explains that a VOS device can be configured as a Versa speed-test client, a Versa speed-test server, or both simultaneously. After the server is configured, the client starts the test by initiating a TCP-based connection toward the speed-test server. The server listens on port 5201. The documentation includes an explicit note that if the VOS device is behind a firewall, port 5201 must be open.
This is different from the SD-WAN overlay data path, which commonly uses UDP-based transport encapsulation, and different from internet speed-test traffic, which uses other ports depending on the specific test type. In this scenario, the question states that a Versa speed-test server was configured, so the relevant requirement is TCP 5201 reachability from the client to the server.
TCP 443 may be used for management or web access, UDP 4790 is associated with SD-WAN transport encapsulation, and UDP 53 is DNS. None of those replace TCP 5201 for Versa speed-test server operation.

Explanation:
The correct answer is A. Versa CGNAT troubleshooting documentation provides commands to inspect CGNAT state inside the vsmd daemon. To view summary information about configured tenants, the document instructs administrators to issue show cgnat tenants. The sample output shows each tenant ID and counters such as the number of configured rules, pools, DS-Lite service chains, 6RD service chains, static NAT entries, subscribers, endpoint-independent mapping entries, endpoint-independent filtering entries, and softwires.
This command is especially useful when CGNAT configuration appears correct in Director but translation is not happening, because it confirms whether the runtime dataplane process actually has the tenant CGNAT state.
show interfaces brief shows interface status and IP addressing. show alarms shows event notifications, and show system uptime shows how long the system has been running. These are useful operational commands but do not show CGNAT tenant programming inside vsmd.

Explanation:
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.