お手軽に合格させる 最新F5 F5CAB3問題集には84問があります
最新のF5CAB3学習ガイド2026年最新の- 提供するのはテストエンジンとPDF
F5 F5CAB3 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
質問 # 18
Which persistence profile would be the most appropriate to ensure an HTTP web request connects to the same pool member? (Choose one answer)
- A. Cookie persistence
- B. Destination address
- C. Hash persistence
- D. SSL persistence
正解：A
解説：
For HTTP-based applications, cookie persistence is the most appropriate and commonly recommended persistence method.
According to the BIG-IP Administration: Data Plane Configuration documentation:
* Cookie persistence inserts or uses an HTTP cookie to maintain session affinity.
* It operates at Layer 7 (HTTP) and is application-aware.
* It allows persistence to be maintained even when multiple clients are behind a NAT device.
Why the other options are incorrect:
* A. Destination addressDestination address persistence is generally used for inbound traffic patterns such as firewall or proxy scenarios.
* B. Hash persistenceHash persistence is less granular and not HTTP-specific.
* C. SSL persistenceSSL persistence is typically used when SSL session IDs are reused and is less reliable than cookies for HTTP applications.
Correct Resolution:
Using cookie persistence ensures that HTTP web requests are consistently directed to the same pool member.
質問 # 19
A BIG-IP Administrator creates a new VLAN on BIG-IP Cluster Member A and attaches an interface to it.
Although the Auto Config Sync is in place, the new VLAN does NOT show up on Cluster Member B. What should the BIG-IP Administrator do to ensure the new VLAN is configured on each Cluster Member?
- A. Enable the Interface that is attached to the new VLAN on Cluster Member A
- B. Configure the new VLAN manually on Cluster Member B
- C. Configure a Default Route for the new VLAN on Cluster Member A
- D. Reset the Device Trust of the BIG-IP Cluster on either Cluster Member
正解：B
解説：
In a BIG-IP High Availability (HA) environment, most configuration objects (Virtual Servers, Pools, iRules) are considered "shared" and are synchronized automatically between devices. However, network-level objects-specifically VLANs and Self IPs-are unique to the hardware and are generally not synchronized by the ConfigSync process.
This is intentional because two devices in a cluster may have different physical cabling or interface assignments. For example, Cluster Member A might use interface 1.1 for a specific VLAN, while Cluster Member B might use interface 1.2. Because the BIG-IP system cannot assume that the physical network topology is identical for both appliances, the administrator must Configure the new VLAN manually on Cluster Member B.
Once the VLAN is created manually on both devices with the exact same name, it can then be used to host
"shared" floating Self IP addresses or traffic groups that will synchronize. Failing to create the VLAN on the peer device will prevent the traffic group from failing over correctly, as the peer will not have the necessary Layer 2 broadcast domain defined to take over the traffic. Resetting Device Trust (Option D) is a drastic step for fix sync communication issues but will not change the fact that VLANs are non-syncable objects.
Enabling the interface (Option B) only affects the link status of Member A and has no impact on the configuration of Member B.
質問 # 20
A BIG-IP Administrator creates a new VLAN on BIG-IP Cluster Member A and attaches an interface to it.
Although the Auto Config Sync is in place, the new VLAN does NOT show up on Cluster Member B. What should the BIG-IP Administrator do to ensure the new VLAN is configured on each Cluster Member?
- A. Enable the Interface that is attached to the new VLAN on Cluster Member A
- B. Configure the new VLAN manually on Cluster Member B
- C. Configure a Default Route for the new VLAN on Cluster Member A
- D. Reset the Device Trust of the BIG-IP Cluster on either Cluster Member
正解：B
質問 # 21
Refer to the exhibit.
DNS queries from two internal DNS servers are being load-balanced to external DNS servers via a virtual server on a BIG-IP device. The DNS queries originate from:
192.168.10.100
192.168.10.200
and target:
192.168.2.150
All DNS queries destined for the external DNS servers fail.
Which property change should the BIG-IP Administrator make in the Virtual Server to resolve this issue?
(Choose one answer)
- A. Protocol to UDP
- B. Protocol profile (Client) to DNS_OPTIMIZED
- C. Source Address to 192.168.10.0/24
- D. Type to Performance (HTTP)
正解：A
解説：
DNS traffic is primarily transported using UDP port 53. In the exhibit, the Virtual Server is configured with the Protocol set to TCP, which prevents standard DNS queries from being processed correctly. BIG-IP Virtual Servers must be configured with the correct Layer 4 protocol to match the application traffic they are handling.
According to the BIG-IP Administration: Data Plane Configuration documentation:
The Protocol setting on a Virtual Server defines whether traffic is processed as TCP, UDP, or another supported transport protocol.
Standard DNS queries and responses use UDP, while TCP is only required for DNS zone transfers (AXFR) or exceptionally large responses.
When a DNS Virtual Server is incorrectly configured with TCP, UDP-based DNS queries are dropped, causing all requests to fail.
Why the other options are incorrect:
A). Protocol profile (Client) to DNS_OPTIMIZEDA DNS profile enhances DNS functionality but does not correct an incorrect transport protocol configuration.
B). Type to Performance (HTTP)Performance (HTTP) Virtual Servers are designed for HTTP traffic and are not suitable for DNS services.
C). Source Address to 192.168.10.0/24The existing source IPs already fall within the allowed range, so this setting does not address the failure.
Correct Resolution:
Changing the Protocol to UDP aligns the Virtual Server with standard DNS transport requirements, allowing DNS queries to be successfully processed and load-balanced.
質問 # 22
A Standard Virtual Server reports poor performance for Internet users.
What TCP profile configuration should be applied?
- A. Client: f5-tcp-optimized
- B. Client: f5-tcp-wan / Server: f5-tcp-lan
- C. Client: f5-tcp-lan
- D. Client: f5-tcp-lan / Server: f5-tcp-wan
正解：B
解説：
WAN-optimized TCP profiles improve performance for high-latency Internet clients, while LAN profiles are optimal for backend servers.
質問 # 23
A virtual server is configured to offload SSL from a pool of backend servers. When users connect to the virtual server, they successfully establish an SSL connection but no content is displayed. A packet trace performed on the server shows that the server receives and responds to the request. What should a BIG-IP Administrator do to resolve the problem?
- A. enable SNAT
- B. disable Server SSL profile
- C. enable Server SSL profile
- D. disable SNAT
正解：A
解説：
This scenario describes a classic routing issue often encountered during SSL offload deployments. The fact that an SSL connection is established indicates the Client SSL profile is working correctly. The packet trace showing the server "receives and responds" to the request is the most critical diagnostic clue.
When a BIG-IP receives traffic, it typically passes the client's original source IP address to the backend server. If the backend server's default gateway is not the BIG-IP (a common "one-arm" network topology), the server will attempt to send its response directly back to the client's IP via its own default router. The client's browser will reject this response because it expects traffic to come from the Virtual Server's IP, not the backend server's IP.
To resolve this, the administrator must enable SNAT (Source Address Translation), typically using SNAT Automap. When SNAT is enabled, the BIG-IP replaces the client's original source IP with one of its own Self IPs before forwarding the request to the server. Because the source of the packet is now the BIG-IP, the backend server is forced to send its response back to the BIG-IP. The BIG-IP then receives the response, translates it back, and delivers the content to the user. Option A is unnecessary if the servers are expecting plain-text traffic after the BIG-IP performs offload. Option D would only worsen the existing routing discrepancy.
質問 # 24
A BIG-IP Administrator uses backend servers to host multiple services per server. There are multiple virtual servers and pools defined, referencing the same backend servers.
Which load balancing algorithm is most appropriate to have an equal number of connections on each backend server? (Choose one answer)
- A. Predictive (node)
- B. Predictive (member)
- C. Least Connections (node)
- D. Least Connections (member)
正解：C
解説：
In this scenario, each backend node (server) hosts multiple services and is referenced by multiple pools and virtual servers. The goal is to ensure an equal number of total connections per backend server, regardless of how many pool members (services/ports) exist on that server.
According to the BIG-IP Administration: Data Plane Configuration documentation:
Least Connections (node) tracks the total number of active connections to a node across all pool members and services.
This algorithm ensures load distribution is balanced at the server level, not just at the individual service (member) level.
It is specifically recommended when:
Multiple pool members exist on the same backend server
Multiple virtual servers reference the same backend servers
Why the other options are incorrect:
B . Predictive (member)
Predictive algorithms are advanced and traffic-pattern based, but they operate at the member level and do not guarantee equal connections per server.
C . Least Connections (member)
This balances connections per pool member, which can overload a server hosting multiple members while still appearing "balanced" per member.
D . Predictive (node)
Although node-aware, predictive algorithms are less deterministic and not the best choice when strict equality of connections is required.
Correct Resolution:
Using Least Connections (node) ensures that each backend server carries an equal connection load across all services and pools.
質問 # 25
A BIG-IP Administrator finds the following log entry after a report of user issues connecting to a virtual server:
01010201: Intercept exhaustion on 10.70.110.112 to 192.28.123.250:80 (proto 6) How should the BIG-IP Administrator modify the SNAT pool that is associated with the virtual server?
(Choose one answer)
- A. Remove an IP address from the SNAT pool
- B. Increase the timeout of the SNAT addresses
- C. Add an IP address to the SNAT pool
- D. Remove the SNAT pool and apply SNAT Automap
正解：C
解説：
The log message "Intercept exhaustion" indicates that the BIG-IP system has exhausted the available source port translations for one or more SNAT addresses. This occurs when too many concurrent client connections are being translated through a limited number of SNAT IP addresses, and all ephemeral source ports (typically ~64,000 per SNAT IP) are in use.
According to the BIG-IP Administration: Data Plane Configuration documentation:
Each SNAT IP address provides a finite number of available source ports.
When the number of concurrent connections exceeds the available port space, the BIG-IP logs an Intercept exhaustion error and new connections fail.
The recommended resolution is to increase the available SNAT resources by adding additional IP addresses to the SNAT pool.
Why the other options are incorrect:
A). Increase the timeout of the SNAT addressesIncreasing timeouts may actually worsen the problem by keeping ports allocated longer, accelerating port exhaustion.
B). Remove the SNAT pool and apply SNAT AutomapSNAT Automap uses the Self IP addresses on the egress VLAN, which may not provide additional capacity and can introduce routing or design issues. This is not a direct or recommended fix for SNAT exhaustion.
C). Remove an IP address from the SNAT poolThis would reduce the number of available source ports and further exacerbate the intercept exhaustion condition.
Correct Resolution:
By adding an IP address to the SNAT pool, the BIG-IP increases the total number of available source ports, alleviating intercept exhaustion and restoring successful client connections.
質問 # 26
The BIG-IP Administrator has to provide encrypted communication between users and the virtual server they access. Multiple hostnames are configured in DNS with the same IP address.
Which profile type and setting in the profile should be used? (Choose one answer)
- A. Server SSL, Client Name
- B. Client SSL, Server Name
- C. Client SSL, Client Name
- D. Server SSL, Server Name
正解：B
解説：
When multiple hostnames resolve to the same IP address and encrypted communication is required, the BIG- IP must be able to present the correct SSL certificate based on the hostname requested by the client. This is accomplished using Server Name Indication (SNI).
According to BIG-IP Administration: Data Plane Configuration documentation:
* SNI is a client-side TLS extension, where the client includes the requested hostname during the SSL handshake.
* BIG-IP evaluates this hostname using the Client SSL profile, not the Server SSL profile.
* The "Server Name" setting in the Client SSL profile enables BIG-IP to select the appropriate SSL certificate for the requested hostname.
Why option C is correct:
* Client SSL profile handles inbound (client-side) encryption.
* Server Name enables SNI-based certificate selection when multiple DNS names share the same virtual server IP.
Why the other options are incorrect:
* A. Client SSL, Client NameThere is no Client SSL setting called Client Name for SNI certificate selection.
* B. Server SSL, Server NameServer SSL is used for encryption between BIG-IP and backend servers, not for client-side hostname identification.
* D. Server SSL, Client NameServer SSL does not process client-requested hostnames during TLS negotiation.
Correct Resolution:
Configure a Client SSL profile and enable the Server Name (SNI) setting to support multiple encrypted hostnames on the same virtual server IP.
質問 # 27
Refer to the exhibit.
A BIG-IP Administrator needs to configure health monitors for a newly configured server pool named Pool_B. Which health monitor settings will ensure that all pool members will be accurately marked as available or unavailable?
- A. HTTPS, HTTP, FTP, and SSH with the Availability Requirement of all health monitors
- B. HTTPS, HTTP, FTP, and ICMP, with the Availability Requirement of all health monitors
- C. HTTPS and HTTP with the Availability Requirement of at least one health monitor
- D. HTTPS, HTTP, FTP, and SSH, with the Availability Requirement of at least one monitor
正解：D
解説：
The pool member list in the exhibit shows servers listening on four distinct service ports: 80 (HTTP), 21 (FTP), 443 (HTTPS), and 22 (SSH). To accurately monitor a pool where members provide different services, the administrator must apply monitors that correspond to each of those specific services.
The key to this configuration is the Availability Requirement (also known as "Monitor Rule"). If the administrator sets the requirement to "All health monitors," every single monitor (HTTP, HTTPS, FTP, and SSH) must pass for a member to be marked "Up." This would cause an immediate failure: for example, a server listening only on port 80 would fail the HTTPS, FTP, and SSH checks, resulting in the member being marked "Down" even if the HTTP service is healthy.
To ensure accuracy, the administrator should apply all four relevant monitors and set the Availability Requirement to at least one monitor. With this setting, the BIG-IP marks a member as "Up" if any of the assigned monitors return a successful response. Therefore, the member at 10.200.50.210:80 will stay "Up" as long as the HTTP monitor passes, even though it fails the FTP, HTTPS, and SSH monitors. This configuration allows a single pool to contain diverse service types while ensuring that the specific port defined for each member is verified correctly. Option C is incorrect because ICMP only checks if the IP is alive, not if the specific service port is functioning.
質問 # 28
An organization reports slow performance accessing an Intranet website. All employees use a single proxy IP.
What should the BIG-IP Administrator do?
- A. Change Fallback Persistence to source_addr
- B. Change Default Persistence to cookie
- C. Change Source Address to proxy IP
- D. Change Load Balancing to Least Connections
正解：B
解説：
When many users share one source IP, source-address persistence fails. Cookie persistence uniquely identifies clients at Layer 7.
質問 # 29
A BIG-IP Administrator adds new pool members to a highly utilized pool. The application begins failing.
What pool-level setting should be checked?
- A. Slow Ramp Time
- B. Availability Requirement
- C. Action On Service Down
- D. Allow SNAT
正解：A
解説：
Slow Ramp Time prevents new members from being overwhelmed immediately after activation.
質問 # 30
Refer to the exhibit.
DNS queries from two internal DNS servers are being load-balanced to external DNS servers via a virtual server on a BIG-IP device. The DNS queries originate from:
192.168.10.100
192.168.10.200
and target:
192.168.2.150
All DNS queries destined for the external DNS servers fail.
Which property change should the BIG-IP Administrator make in the Virtual Server to resolve this issue?
(Choose one answer)
- A. Protocol to UDP
- B. Protocol profile (Client) to DNS_OPTIMIZED
- C. Source Address to 192.168.10.0/24
- D. Type to Performance (HTTP)
正解：A
解説：
DNS traffic is primarily transported using UDP port 53. In the exhibit, the Virtual Server is configured with the Protocol set to TCP, which prevents standard DNS queries from being processed correctly. BIG-IP Virtual Servers must be configured with the correct Layer 4 protocol to match the application traffic they are handling.
According to the BIG-IP Administration: Data Plane Configuration documentation:
* The Protocol setting on a Virtual Server defines whether traffic is processed as TCP, UDP, or another supported transport protocol.
* Standard DNS queries and responses use UDP, while TCP is only required for DNS zone transfers (AXFR) or exceptionally large responses.
* When a DNS Virtual Server is incorrectly configured with TCP, UDP-based DNS queries are dropped, causing all requests to fail.
Why the other options are incorrect:
* A. Protocol profile (Client) to DNS_OPTIMIZEDA DNS profile enhances DNS functionality but does not correct an incorrect transport protocol configuration.
* B. Type to Performance (HTTP)Performance (HTTP) Virtual Servers are designed for HTTP traffic and are not suitable for DNS services.
* C. Source Address to 192.168.10.0/24The existing source IPs already fall within the allowed range, so this setting does not address the failure.
Correct Resolution:
Changing the Protocol to UDP aligns the Virtual Server with standard DNS transport requirements, allowing DNS queries to be successfully processed and load-balanced.
質問 # 31
DNS queries from internal DNS servers fail when sent through a BIG-IP Virtual Server.
Which Virtual Server property should be changed?
- A. Protocol to UDP
- B. Source Address to subnet
- C. Protocol Profile (Client) to DNS_OPTIMIZED
- D. Type to Performance (HTTP)
正解：A
解説：
Standard DNS queries use UDP. Configuring the Virtual Server for TCP causes DNS traffic to fail.
質問 # 32
The BIG-IP Administrator needs to load balance a pool of web servers. Load balancing should consider the number of connections that are active on that pool member.
Which load balancing method meets this requirement? (Choose one answer)
- A. Least Connections (member)
- B. Ratio (node)
- C. Round Robin
- D. Ratio (member)
正解：A
解説：
The requirement states that load balancing decisions must be based on the number of active connections on each pool member. This directly maps to the Least Connections (member) load balancing method.
According to the BIG-IP Administration: Data Plane Configuration documentation:
* Least Connections (member) selects the pool member with the fewest active connections at the time of the request.
* This method dynamically adapts to real-time traffic patterns and ensures that more heavily loaded pool members receive fewer new connections.
* It is especially effective for web servers where connection duration may vary and equal distribution of active sessions is desired.
Why the other options are incorrect:
* B. Round RobinDistributes connections sequentially without considering current load or active connections.
* C. Ratio (member)Distributes traffic based on static ratios, not real-time connection counts.
* D. Ratio (node)Uses predefined ratios at the node level and does not account for active connection counts.
Correct Resolution:
Using Least Connections (member) ensures that new connections are directed to the pool member currently handling the fewest active connections, meeting the stated requirement.
質問 # 33
......
F5CAB3問題集と試験テストエンジン：https://www.jpntest.com/shiken/F5CAB3-mondaishu
最新版を今すぐ試そうF5CAB3練習テスト問題解答：https://drive.google.com/open?id=1lhOghTenikJfbe1OzaseoJAEzQi1vH9B