4A0-D01 Sample Questions & Answers

To send logs to a remote server, the server's IP address and transport parameters (like UDP or TCP) must be defined as a destination.

A rule is needed to match the desired log messages (based on severity, application, etc.) and associate them with the action of sending them to the configured remote destination.

To check the specific status and configuration of a subinterface, you must specify its full name, which includes the physical port and the subinterface index (e.g., ethernet-1/1.100). This command will display detailed information for that logical interface, including its operational state, associated VLAN, IP address, and network instance, which is crucial for troubleshooting.

Even with multiple equal-cost paths available, ECMP relies on a hashing algorithm to distribute traffic. A typical default hash uses Layer 3/4 headers (source/destination IP, source/destination port). For a single, long-lived TCP session between two endpoints, these values are constant. Therefore, the hash calculation will always produce the same result, sending all packets for that specific flow down the same path. This is expected behavior known as per-flow load balancing. To see traffic use multiple paths, multiple independent flows with different header information are required.

The top command in the SR Linux CLI is a shortcut that immediately returns the user to the root of the current mode's hierarchy. If in configuration mode, it goes to /configure; if in operational mode, it goes to /. The .. command only moves up one level in the hierarchy, and exit all would exit the configuration mode entirely, not just go to the top.

A MAC-VRF defines a Layer 2 forwarding domain, essentially a virtual switch. Associating a subinterface (which is typically tied to a VLAN) with a MAC-VRF tells the system that any traffic received on that subinterface belongs to that specific L2 VPN segment. This is the logical binding between the physical/virtual port and the L2 service instance. A Layer 3 gateway (IRB interface) would be associated with an IP-VRF.

BGP's strength lies in its policy-based routing capabilities. It allows for granular control over route advertisement and selection using attributes like communities, AS-path, and local preference. In large, multi-tenant, or complex data centers, this control is essential for traffic engineering, route filtering, and creating logical traffic patterns, which is far more difficult to achieve with the metric-based path selection of IGPs.

The description leaf in the YANG model for an interface is located directly under the interface context itself. For example, to configure a description for ethernet-1/1, you would navigate to /configure interface ethernet-1/1 and then issue the command description "Link to Spine-1". It is a direct property of the interface.

A 'model-driven' architecture means that the single source of truth for all configuration data, operational state, and RPCs is a set of well-defined, structured data models, which in SR Linux's case is YANG. This allows for predictable, programmatic interaction with the system via APIs like gNMI and NETCONF, as the structure of the data is always known and validated against the model.

SR Linux allows a static route to be associated with a BFD session. This feature, often called BFD tracking, ensures the static route is only considered valid and installed in the RIB if the BFD session to the next-hop is up. If the BFD session goes down, indicating a reachability failure, the static route is automatically withdrawn, allowing for failover to an alternate path. This adds dynamic failure detection to an otherwise static configuration.

The Application Manager acts as the process manager, responsible for starting all other applications based on the system's configuration and ensuring they are running correctly.

A key role of the Application Manager is to act as a watchdog for other processes. It monitors their health and will automatically restart any application that crashes, enhancing system resiliency.