F5CAB5 Exam dumps PDF | Exam-Dumps.net (Page: 2)

QUESTION: 9

Refer to the exhibit.

A BIG-IP Administrator needs to deploy an application on the BIG-IP system to perform SSL offload and re-encrypt the traffic to pool members. During testing, users are unable to connect to the application.

What must the BIG-IP Administrator do to resolve the issue? (Choose one answer)

Remove the configured SSL Profile (Client)
Configure Protocol Profile (Server) as splitsession-default-tcp
Enable Forward Proxy in the SSL Profile (Client)
Configure an SSL Profile (Server)

Answer(s): D

Explanation:

To successfully perform SSL offload and re-encryption on a BIG-IP system, the virtual server must be configured with both a Client SSL profile and a Server SSL profile. The Client SSL profile enables BIG-IP to decrypt inbound HTTPS traffic from clients, while the Server SSL profile is required to re-encrypt traffic before forwarding it to the pool members.

From the exhibit, the virtual server has a Client SSL profile configured, which allows BIG-IP to accept HTTPS connections from clients. However, there is no Server SSL profile attached, meaning BIG-IP attempts to send unencrypted HTTP traffic to pool members listening on HTTPS (port 443). This protocol mismatch causes the server-side SSL handshake to fail, resulting in users being unable to connect to the application.

This behavior is well documented in BIG-IP SSL troubleshooting guides: when backend servers expect HTTPS, a Server SSL profile is mandatory to establish a secure connection from BIG-IP to the pool members.

The other options are incorrect:

Removing the Client SSL profile (Option A) would break client-side HTTPS.

The server-side TCP profile (Option B) is unrelated to SSL encryption.

Forward Proxy (Option C) is only used for outbound SSL inspection scenarios.

Therefore, configuring an SSL Profile (Server) is the correct and required solution.

Reveal Solution Next Question

QUESTION: 10

A BIG-IP Administrator notices that one of the servers that runs an application is NOT receiving any traffic. The BIG-IP Administrator examines the configuration status of the application and observes the displayed monitor configuration and affected pool member status.

What is the possible cause of this issue? (Choose one answer)

The node health monitor is NOT responding.
The application is NOT responding with the expected Receive String.
HTTP 1.1 is NOT appropriate for monitoring purposes.
The BIG-IP device is NOT able to reach the pool.

Answer(s): A

Explanation:

The key clue in the exhibit is the pool member's availability showing "Offline (Enabled) Parent down". In BIG-IP terminology, a pool member inherits the status of its parent node. If the node is marked down (for example, by a node-level monitor or a default "node is down" condition), then all pool members using that node IP will also be marked down and will not receive any traffic, even if the application service on the member port might be healthy.

While the HTTPS monitor configuration (send/receive strings) is displayed, the status specifically indicates a node (parent) failure, not a service-level failure. If the problem were the application not matching the receive string, you would typically see the member down due to the member's monitor failing (and the status would reflect monitor failure details), rather than "parent down."

Option D is too broad; BIG-IP can generally reach the subnet (other servers work), and this symptom points to a specific node condition. Option C is incorrect because HTTP/1.1 is commonly used for monitoring and is valid when properly formatted (especially with a Host header). Therefore, the most likely cause is that the node health monitor is not responding, causing the node--and consequently the member--to be marked down.

Reveal Solution Next Question

QUESTION: 11

Which menu should you use on the BIG-IP Configuration Utility to generate a QKView support file?

(Choose one answer)

System > Configuration
System > Archive
System > Support
System > Logs

Answer(s): C

Explanation:

A QKView is the primary diagnostic file used by F5 Support to analyze BIG-IP system health, configuration, performance, and logs. It collects a wide range of data, including running configuration, license details, module provisioning, hardware status, logs, statistics, and diagnostic command output. Generating a QKView is a standard first step when troubleshooting issues or opening a support case with F5.

In the BIG-IP Configuration Utility (GUI), the correct location to generate a QKView is System > Support (Option C). This menu is specifically designed for support and troubleshooting activities. From this section, administrators can create QKView files, upload them directly to F5 iHealth, or download them locally for later analysis or submission to F5 Support.

The other options are incorrect:

System > Configuration (Option A) is used for system-wide settings such as device name, NTP, and DNS.

System > Archive (Option B) is used to create UCS backups, not diagnostic QKViews.

