The correct answers are A and B . In the exhibit, the LAN interface shows a fixed VLAN ID value of 100 .
Because this value is directly configured in the template rather than represented as a per-device variable, every branch that uses this template will receive the same LAN VLAN ID. This supports option A. Versa configuration examples show that VLAN-tagged interfaces are created by defining logical units with a vlan- id, and organizations then use those tagged interfaces for traffic identification and routing services.
For the MPLS WAN network , the VLAN ID field is shown as a variable or bind-data style value rather than a fixed number. This allows each branch device to receive a different MPLS VLAN ID during onboarding, depending on the branch-specific values supplied in the workflow or device bind data. Therefore, branches can have separate VLAN IDs on the MPLS WAN transport, which supports option B. Versa SD-WAN troubleshooting output also shows WAN interfaces as logical VNI subinterfaces, such as vni-0/1.0 and vni-0/2.
0, mapped to SD-WAN transport networks like INET and MPLS.
Option C is incorrect because an INET interface can be untagged, commonly represented with VLAN ID 0. Option D is incorrect because the MPLS VLAN field is intentionally parameterized, not incorrectly configured.

The correct answer is A . Versa CGNAT troubleshooting documentation includes per-pool and resource counters that show allocation behavior and failures. The counters include values such as bindings allocated, bindings freed, allocation failures, out-of-address errors, and out-of-ports errors. It also shows that CGNAT source-port resources are divided and distributed to worker threads by Versa RFD/RFM, and that allocated source-port ranges can be viewed using show rfm table src-port allocated.
If out-of-ports errors increase while out-of-address errors remain zero, the pool still has usable translated IP addresses, but the available port resource for NAT bindings is exhausted. This commonly occurs when too many concurrent sessions share a limited public IP or source-port range. The corrective action would be to expand the NAT resource, add more public translated IPs, adjust port allocation, or reduce excessive session usage.
A missing NAT IP pool would more likely produce out-of-address problems. A wrong zone match might prevent translation entirely, and OSPF in the LAN VR is unrelated to CGNAT port-resource exhaustion.

The correct answer is C . In Versa Secure SD-WAN, licensing and device management are centralized through Versa Director , not directly through the Controller. During zero-touch provisioning and staging, the branch device is brought under centralized management, and Director pushes the required staging and operational configuration. Versa staging documentation explains that during Stage 2 and Stage 3, Versa Director pushes configuration to the branch device, and after Stage 3 the branch becomes fully operational as part of the customer SD-WAN network.
Versa monitoring documentation also shows that the Director node provides license visibility, specifically stating that the Director monitoring view includes a License pane that displays information about the licenses installed on the VOS devices managed by the Director node. This confirms that license administration is handled from Director, not from the Controller. The Controller is responsible for SD-WAN control-plane functions and tunnel connectivity, but it is not the primary system for managing customer license subscriptions.
Option A is incomplete because the practical operational model is not simply receiving individual soft licenses. Option B incorrectly implies licenses are preloaded on physical CPEs as the key licensing method. Option D is incorrect because ZTP management and license subscription handling are not performed by the Controller.

The correct answer is A . During Versa SD-WAN onboarding, the branch uses the staging server only in the early part of the process. Versa documentation states that in Stage 1 , the branch starts an IKE session with the staging server, receives an IP address, and is informed of the Versa Director IP address. In Stage 2 , Versa Director pushes the stage-two configuration to the branch through the staging server. In this stage-two configuration, the Controller IP address is given as the remote IP address in the IPsec profile , and the branch is rebooted. After reboot, the branch should establish the IKE session with the Controller.
If the branch keeps trying to connect to the staging server after the stage-two reboot, the most likely issue is that the stage-two IPsec profile still points to the staging server or does not contain the correct Controller remote IP. Analytics, DHCP, and URL filtering settings do not determine whether the branch moves from staging-server connectivity to Controller IKE connectivity.

The correct answer is LOCAL_PREF . In BGP, the Local Preference attribute is used inside an autonomous system to influence which exit path is preferred for outbound traffic. In this scenario, the Versa Secure SD- WAN CPE receives routes from two upstream service providers, SP1 and SP2. To prefer routes learned from AS 64515 over routes learned from AS 64519, you would apply a BGP import or route policy that assigns a higher local preference to routes received from SP1. Versa SD-WAN design guidance shows this exact routing concept: an import policy can manipulate the Local-Pref attribute to prefer one advertised route path over another. The Versa output examples also display "Local Preference" as a BGP route attribute used in route selection.
MULTI_EXIT_DISC, or MED, is generally used to influence how a neighboring AS enters your AS, not how your CPE prefers routes learned from different upstreams. ORIGIN is part of BGP best-path selection but is not normally the administrative tool used to prefer one provider. NEXT_HOP identifies the next-hop address and does not directly define route preference.