Free F5 F5CAB4 Practice Exam with Questions & Answers

On BIG-IP systems that participate in a Device Service Cluster (DSC), each device compares the remote device’s system time to its own system time. If the difference is outside the ConfigSync time threshold (commonly referenced as 3 seconds by default), BIG-IP updates the shell prompt to show “Peer Time Out of Sync”, and ConfigSync operations may fail until time is corrected (typically by fixing NTP reachability/configuration, or in some cases adjusting the threshold). (cdn.studio.f5.com)

This message is specifically about time drift between peers in the trust domain/DSC—not basic reachability (so B is not what it means), and it does not prove which side is “correct” (so C is too specific). It also doesn’t directly mean an NTP source is “skewed” (A can be a cause, but the prompt message itself indicates the peer-to-peer time mismatch condition). (cdn.studio.f5.com)

On a BIG-IP system, remote syslog server configuration is managed through the logging configuration framework. In the Configuration Utility, this is accessed via:

System > Logs > Configuration

This section allows the administrator to:

Define remote syslog destinations

Configure log publishers

Control which log types (system, audit, LTM, ASM, etc.) are forwarded to external syslog servers

Why the other options are incorrect:

A. System > Configuration > Local TrafficUsed for traffic management settings, not logging.

C. System > Logs > AuditDisplays audit log settings and content but does not configure remote syslog destinations.

D. System > Configuration > DeviceUsed for device-level settings such as hostname and platform configuration, not logging.

Therefore, the correct location to reconfigure BIG-IP to send logs to new syslog servers is System > Logs > Configuration.

===========

On a BIG-IP system, NTP (Network Time Protocol) configuration is part of the system-level configuration settings. In the Configuration Utility, NTP servers are configured under the System configuration hierarchy.

The correct navigation path is:

System > Configuration > Device > NTP

This location allows the administrator to:

Add, modify, or remove NTP servers

Ensure accurate system time synchronization

Maintain proper time alignment required for features such as ConfigSync, HA failover, logging, and certificate validation

Why the other options are incorrect:

A. System > Platform is used for hardware-related settings.

B. System > Preferences manages UI and user preferences.

C. System > Services controls system daemons and services, not time configuration.

Therefore, the correct answer is D. System > Configuration.

===========

The "Management Port" is distinct from TMM data ports. Configuration for global platform-level settings, including administrative access restrictions (IP Allow lists for SSH and HTTPS) for the management port, is found under System > Platform. This is a critical Control Plane hardening step to prevent unauthorized remote access

Here is the next batch of 10 questions from your document that are 100% related to BIG-IP

The recommended and supported method for creating BIG-IP users from the CLI is through TMSH, using the authentication subsystem.

tmsh create auth user prompt-for-password:

Properly creates the user within BIG-IP’s AAA/authentication framework

Encrypts the password securely

Ensures the user is stored and managed correctly in the BIG-IP configuration database

Is fully supported and documented

Why the other options are incorrect:

B is unsafe and unsupported because editing bigip.conf directly and storing clear-text passwords violates security and configuration management best practices.

C (f5adduser / f5passwd) is deprecated and not recommended for modern BIG-IP versions.

D creates a Linux system user only, not a BIG-IP administrative user, and will not allow access to the Configuration Utility or TMSH roles.

When a failover occurs, the newly active device must inform the surrounding network that it now "owns" the shared IP addresses. Without MAC Masquerade, the new device uses its own hardware MAC, requiring upstream routers to update their ARP tables (which causes a delay). MAC Masquerading allows the HA pair to share a "floating" MAC address, ensuring the Control Plane transition is transparent to the network layer

Connectivity management requires a proper logical-to-physical mapping within the BIG-IP Control Plane.

VLAN Association: In TMOS, a Self IP address is not assigned directly to a physical interface. Instead, it is assigned to a VLAN (Virtual Local Area Network) object.

Procedural Troubleshooting: If a Self IP is unreachable, the primary failure point is often that the IP was associated with the wrong VLAN, or the VLAN itself is not correctly associated with the intended physical interface or trunk.

Layer 2 Mapping: The Control Plane requires the VLAN to be "up" and "untagged" or "tagged" on a valid interface for traffic to flow. If the administrator selects the incorrect VLAN, the Self IP will exist in the configuration but will be logically isolated from the physical network wire.

To maintain integrity in a High Availability environment, TMOS prevents the deletion of active Devic28e Groups. Procedurally, a device group is a container for synchronization; the Control Plane requires that you first strip the group of all associated members (devices) before the group object itself can be removed from the configuration.

On BIG-IP systems, all authentication attempts for administrative access—including logins to the Configuration Utility (GUI)—are logged in /var/log/secure. This log file records:

Successful and failed login attempts

The username used

The authentication method (local, LDAP, RADIUS, etc.)

Access denials and PAM authentication errors

Why the other options are incorrect:

/var/log/pam/tallylog tracks account lockouts and failed attempt counters, not detailed login attempts.

/var/log/ltm logs traffic management events, not administrative authentication.

/var/log/httpd logs web server activity but does not record authentication success or failure for BIG-IP administrative users.

Therefore, the correct log file to verify whether a user attempted to log in to the BIG-IP Configuration Utility is /var/log/secure.

===========

Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Admi13nistration documents:

To accurately report the current status of specific web applications hosted on the same server (node), the Control Plane must use a monitor that operates at the application layer.

Application-Specific Monitoring: While a node (the IP address) might be up and responding to ICMP (ping) or TCP handshakes, a specific web service or path on that server could be failing.

Custom Send Strings: An HTTP monitor allows the administrator to define a "Send String" to request a specific page or URI related to the application in that pool .

Receive Strings: The "Receive String" identifies a unique value that the application must return to be considered "Available" .

Granular Status Reporting: By deploying these monitors at the pool level, the Control Plane can mark a pool member "Offline" for one application pool if the receive string is missing, while keeping it "Available" in another pool where the service is still healthy.