The correct answer is C . In Versa Secure SD-WAN, Direct Internet Access, or DIA, provides local internet breakout from the branch rather than backhauling internet-bound traffic through a hub. Versa design documentation explains that the DIA architecture creates an internal connection between the tenant VRF and the WAN transport VR and uses CGNAT to translate internet-bound LAN traffic to the public IP address associated with the WAN transport interface. It specifically states that the main DIA components include the CGNAT function for translating internet-bound traffic and that DIA is configured using Director Workflows when configuring tunnels.

When the workflow template is used and the DIA option is selected for the internet breakout tunnel, Director automatically builds the required DIA infrastructure, including the NAPT/CGNAT configuration associated with the internet-facing transport network. This is why manual creation of the CGNAT pool and rule is not required in the workflow-based method. Option A describes a manual configuration approach, not the workflow-generated behavior. Option B is incorrect because NAT must be associated with the internet-facing breakout path, not simply the LAN interface. Option D is incorrect because DIA normally requires address translation for LAN users accessing the public internet.

The correct answer is B . The exhibit shows the OSPF neighbor in the exst state, which means Exchange Start . Versa documentation lists the OSPF neighbor state codes and identifies exst as “exchange start,” followed by exchange, loading, and full. In normal OSPF adjacency formation, neighbors progress through initialization and two-way communication before they negotiate database exchange. If the neighbor becomes stuck in ExStart or Exchange, a common and highly probable cause is an MTU mismatch between the two OSPF peers. During database description packet negotiation, the peers must agree on parameters that allow LSDB exchange; an MTU mismatch can prevent the adjacency from advancing to Full.

Option A is less likely because an area mismatch usually prevents the neighbor relationship from forming correctly rather than leaving it stuck in ExStart. Option C is also incorrect because the neighbor has already progressed beyond early states, which indicates that bidirectional communication has occurred. Option D is not the best answer because dropping OSPF multicast 224.0.0.5 would typically prevent discovery or keep the adjacency in an earlier state, not specifically in ExStart. Therefore, the probable cause is an interface MTU mismatch.

The correct answer is A . The exhibit shows that the IPsec VPN is being configured with Tunnel Routing Instance: XIAN-Control-VR . However, the question states that the tunnel is toward a non-SD-WAN site over the INET-Transport-VR . For a site-to-site IPsec tunnel, the tunnel routing instance must match the routing instance used to reach the peer public IP address. In this case, the remote non-SD-WAN peer is 10.1.1.1 , and the intended underlay transport is INET-Transport-VR , not the Control VR.

Versa troubleshooting documentation explains that routing instances are used to define where traffic is sourced and forwarded. For example, configuration examples select routing instances when enabling services or initiating tests, and traffic must use the correct WAN or transport routing instance to reach the remote endpoint. Versa branch troubleshooting also emphasizes that after transport connectivity is available, the branch establishes IKE-based IPsec connectivity; if that connectivity fails, the IPsec-related interface remains down.

Changing the routing instance to global would not be correct because the intended path is specifically INET-Transport-VR. A higher precedence value is not required to establish the tunnel. The policy selector shown already defines local-to-remote interesting traffic, and the key failure is the incorrect tunnel routing instance.

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.

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 A . In Versa SD-WAN traffic steering, forwarding profiles define how traffic is mapped to WAN circuits, how next hops are selected, and how traffic behaves when SLA conditions are violated. If the requirement is to stop traffic when no SLA-compliant path is available, the relevant behavior is the SLA Violation Action . Setting this option to Drop prevents the VOS device from forwarding the matching traffic over a circuit that does not satisfy the policy’s SLA requirements.

This is the opposite of using Forward , which allows traffic to continue even when the available next hops violate the SLA. Forward may be appropriate for best-effort applications where degraded delivery is better than no delivery, but it is not appropriate for strict business-critical applications that must not use a degraded path.

Nexthop Failure Action controls how the system behaves when a next hop fails, such as waiting for recovery or re-evaluating. Header compression affects packet overhead, and the recompute timer controls periodic recalculation timing. None of those settings directly enforce “drop when SLA is not met.”

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 A . Versa SD-WAN data-path troubleshooting documentation shows the VSM local-tunnel-site output and includes a legend in which BN means Behind NAT . In the WAN local link details, the output also displays a field named WAN lcl link behind NAT , with values such as 1 or 0, and link flags including [ BN CT PT SLA-P ] when the WAN link is behind NAT.

This information is important because NAT status affects how SD-WAN tunnel endpoints are discovered and how public and private transport addresses are represented. The same output includes both public and private WAN link addresses, making it useful for troubleshooting sites behind NAT, stale tunnel endpoints, or incorrect public-address learning.

WAN lcl vrf-id identifies the local transport routing instance ID, not NAT status. Tenant ID identifies the tenant context. Neighbour site type identifies whether the remote endpoint is a Controller, hub, or SD-WAN site. None of those fields specifically confirms whether the local WAN transport is behind NAT.