Refer to the exhibit.

The BIG-IP Administrator is investigating disk utilization on the BIG-IP device. What should the BIG-IP Administrator check next? (Choose one answer)
When troubleshooting a BIG-IP system where a partition is reported as full (100% utilization), identifying and removing large or unnecessary files is the immediate next step for restoration of system stability.
Symptoms of Full Partitions: If a file system (such as the root / or /var) becomes full, it can result in unpredictable system behavior, failure to save configurations, and the inability to log in to the Web UI.
The Root (/) Partition: This partition is intentionally kept small on F5 systems. It is highly sensitive to the storage of third-party software or diagnostic files that should ideally be stored in the /shared or /var directories.
Procedural Resolution: To resolve 100% disk usage, administrators should check for large files on the affected partition using CLI commands like du -ah or find / -xdev -type f -exec du {} \; | sort -rn | head -20.
Common Culprits: Large files typically causing these issues include old core files, tech support bundles, large diagnostic logs (packet diags), or temporary files created during administrative tasks.
Diagnostics vs. Remediation: While tests like the EUD (End User Diagnostics) or platform diagnostics are useful for hardware verification, they do not resolve file system exhaustion issues that have already reached a critical 100% state.
A user needs to generate a QKView to upload to iHealth to determine any issues with upgrading TMOS. Where can the user generate the QKView in the Configuration Utility?
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents: Generating a QKView is a standard procedure for identifying device health and upgrade readiness42. Within the Configuration Utility, this Control Plane diagnostic tool is located under System > Support43. This utility collects configuration and state data into a single file used by the iHealth 'Upgrade Advisor' to report on known bugs or compatibility issues prior to a version change.
Which method is recommended for creating a new user from the CLI? (Choose one answer)
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
The recommended and supported method for creating BIG-IP users from the CLI is through TMSH, using the authentication subsystem.
tmsh create auth user <username> 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 looking at this BIG-IP prompt: root@virtual-bigip1] Peer Time Out of Sync
What does the message indicate? (Choose one answer)
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
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)
A configuration change is made on the standby member of a device group. What is displayed as "Recommended Action" on the Device Management Overview screen?
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents: The BIG-IP Control Plane monitors the 'Commit ID' of the configuration on all group members. When a change is made on the Standby unit, it becomes the member with the most recent configuration. The 'Recommended Action' in the HA status dashboard will be to synchronize that specific device's configuration to the rest of the group to ensure consistency
Ryan Perez
3 days agoCarol Walker
22 days agoRachel Nguyen
1 month agoSharon White
1 month agoJason Robinson
1 month agoTiffany Smith
1 month agoKenneth Gonzalez
1 month agoMelissa Ramirez
1 month agoRyan Phillips
1 month agoTimothy
2 months agoLelia
2 months agoMarkus
3 months agoYoulanda
3 months agoNieves
3 months agoJoanna
3 months agoMarylin
4 months agoGayla
4 months agoValentin
4 months agoTanesha
4 months agoMabel
5 months agoIlona
5 months agoJosphine
5 months agoTijuana
5 months agoIsaiah
6 months ago