An organization is performing a major release upgrade to its BIG-IP system. The system is under medium load and has enough disk space to perform the upgrade.Which pre-upgrade task is disruptive to regular system performance and should be performed during a maintenance window? (Choose one answer)
Answer(s): B
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:Reactivating a BIG-IP license is a traffic-disruptive operation. During the license reactivation process, the BIG-IP system performs a configuration reload, which results in a temporary interruption of all traffic processing. Because traffic handling is affected, F5 explicitly recommends scheduling license updates during a maintenance window.This behavior is documented in F5 Knowledge Base articles, which state that license reactivation impacts traffic and must be planned accordingly during upgrades or system changes.The other options are not considered disruptive:Creating a QKView is primarily a diagnostic task and does not interrupt traffic.Running tmsh save sys config only saves the running configuration to disk.Generating a UCS is resource-intensive but does not reload configuration or interrupt traffic processing.
New Syslog servers have been deployed in an organization. The BIG-IP Administrator must reconfigure the BIG-IP system to send log messages to these servers.In which location in the Configuration Utility can the BIG-IP Administrator make the needed configuration changes to accomplish this? (Choose one answer)
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents: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 > ConfigurationThis section allows the administrator to:Define remote syslog destinationsConfigure log publishersControl which log types (system, audit, LTM, ASM, etc.) are forwarded to external syslog serversWhy 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.===========
The BIG-IP Administrator suspects unauthorized SSH login attempts on the BIG-IP system.Which log file would contain details of these attempts? (Choose one answer)
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:On BIG-IP systems, authentication and authorization events are logged in /var/log/secure. This includes:Successful and failed SSH login attemptsInvalid user authentication attemptsPAM (Pluggable Authentication Module) authentication failuresAccess denials related to secure servicesWhy the other options are incorrect:/var/log/messages contains general system messages and service events, not detailed authentication failures./var/log/audit records administrative configuration changes (who changed what and when), not login attempts./var/log/ltm logs traffic-management (TMM) and application-related events.Therefore, the correct log file for investigating unauthorized SSH login attempts is /var/log/secure.===========
Which command will provide the BIG-IP Administrator with the current device HA status? (Choose one answer)
Answer(s): C
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:To determine the current failover (HA) status of a BIG-IP system using tmsh, F5 documentation explicitly states that the administrator should use the following command:show /cm failover-statusThis command displays:The current failover state (active, standby, or offline)Detailed failover status informationThe operational HA condition of the device within a device groupAccording to F5 Knowledge Base Article K08452454, the documented procedure for checking failover status is:Log in to the TMOS Shell (tmsh)Run show /cm failover-statusWhy the other options are incorrect:A . list /cm failover shows configuration settings, not operational HA status.B . show /sys failover is not the documented command for checking current failover status and does not align with F5's recommended procedure.
In which of the following log files would log events pertaining to pool members being marked "UP" or "DOWN" by their Health Monitors be written? (Choose one answer)
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:On BIG-IP systems, Local Traffic Manager (LTM) is responsible for:Pool and pool member managementHealth monitor executionMarking pool members UP or DOWN based on monitor resultsEvents related to health monitor status changes, including when pool members transition between UP and DOWN, are logged in /var/log/ltm.Why the other options are incorrect:/var/log/audit records administrative configuration changes, not runtime health status./var/log/secure logs authentication and authorization events./var/log/monitors is not a standard BIG-IP log file.Therefore, the correct log file for pool member health monitor status events is /var/log/ltm.===========
Post your Comments and Discuss F5 F5CAB4 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 F5CAB4 content, but please register or login to continue.