매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
BIG-IP Administration Support and Troubleshooting 온라인 연습
최종 업데이트 시간: 2026년02월14일
당신은 온라인 연습 문제를 통해 F5 F5CAB5 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 F5CAB5 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 42개의 시험 문제와 답을 포함하십시오.
정답:
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.
정답:
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.
정답:
Explanation:
According to official F5 documentation (K52015891 C 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.
정답:
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.
정답:
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.
정답:
Explanation:
The key clue in the exhibit is the pool member’s availability showing “Offline (Enabled) C 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.
정답:
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.
정답:
Explanation:
This virtual server is intended to function as a forwarding (IP-forwarding) virtual server, which is commonly used for routing or firewall-style deployments where BIG-IP forwards traffic transparently without load balancing or address translation. For a forwarding virtual server to match and pass all traffic, the destination must be configured as 0.0.0.0:any with a mask of 0.0.0.0, not 255.255.255.255.
The configured mask 255.255.255.255 represents a /32 host mask, which restricts the virtual server to matching traffic destined only for the exact IP address 0.0.0.0. Since 0.0.0.0 is not a valid routable destination for normal traffic, no packets will ever match the virtual server, causing it to pass no traffic at all.
This is a well-documented BIG-IP behavior:
destination 0.0.0.0:any
mask 0.0.0.0
together define a catch-all forwarding virtual server.
The destination itself (Option A) is correct for a forwarding VS, and disabling address translation (Option C) is expected and required for IP-forwarding mode. Therefore, the incorrect subnet mask is the sole reason the virtual server is not functioning as expected.
정답:
Explanation:
A gateway_icmp monitor checks basic network reachability by sending ICMP echo requests (pings) to the pool member or its gateway. If the pool is marked DOWN while the server is confirmed to be online, the most likely cause is that ICMP traffic is being blocked.
A host-based firewall active on the server (Option C) can block ICMP echo requests or replies, preventing BIG-IP from receiving a successful response to the health check. This results in the monitor failing and the pool member being marked down, even though the server and application are otherwise functioning normally. This explanation is consistent with the scenario where other servers in the same subnet work correctly, indicating that routing and BIG-IP configuration are not the issue.
The other options are unrelated to ICMP monitoring. Logged-in users (Option A), missing patches (Option B), and stopped HTTP services (Option D) do not affect a gateway_icmp monitor. BIG-IP troubleshooting best practices recommend verifying ICMP reachability and firewall policies when diagnosing ICMP-based monitor failures.
정답:
Explanation:
In an HTTPS session, the application-layer payload―including HTTP request headers, response headers, cookies, and body content―is encrypted using SSL/TLS. Without decrypting the traffic (for example, without SSL offloading on BIG-IP or access to the private keys), a packet capture cannot reveal any HTTP-level details.
However, network-layer and transport-layer information remains visible, even when encryption is used. This includes source and destination IP addresses, source and destination ports, TCP flags, sequence numbers, and TLS handshake metadata. Therefore, the source IP address (Option B) is visible in a packet capture of HTTPS traffic without decryption.
Options A, C, and D are incorrect because HTTP headers and cookies are part of the encrypted payload once HTTPS is established. BIG-IP troubleshooting documentation emphasizes this distinction when analyzing encrypted traffic flows using tcpdump, as administrators must rely on IP, port, and timing information unless SSL inspection or decryption is configured.
정답:
Explanation:
The pool member is marked DOWN because it is monitored by multiple health monitors, specifically an HTTP monitor and an HTTP/2 monitor. The status message clearly shows that the HTTP monitor is UP, while the HTTP/2 monitor is DOWN. In BIG-IP, when multiple monitors are assigned to a pool member, the default behavior is AND logic, meaning all assigned monitors must succeed for the pool member to be considered healthy.
In this scenario, the server is responding successfully to standard HTTP (likely HTTP/1.1) requests but does not support or respond correctly to HTTP/2 requests. As a result, the HTTP/2 monitor fails, which causes the overall monitor status to be DOWN, even though HTTP traffic itself is working.
This behavior is expected and documented in BIG-IP monitoring logic. Unless the monitor rule is explicitly changed to “at least one of”, a single failing monitor will mark the pool member down. Therefore, the correct conclusion is that the pool member is only serving HTTP traffic, not HTTP/2.
The resolution would be to either remove the HTTP/2 monitor, correct the application to support HTTP/2, or adjust the monitor rule to match the intended health-check logic.
정답:
Explanation:
When a pool member is marked DOWN, it indicates that the configured health monitor is failing. The most effective troubleshooting approach is to focus on the monitor behavior and the actual traffic between BIG-IP and the pool member.
Enabling monitor logging (Option B) is a recommended first step. Monitor logging provides detailed information about why the health check is failing, such as timeouts, connection refusals, incorrect responses, or unexpected status codes. This directly correlates with BIG-IP troubleshooting best practices and allows administrators to confirm whether the failure is due to application behavior, incorrect monitor configuration, or network reachability.
Collecting a TCPdump packet capture (Option D) is also a highly effective method. A packet capture allows the administrator to verify whether the monitor probes are being sent, whether responses are received, and whether packets are being dropped, reset, or malformed. This is especially valuable when diagnosing firewall issues, SSL problems, or application-level failures.
Reviewing pool statistics (Option C) is useful for general monitoring but does not explain why a health monitor is failing. Reviewing the routing table (Option A) is typically unnecessary unless there is evidence of a broader routing issue affecting multiple destinations.
정답:
Explanation:
To collect application-layer details such as HTTP status codes (200, 404, 500, etc.) and HTTP methods (GET, POST, PUT, DELETE), the BIG-IP system must use a profile designed for traffic visibility and reporting rather than basic traffic handling. The Analytics profile (Option C) is the correct choice because it is specifically designed to collect, store, and present detailed statistics about HTTP and TCP traffic passing through a virtual server.
When an Analytics profile is attached to a virtual server, BIG-IP can record metrics such as HTTP response codes, request methods, URI paths, latency, throughput, and client-side/server-side performance data. These statistics are then accessible through the BIG-IP GUI under Statistics → Analytics, allowing administrators to validate application behavior and troubleshoot performance or functional issues.
The HTTP profile (Option B) enables HTTP protocol awareness and features like header insertion and compression, but it does not provide historical or statistical reporting of HTTP methods and response codes. Request Adapt (Option A) is used for ICAP-based content adaptation, not visibility. Statistics (Option D) is not a standalone profile and does not provide HTTP-level insight.
Therefore, the Analytics profile is the only default profile that fulfills this requirement.
정답:
Explanation:
Before upgrading a BIG-IP system to a newer TMOS version, it is critical to review known issues to avoid introducing instability or regressions. F5 Bug Tracker (Option B) is a primary resource for this purpose. It allows administrators to search for documented software defects by TMOS version, module, symptom, or bug ID. Using Bug Tracker, an administrator can identify unresolved issues, fixed bugs, and behavioral changes that may affect their specific deployment, such as traffic handling, high availability, or module-specific functionality. This directly supports proactive troubleshooting and informed upgrade planning.
F5 iHealth (Option D) is another essential tool used during upgrade preparation. iHealth analyzes uploaded UCS or QKView files and correlates the device configuration and software version with F5’s known issues database. It provides actionable reports highlighting critical defects, upgrade risks, interoperability concerns, and recommended target versions. iHealth is especially valuable because it contextualizes known issues based on the actual configuration running on the device.
The other options are not appropriate for verifying known software issues. F5 End User Diagnostics (Option A) is a client-side troubleshooting tool, F5 University (Option C) is a training platform, and F5 Downloads (Option E) is primarily used to obtain software images and release notes, not to analyze known defects in depth.
정답:
Explanation:
Uneven load balancing on a BIG-IP system typically occurs when traffic is not distributed evenly across all available pool members. One common reason is that monitors have marked down multiple pool members (Option B). When health monitors fail for specific pool members, BIG-IP automatically removes those members from load-balancing decisions. As a result, traffic is sent only to the remaining healthy member, creating the appearance that load balancing is not functioning correctly. This behavior is expected and aligns with BIG-IP’s design to ensure traffic is sent only to healthy resources.
Another frequent cause is the presence of a persistence profile on the pool or virtual server (Option C). Persistence (such as source address or cookie persistence) forces subsequent client connections to be sent to the same pool member for session continuity. While persistence is critical for certain applications, it can override the load-balancing algorithm and cause most or all traffic to be directed to a single pool member, especially during low traffic volumes or testing scenarios.
The other options are incorrect because a virtual server marked down (Option A) would not pass traffic at all, and all pool members marked down (Option D) would result in no connections rather than uneven distribution. This analysis follows standard BIG-IP troubleshooting methodology using pool status, monitor results, and persistence configuration review