System > Logs (Option D) is used to view and manage log files, not to generate support bundles.

This workflow is clearly documented in BIG-IP Administration and Support guides and is considered a best practice for efficient troubleshooting and support engagement.

Reveal Solution Next Question

QUESTION: 12

A device group is currently in the Changes Pending sync status. How can the BIG-IP Administrator determine which member of the device group has the most recent configuration? (Choose one answer)

Device Management > Overview
Device Management > Devices
System > High Availability
Device Management > Device Groups

Answer(s): D

Explanation:

When a BIG-IP device group shows a Changes Pending status, it indicates that one or more devices in the group have configuration changes that have not yet been synchronized to the other members. To identify which device has the most recent (authoritative) configuration, the administrator must view the detailed synchronization status at the device group level.

The correct location is Device Management > Device Groups (Option D). Within this menu, the BIG-IP Configuration Utility displays each device group along with its synchronization status and provides details about which device has pending changes. From this view, the administrator can clearly see which device is marked as having changes pending, making it the source device that should be used to initiate a Sync to Group operation.

The other options do not provide the required level of detail:

Device Management > Overview (Option A) shows general HA status but not configuration ownership.

Device Management > Devices (Option B) lists devices but does not clearly identify which one holds unsynchronized changes.

System > High Availability (Option C) focuses on failover and traffic groups, not configuration sync state.

This workflow aligns with BIG-IP best practices for configuration synchronization and ensures changes are propagated correctly without overwriting newer configurations.

Reveal Solution Next Question

QUESTION: 13

A BIG-IP Administrator suspects that one of the BIG-IP device power supplies is experiencing power outages.

Which log file should the BIG-IP Administrator check to verify the suspicion? (Choose one answer)

/var/log/daemon.log
/var/log/kern.log
/var/log/ltm
/var/log/audit

Answer(s): C

Explanation:

According to official F5 documentation (K52015891 Troubleshooting BIG-IP power supply issues), hardware-related alerts for power supplies, fans, and chassis components are logged in /var/log/ltm.

When a BIG-IP device experiences a power supply issue--such as failure, intermittent outages, or fan-related faults--the system generates alerts through internal platform monitoring services. These alerts are written to the /var/log/ltm file and often appear with messages similar to:

Chassis power supply 2 has experienced an issue. Status is as follows: FAN=bad; STATUS=bad.

This makes /var/log/ltm the authoritative log file for identifying and verifying power supply and chassis-related problems on BIG-IP systems.

The other log files are not appropriate for this purpose:

/var/log/daemon.log contains general daemon messages but is not the primary source for chassis hardware alerts.

/var/log/kern.log logs kernel-level events, not platform power status.

/var/log/audit records administrative actions and configuration changes.

Conclusion:
Per F5-supported guidance, when suspecting power supply outages or chassis hardware issues, the BIG-IP Administrator should always check /var/log/ltm first.

Reveal Solution Next Question

QUESTION: 14

Refer to the exhibit.

The image shows the status of a virtual server named application_vs in the BIG-IP Configuration Utility.

What is the cause of the status shown? (Choose two answers)

Pool member(s) administratively disabled
Pool member(s) forced offline
Node(s) administratively disabled
Virtual Server administratively disabled

Answer(s): A,C

Explanation:

The exhibit shows the virtual server application_vs with a status indicating it is offline but enabled. In BIG-IP terminology, this status means the virtual server itself is administratively enabled, but it is unable to pass traffic because no usable pool members are available.

Two common and documented causes for this condition are:

Pool member(s) administratively disabled (Option A):
When all pool members are administratively disabled, BIG-IP removes them from load-balancing decisions. Even though the virtual server remains enabled, it has no available pool members to send traffic to, resulting in an offline status.

Node(s) administratively disabled (Option C):
Pool members inherit the status of their parent nodes. If a node is administratively disabled, all associated pool members are also marked unavailable. This condition causes the virtual server to show as offline, even though the virtual server configuration itself is correct.

The other options are incorrect:

Forced offline pool members (Option B) result in a different operational intent and are explicitly set for maintenance scenarios.

Virtual server administratively disabled (Option D) would show the virtual server as disabled, not enabled/offline.

This behavior is consistent with BIG-IP traffic management logic and is commonly verified by reviewing pool and node availability states when diagnosing virtual server availability issues.

Reveal Solution Next Question

QUESTION: 15

