Which menu should you use on the BIG-IP Configuration Utility to generate a QKView support file?(Choose one answer)
Answer(s): C
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.
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)
Answer(s): D
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.
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)
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.
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)
Answer(s): A,C
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.
Which menu should you use on the BIG-IP Configuration Utility to generate a QKView support file? (Choose one answer)
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.
Post your Comments and Discuss F5 F5CAB5 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the F5CAB5 content, but please register or login to continue.