View all questions & answers for the BIG-IP Administration Data Plane Concepts (F5CAB2) exam


Question 9 Discussion

An organization needs to deploy an HTTP application on a BIG-IP system. The requirements specify hardware acceleration to enhance performance, while HTTP optimization features are not required. What type of virtual server and associated protocol profile should be used to meet these requirements? (Choose one answer)

  • A. Type: Stateless Protocol Profile: fastL4
  • B. Type: Standard Protocol Profile: tcp-wan-optimized
  • C. Type: Performance (Layer 4) Protocol Profile: fastL4
  • D. Type: Performance (HTTP) Protocol Profile: fasthttp
Correct Answer: D

Brave-Dump Clients Votes

C 100%

Comments



Drome 2026-01-06 17:13:57

Selected Answers: C


Cuando el requisito principal es hardware acceleration, BIG-IP debe operar en Layer 4.
  • Payton K 2026-01-21 02:34:18
    You answer would have been right if HTTP optimization were to be required but it is not required. That's why C is the most appropriate way to answer the question.


Anonymous User 2026-01-19 01:51:15

Selected Answers: C


The key requirements are:

HTTP application

Hardware acceleration for performance

HTTP optimization features are NOT required

This points directly to a Layer 4–only solution.

Why Performance (Layer 4) with fastL4 is correct

fastL4:

Uses hardware acceleration (ePVA / Fast Path) when available

Provides very high throughput and low latency

Does not inspect or optimize HTTP (no Layer 7 features)

Performance (Layer 4) virtual servers are specifically designed for this use case.


Anonymous User 2026-02-21 12:30:26

Selected Answers: C


C. Type: Performance (Layer 4) Protocol Profile: fastL4
The Performance (Layer 4) virtual server type uses the fastL4 profile, which leverages hardware acceleration (PVA - Packet Velocity ASIC) for high-performance throughput. Since HTTP optimization features are explicitly not required, there's no need for a Standard or Performance (HTTP) virtual server, which would add HTTP profile overhead. The fastL4 profile bypasses full proxy processing and passes traffic at the hardware level, perfectly matching the requirement for hardware acceleration without HTTP optimization.