F5CAB4 Exam Questions 2026 – Real Practice Test with Verified Answers

Explanation:
When a BIG-IP Administrator changes module provisioning (for example, enabling ASM on a system previously provisioned only for LTM), the BIG-IP system must restart the Traffic Management Microkernel (TMM) process.
The TMM process is responsible for:
Traffic handling
LTM, ASM, and other traffic-processing modules
Enforcing security and application policies
Provisioning changes affect how traffic modules are loaded and integrated into TMM. As a result, TMM is restarted, which causes a temporary interruption of traffic processing. This is expected behavior and is why module provisioning changes should be planned during a maintenance window.
Why the other options are incorrect:
A. bd is related to blade/platform management, not module provisioning.
C. sshd handles SSH access and is not affected by provisioning changes.
D. httpd supports the Configuration Utility (GUI) and does not restart due to module provisioning.
Therefore, the correct answer is B. tmm.

Explanation:
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

Explanation:
The audit log (/var/log/audit) records configuration changes made on the BIG-IP system, including:
Who made the change (user account)
What was changed (for example, a virtual server modification)
When the change occurred
How it was performed (GUI, TMSH, or API)
Why the other options are incorrect:
/var/log/secure logs authentication events such as login successes and failures, not configuration changes.
/var/log/ltm logs traffic-management and runtime LTM events, not administrative configuration modifications.
Therefore, the correct log file for tracking who changed a virtual server is /var/log/audit.

Explanation:
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.

Explanation:
This log message indicates that the system is low on memory and has activated 'Aggressive Mode' to reclaim resources by closing old connections37. In an HA environment, one way to ensure state stability during memory pressure is to manage how connection data is handled38. While the document suggests D, procedural mitigation for 'Aggressive Mode' often involves reviewing resource provisioning or optimizing connection idle timeouts to reduce memory footprint39.