매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
BIG-IP Administration Control Plane Administration 온라인 연습
최종 업데이트 시간: 2026년02월14일
당신은 온라인 연습 문제를 통해 F5 F5CAB4 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 F5CAB4 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 53개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
A BIG-IP device group cannot be deleted if it still contains device members, even if one of those devices has already been decommissioned or is unreachable. Before deleting the device group, the administrator must explicitly remove the decommissioned device from the device group configuration.
Once the removed or unreachable device is deleted from the device group membership, the BIG-IP system allows the remaining administrator to successfully delete the device group.
Why the other options are incorrect:
A. Remove all members from the device group
This is not required; the key requirement is removing the decommissioned device, not all members. B. Make sure all members are in sync
Synchronization status does not prevent device group deletion.
D. Disable the device group
Device groups cannot be disabled; they must be modified or deleted.
Therefore, the correct prerequisite action is to remove the decommissioned device from the device group, making C the correct answer.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
In the BIG-IP Configuration Utility, all system backup and restore operations―including UCS (User Configuration Set) file restoration―are performed from the Archives section.
The correct navigation path is:
System > Archives
From this location, the administrator can:
Upload UCS files
Restore UCS backups
Manage system archive files used for backup and recovery
Why the other options are incorrect:
A. System > Configuration is used for general system settings, not backup restoration.
C. Local Traffic > Virtual Servers is used for application traffic objects.
D. Local Traffic > Policies manages traffic policies, not system backups.
Therefore, the correct section to restore a UCS file using the Configuration Utility is System > Archives.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
On BIG-IP systems, all authentication attempts for administrative access―including logins to the Configuration Utility (GUI)―are logged in /var/log/secure.
This log file records:
Successful and failed login attempts
The username used
The authentication method (local, LDAP, RADIUS, etc.)
Access denials and PAM authentication errors
Why the other options are incorrect:
/var/log/pam/tallylog tracks account lockouts and failed attempt counters, not detailed login attempts.
/var/log/ltm logs traffic management events, not administrative authentication.
/var/log/httpd logs web server activity but does not record authentication success or failure for BIG-IP administrative users.
Therefore, the correct log file to verify whether a user attempted to log in to the BIG-IP Configuration Utility is /var/log/secure.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
When restoring a User Configuration Set (UCS) file, BIG-IP allows administrators to selectively exclude the license during the restore process. From the CLI, this is accomplished using the no-license option with the tmsh load /sys ucs command.
The command:
tmsh load /sys ucs <ucs filename> no-license
restores:
System configuration
Certificates and keys
Device and traffic objects
while explicitly excluding the license file, which is required when:
Migrating configurations between devices
Restoring to hardware with a different license
Avoiding license conflicts or overwrites
Why the other options are incorrect:
A does not provide the option to exclude the license.
B restores the UCS including the license, which does not meet the requirement.
D is incorrect because the BIG-IP GUI does not provide a checkbox to exclude the license during UCS restore.
Therefore, the correct and supported method is C.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
When BIG-IP is configured to use remote authentication (such as LDAP), all authentication and authorization attempts―including successes and failures―are logged to /var/log/secure.
For LDAP-based administrative login issues, /var/log/secure contains:
LDAP authentication failures
PAM authentication errors
Authorization and access-denied messages
Details explaining why a remote user could not log in
Why the other options are incorrect:
/var/log/user.log is not a standard BIG-IP log file for authentication.
/var/log/ltm logs traffic management events, not user authentication.
/var/log/messages contains general system messages but not detailed authentication failure information.
Therefore, the correct log file to troubleshoot LDAP administrative login failures is /var/log/secure.
정답:
Explanation:
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 management
Health monitor execution
Marking pool members UP or DOWN based on monitor results
Events 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.
정답:
Explanation:
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-status
This command displays:
The current failover state (active, standby, or offline)
Detailed failover status information
The operational HA condition of the device within a device group
According 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-status
Why 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.
정답:
Explanation:
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 attempts
Invalid user authentication attempts
PAM (Pluggable Authentication Module) authentication failures
Access denials related to secure services
Why 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.
정답:
Explanation:
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 > Configuration
This section allows the administrator to:
Define remote syslog destinations
Configure log publishers
Control which log types (system, audit, LTM, ASM, etc.) are forwarded to external syslog servers
Why the other options are incorrect:
A. System > Configuration > Local Traffic
Used for traffic management settings, not logging.
C. System > Logs > Audit
Displays audit log settings and content but does not configure remote syslog destinations.
D. System > Configuration > Device
Used 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.
정답:
Explanation:
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.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
BIG-IP supports remote authentication by integrating with centralized authentication services through its AAA framework. The supported and commonly used remote authentication servers include:
LDAP (A)
Used to authenticate users against directory services such as Active Directory or other LDAP-compliant directories.
RADIUS (C)
Commonly used for centralized authentication, authorization, and accounting, especially in network and security environments.
Why the other options are incorrect:
OAUTH (B) is an authorization framework, not supported as a direct administrative authentication backend for BIG-IP management access.
SAML (D) is primarily used for single sign-on (SSO) in application authentication scenarios, not for BIG-IP administrative login authentication.
Thus, the correct remote authentication server types are LDAP and RADIUS.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
Traffic Groups are the mechanism BIG-IP uses to control which device owns specific application traffic in a high-availability (HA) configuration. When maintenance is required on a device that is currently active for a traffic group, the correct and recommended action is to fail over that traffic group to another device in the device group.
Failing over the traffic group moves ownership of that traffic group (and the virtual servers associated with it) to another available device without forcing the entire device into standby.
This allows targeted maintenance while minimizing impact to other traffic groups that may still be active on the device.
Why the other options are incorrect:
A is unnecessary and incorrect; traffic groups are not recreated for routine maintenance.
C forces the entire device to standby, which may move more traffic than intended.
D (Demote) affects device trust/priority behavior and is not the standard or recommended method for moving traffic group ownership.
Therefore, selecting the Traffic Group and choosing Failover is the correct solution.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
In netstat output:
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
On BIG-IP systems, SSH access restrictions are configured under the /sys sshd object. The allow property defines the IP addresses or networks permitted to connect to the management interface using SSH.
The list command is used to display the current configuration settings.
Therefore, tmsh list /sys sshd allow correctly displays the configured allowed IP ranges.
Why the other options are incorrect:
A (show) displays runtime or statistical information, not configuration values.
C and D incorrectly reference /etc/hosts.allow; BIG-IP manages SSH access through TMSH objects, not by directly listing host files in this context.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:
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.