5V0-43.21 · Question #1
Which built-in application profile is a valid option for a Virtual Service?
The correct answer is B. System-Fast-Path. System-Fast-Path (B) is a valid built-in application profile for a Virtual Service because it defines a legitimate traffic-handling mode - fast path processing - that allows the system to forward traffic with reduced overhead, bypassing full proxy inspection for…
Question
Which built-in application profile is a valid option for a Virtual Service?
Options
- ASystem-DTLS
- BSystem-Fast-Path
- CSystem-ICMP
- DSystem-DNS
How the community answered
(39 responses)- A5% (2)
- B90% (35)
- C3% (1)
- D3% (1)
Explanation
System-Fast-Path (B) is a valid built-in application profile for a Virtual Service because it defines a legitimate traffic-handling mode - fast path processing - that allows the system to forward traffic with reduced overhead, bypassing full proxy inspection for performance-sensitive flows.
The distractors are wrong for the following reasons: System-DTLS (A) refers to Datagram TLS, a transport-layer security protocol for UDP - it is not a recognized built-in application profile in this context. System-ICMP (C) is a network-layer diagnostic protocol (used for ping/traceroute) and does not function as an application profile you'd assign to a Virtual Service. System-DNS (D) may sound plausible since DNS is an application-layer protocol, but it is not a valid built-in profile option for a Virtual Service in this product's profile library.
Memory tip: Think "Fast-Path = Fast traffic" - among the options, only Fast-Path describes a processing behavior appropriate for a Virtual Service profile. The others name protocols (DTLS, ICMP, DNS) rather than a service-handling mode, which is a quick way to rule them out on the exam.
Topics
Community Discussion
No community discussion yet for this question.