F5 Updated F5CAB2 Exam Questions and Answers by johnny

Configuring networking objects in BIG-IP requires using the correctTMSH module pathandverb.

Module Path:Trunks are networking objects, so they reside under the /net module, not /sys.

Verb:Since the trunk already exists, the modify verb must be used to update its properties rather than create.

Syntax:The correct syntax to append physical interfaces to an existing trunk is tmsh modify /net trunk [name] interfaces add { [port list] }.

Data Plane Impact:Adding interfaces to a trunk (Link Aggregation) increases the total aggregate bandwidth available to the system and provides additional hardware redundancy.

When handling high-volume UDP traffic where the BIG-IP does not need to maintain any session history or relationship between packets, aStatelessvirtual server is the appropriate choice.

No Connection Tracking:A stateless virtual server does not create or maintain entries in the BIG-IP connection table. This means the system processes each packet as an individual event, without "considering previous connections" or packets from the same source.

High Performance:Because the system bypasses the overhead of state management, stateless virtual servers provide the highest possible throughput for UDP and ICMP traffic.

Use Cases:This is ideal for services like DNS (stateless queries) or some types of syslog traffic where each packet is independent and doesn't require the persistence or protocol inspection typically provided by a full-proxy.

Why other options are incorrect:

Forwarding:While a Forwarding (IP) virtual server can handle UDP, it still maintains a state entry in the connection table to ensure return traffic is handled correctly.

Standard:This is a full-proxy virtual server. It is inherently stateful and requires a connection table entry for every flow it manages.

Reject:This is a special virtual server type that simply drops incoming traffic and, in the case of TCP, sends a reset (RST) or, for UDP, sends an ICMP unreachable message. It is not a load balancing type.

When troubleshootingperformance and latency issueson BIG-IP, especially under peak load conditions, it is critical to identify whichVirtual Servers are consuming the most resources. This is a coredata plane analysis task.

BIG-IP provides multiple views of configuration and status, but only certain areas exposereal-time and historical traffic statisticsthat correlate directly with CPU usage and throughput.

Why Option C Is Correct:

Statistics > Module Statistics > Local Traffic > Virtual Serversprovides:

Real-time and cumulative statistics per Virtual Server

Metrics such as:

Bits in / Bits out

Packets in / Packets out

Current connections

Connection rate

Total requests

The ability toidentify high-traffic or high-connection Virtual Servers, which are the most likely contributors to elevated CPU utilization

These statistics allow the administrator toobjectively determine which Virtual Servers are the top consumers of system resourcesand therefore good candidates for migration to a dedicated BIG-IP device.

Why the Other Options Are Incorrect:

A. Local Traffic > Virtual Servers > Virtual Server List

Primarily aconfiguration view

Does not provide sufficient performance or utilization statistics to identify CPU-heavy Virtual Servers

B. System > Platform

Displayshardware-level informationsuch as CPU cores, memory, disk, and platform type

Does not break down utilization by Virtual Server

D. Local Traffic > Network Map

Provides alogical topology viewof Virtual Servers, pools, and pool members

Useful for understanding relationships, but not for identifying high-utilization Virtual Servers

Key Data Plane Concept Reinforced:

To diagnose performance problems and plan traffic redistribution, BIG-IP administrators must rely onModule and object-level statistics, not configuration screens. TheVirtual Server statistics viewis the authoritative location for identifyingtraffic hotspotsthat directly impact CPU and latency during peak events such as Black Friday.

===========

In the BIG-IP system, VLANs are the logical entities that group physical interfaces or trunks together. To modify how a VLAN interacts with an interface, the administrator must navigate to the specific VLAN configuration object.

VLAN List:This section displays all existing VLANs configured on the system.

Interface Association:Within the properties of a specific VLAN (in this case, "external"), there is anInterfacessection. This is where physical ports or trunks are assigned to the VLAN.

Tagging Status:For each associated interface, the administrator can choose betweenTagged(802.1Q) orUntagged.

Untagged:The interface will treat incoming traffic without a VLAN header as part of this VLAN, and outgoing traffic will not have a VLAN tag added. An interface can only be "Untagged" for one VLAN.

Tagged:Allows an interface to carry traffic for multiple VLANs simultaneously by using 802.1Q headers.