매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
BIG-IP Administration Support and Troubleshooting 온라인 연습
최종 업데이트 시간: 2026년03월09일
당신은 온라인 연습 문제를 통해 F5 F5CAB5 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 F5CAB5 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 42개의 시험 문제와 답을 포함하십시오.
정답: A
Explanation:
The "Manual Resume" feature is a safety mechanism used when a pool is not working as expected due to flapping services or unstable backend applications. Normally, when a health monitor fails, the pool member is marked "Offline" (Red), and when the monitor passes, it automatically returns to "Available" (Green) 47. However, if "Manual Resume" is enabled, the BIG-IP will not automatically put the member back into rotation after a failure48. Even if the health check begins to pass again, the member remains in an "Offline (Disabled) " state49. This requires an administrator to manually intervene and re-enable the member. This is a common point of confusion when troubleshooting; a member may show passing health checks but still not receive traffic because it is waiting for a manual administrative "resume" command. This feature is intended to prevent "unhealthy" servers from receiving traffic until an engineer has confirmed the root cause of the initial failure was resolved.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP A41dministration Support and Troubleshooting documents: To confirm functionality across a complex environment, the "Network Map" is the most efficient troubleshooting tool in the Configuration Utility43. It provides a hierarchical, visual representation of the traffic management objects44. A single glance allows the administrator to see the status of a Virtual Server (Green/Red/Yellow), the status of its associated pool, the health of individual pool members, and which iRules are currently attached45. This view is superior to the standard "Virtual Server List" for troubleshooting because it maps the dependencies between objects46. For example, if a Virtual Server is "Red, " the Network Map will show if that status is inherited from a failed pool or a specific monitor failing on a pool member. Reviewing these basic stats in the Network Map helps the administrator quickly isolate whether a failure is at the service level (Virtual Server), the logic level (iRule), or the hardware level (Pool Member).
정답:
Explanation:
When load balancing is not working as 23expected and connections appear skewed across physical hardware, the administrator must distinguish between "member"24 and "node" level balancing. A "member" refers to a specific IP and Port combination (e.g., 10.1.1.1:80), whereas a "node" refers to the underlying IP address (10.1.1.1) regardless of the port25. If a single server hosts multiple services (Web, FTP, API) across different pools, using "Least Connections (member) " would only balance connections within each individual pool26. This could lead to a scenario where one server is overwhelmed because it is winning the "least connections" count in three different pools simultaneously. By selecting "Least Connections (node), " the BIG-IP tracks the total number of concurrent connections to the physical IP address across all pools it belongs to27. This ensures that the administrator can maintain an equal distribution of work across the hardware, preventing performance degradation on backend servers that host multiple application services.
정답:
Explanation:
Comprehensive and Detailed Explanation From BIG-IP Administration Supp13ort and Troubleshooting documents: When troubleshooting a Virtual Server that is not working as expected, it is critical to ensure that the applied profiles match the type of traffic being processed. SSH (Secure Shell) is a non-HTTP protocol that operates over TCP. The exhibit indicates that an HTTP profile is applied to the Virtual Server14. An HTTP profile instructs the BIG-IP system to parse traffic as HTTP; however, since SSH traffic does not follow HTTP specifications, the BIG-IP's parser will fail to understand the data stream, typically resulting in dropped packets or reset connections15. To fix this, the administrator must set the HTTP profile to "None"16. This allows the Virtual Server to act as a "Standard" or "FastL4" listener that passes the encrypted SSH data transparently to the backend pool members without attempting application-layer inspection. This highlights a common troubleshooting step: verifying that L7 profiles are not inadvertently applied to L4 traffic, which disrupts the expected traffic flow between the client and the server.
정답:
Explanation:
In F5 TMOS administration, the traffic flow is processed through specific event huddles w3ithin iRules. To troubleshoot or m4odify traffic based on a URI (Uniform Resource Identifier), the BIG-IP system must first parse the application-layer data. The HTTP_REQUEST event is triggered when the system has fully received and parsed the HTTP request headers from the client5. This is the correct point to implement logic that selects a pool or pool member based on the path or file requested (e.g., /images or /api). Using CLIENT_ACCEPTED would be too early in the troubleshooting process because that event triggers at the L4 (TCP) connection establishment phase, before any URI information is available6. Conversely, HTTP_RESPONSE occurs during the return traffic from the server, which is too late to make a load balancing decision7. For troubleshooting virtual server behavior where URIs are involved, ensuring the iRule is attached to a Virtual Server with an HTTP profile and using the HTTP_REQUEST event is essential for proper traffic steering and inspection.
정답:
Explanation:
Comprehensive and Detailed 150 to 250 Words Explanation From BIG-IP Administration, Support, and Troubleshooting Documents:
These log messages indicate that the BIG-IP system’s Traffic Management Microkernel (TMM) has enteredaggressive eviction modedue tohigh global memory utilization. When TMM memory consumption reaches critical thresholds, BIG-IP activates the default eviction policyto protect system stability and prevent a full traffic processing failure. This condition directly corresponds to Option A, where the global eviction policy is triggered because TMM memory resources are nearing exhaustion.
Once aggressive mode is activated, BIG-IP begins using the connection sweeper mechanism, which selectively terminates existing connections to free memory. The repeated log entries stating“1 connections killed”confirm that the system is reaping some connections, not all connections. This behavior matches Option C. The eviction process is incremental and controlled, targeting idle, low-priority, or least-recently-used connections first to minimize impact on active traffic.
Option B is incorrect because BIG-IP doesnotdrop all connections during aggressive mode; it only removes enough connections to relieve memory pressure.
Option D is also incorrect because TMM eviction is based on TMM global memory usage, not swap memory utilization. TMM does not rely on swap space in the same way the host Linux system does.
These messages are a critical warning sign that the system is under memory stress and may require traffic optimization, connection limits, or hardware scaling.
정답:
Explanation:
Comprehensive and Detailed 150 to 250 Words Explanation From BIG-IP Administration, Support, and Troubleshooting Documents:
AQKViewfile 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 isSystem > 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 > Configurationis used for system-wide settings such as DNS, NTP, and device identity.
System > Archiveis used to create UCS backup files, which are configuration backups, not diagnostic bundles.
System > Logsis used only for viewing system logs, not generating support files.
Therefore, System > Supportis the correct and only valid answer.
정답:
Explanation:
The exhibit shows the virtual serverapplication_vswith a status indicating it isoffline but enabled. In BIG-IP terminology, this status means the virtual server itself is administratively enabled, but it is unable to pass traffic becauseno 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/ltmfile 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 theauthoritative log filefor 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.logcontains general daemon messages but is not the primary source for chassis hardware alerts.
/var/log/kern.loglogs kernel-level events, not platform power status. /var/log/auditrecords 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:
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 thenodeis 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 statusspecificallyindicates anode (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 tore-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 acatch-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, thesource 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.