201 Practice Questions

The correct tmsh command to save the running configuration from memory to the configuration files on disk (e.g., bigip.conf) is save /sys config. This is equivalent to clicking the 'Save' button in the Configuration Utility.

The /var/log/platform_check log file is populated by the platform_check service, which periodically polls hardware components like fans, power supplies, and temperature sensors. This log is the primary location for identifying and troubleshooting physical hardware component failures or warnings.

This describes the correct hierarchy. A Virtual Server is the traffic listener. It directs traffic to a Pool, which is a logical group of backend servers. The members of the pool are the actual backend services, defined by a Node (the server's IP address) and a specific service port (e.g., 80, 443).

While some authentication protocols are time-sensitive, the most significant risk in this context is log correlation. For security incident response and general troubleshooting, having accurate, synchronized timestamps across all devices (BIG-IP, RADIUS server, firewalls, etc.) is critical. Without NTP, the BIG-IP's clock can drift, making it impossible to build an accurate timeline of events during an investigation.

The diagram shows SSL offloading, where the BIG-IP decrypts client traffic. A Client SSL profile handles segment 1. Since segment 2 is decrypted (plain HTTP), no Server SSL profile is needed. A Server SSL profile would only be used if the connection from the BIG-IP to the web server also needed to be re-encrypted.

The BIG-IP system is designed to handle this scenario explicitly. The 'Default Persistence Profile' is always checked first. If no persistence record is found using the default profile, the system then checks the 'Fallback Persistence Profile'. This allows for a layered approach to session persistence without requiring iRules or custom profiles for this common use case.

The standard F5 procedure for collecting EUD results involves using a USB flash drive. The EUD utility has a built-in function to detect the drive and save the diagnostic log file, which can then be easily transferred to another machine for review or uploaded to F5 Support.

The :p modifier used with the -i 0.0 interface tells tcpdump to capture traffic on the client-side of the flow after it has been decrypted by the Client SSL profile. This allows the administrator to see the raw, unencrypted application layer data (e.g., HTTP headers and payload) as it is processed by TMM, which is crucial for troubleshooting application-level performance issues.

Port Lockdown is a security feature configured on a per-self-IP basis. To check or change this setting, the administrator must navigate to Network > Self IPs, select the specific self-IP in question, and then review the 'Port Lockdown' setting. SSH is likely allowed while HTTPS is not.

A qkview file is a comprehensive snapshot of the BIG-IP system's configuration, logs, and real-time status. F5 Support engineers rely on this file as the primary source of information for troubleshooting. Uploading it to iHealth provides an initial automated analysis and makes the data readily available to the support team, significantly speeding up the diagnostic process.