Which menu should you use on the BIG-IP Configuration Utility to generate a QKView support file? (Choose one answer)

System > Configuration
System > Archive
System > Support
System > Logs

Answer(s): C

Explanation:

Comprehensive and Detailed 150 to 250 Words Explanation From BIG-IP Administration, Support, and Troubleshooting Documents:

A QKView file is the primary diagnostic support bundle used by F5 Support to troubleshoot BIG-IP system issues. It contains comprehensive system information, including running configuration, licensing details, module provisioning, hardware status, software versions, log files, statistics, and the output of numerous diagnostic commands. Generating a QKView is a standard and recommended first step when investigating performance problems, configuration issues, or when opening a support case with F5.

In the BIG-IP Configuration Utility (GUI), the correct and supported location to generate a QKView is System > Support. This menu is specifically designed for support and troubleshooting operations. From this section, administrators can generate a QKView file, monitor its creation progress,

download it locally, or upload it directly to F5 iHealth for automated analysis. This workflow is clearly documented in BIG-IP Administration and Support guides and aligns with F5 best practices.

The other menu options are not appropriate:

System > Configuration is used for system-wide settings such as DNS, NTP, and device identity.

System > Archive is used to create UCS backup files, which are configuration backups, not diagnostic bundles.

System > Logs is used only for viewing system logs, not generating support files.

Therefore, System > Support is the correct and only valid answer.

Reveal Solution Next Question

QUESTION: 16

A BIG-IP Administrator observes the following messages in the /var/log/ltm log:

warning tmm[pid]: 011e0002: sweeper_segment_cb_any: Aggressive mode /Common/default- eviction-policy activated (0) (global memory) (345209/690176 pages)

warning tmm[pid]: 011e0003: Aggressive mode sweeper /Common/default-eviction-policy (0) (global memory) 1 connections killed warning tmm[pid]: 011e0003: Aggressive mode sweeper /Common/default-eviction-policy (0) (global memory) 1 connections killed warning tmm[pid]: 011e0003: Aggressive mode sweeper /Common/default-eviction-policy (0) (global memory) 1 connections killed

What is happening when the BIG-IP Administrator sees the messages displayed above? (Choose two answers)

The global eviction policy is triggered due to TMM memory exhaustion
The BIG-IP system starts reaping connections; all the connections will be dropped
The BIG-IP system starts reaping connections; some connections will be dropped
The global eviction policy is triggered due to swap memory being used too high

Answer(s): A,C

Explanation:

Comprehensive and Detailed 150 to 250 Words Explanation From BIG-IP Administration, Support, and Troubleshooting Documents:

These log messages indicate that the BIG-IP system's Traffic Management Microkernel (TMM) has entered aggressive eviction mode due to high global memory utilization.
When TMM memory consumption reaches critical thresholds, BIG-IP activates the default eviction policy to protect system stability and prevent a full traffic processing failure. This condition directly corresponds to Option A, where the global eviction policy is triggered because TMM memory resources are nearing exhaustion.

Once aggressive mode is activated, BIG-IP begins using the connection sweeper mechanism, which selectively terminates existing connections to free memory. The repeated log entries stating "1 connections killed" confirm that the system is reaping some connections, not all connections. This behavior matches Option C. The eviction process is incremental and controlled, targeting idle, low- priority, or least-recently-used connections first to minimize impact on active traffic.

Option B is incorrect because BIG-IP does not drop all connections during aggressive mode; it only removes enough connections to relieve memory pressure. Option D is also incorrect because TMM eviction is based on TMM global memory usage, not swap memory utilization. TMM does not rely on swap space in the same way the host Linux system does.

These messages are a critical warning sign that the system is under memory stress and may require traffic optimization, connection limits, or hardware scaling.

Reveal Solution Next Question

F5 F5CAB5 Exam (page: 2) F5 BIG-IP Administration Support and Troubleshooting Updated on: 06-Apr-2026

QUESTION: 9

Explanation:

QUESTION: 10

Explanation:

QUESTION: 11

Explanation:

QUESTION: 12

Explanation:

QUESTION: 13

Explanation:

QUESTION: 14

Explanation:

QUESTION: 15

Explanation:

QUESTION: 16

Explanation:

F5 F5CAB5 Exam (page: 2)
F5 BIG-IP Administration Support and Troubleshooting
Updated on: 06-Apr-2026