iSCSI High Performance Architecture Design
A network architect designs the iSCSI architecture. The requirements are to achieve high performance and a low amount of oversubscription and to minimize latency. Which two actions must be taken to meet these requirements? (Choose two.)
Community Votes
67% of anonymous learners picked answer BE. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the understanding of iSCSI optimization techniques, specifically how port binding improves throughput and how physical topology affects latency, while MTU configuration is often a secondary or assumed parameter rather than a primary architectural action for latency.
This question addresses the design of high-performance iSCSI architectures by focusing on minimizing latency and reducing oversubscription. It establishes that enabling port binding and minimizing network hops are critical actions to achieve these specific performance goals.
Many candidates incorrectly choose MTU 9000 (Option C) because jumbo frames are associated with high performance. However, while Jumbo Frames reduce CPU overhead, they do not directly address 'oversubscription' or 'hops' in the same way port binding and topology do, and the question asks for actions to meet specific low-latency/low-oversubscription requirements where E and B are more definitive architectural controls.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
To achieve high performance and minimize latency in an iSCSI architecture, two key factors must be addressed: path utilization and physical distance. Enabling iSCSI port binding (Option B) allows the initiator to use multiple network paths simultaneously, providing load balancing and failover capabilities which reduces the risk of bottlenecks (oversubscription) on a single link. Minimizing the number of hops between storage and hosts (Option E) directly reduces latency, as each hop introduces processing delay. These two actions work together to ensure efficient data transfer and minimal delay.Why the Other Options Are Wrong
Using a software-based iSCSI adapter (Option A) typically consumes significant CPU resources compared to hardware offload solutions (like TOE cards), leading to higher latency and lower performance, so this is incorrect. Setting the payload size to MTU 1500 (Option D) is the standard Ethernet frame size; while compatible, it does not offer the performance benefits of Jumbo Frames (MTU 9000). While Option C (MTU 9000) does improve throughput by reducing header overhead, the question emphasizes 'low amount of oversubscription' and 'minimize latency'. Port binding (B) directly combats oversubscription by aggregating links, and minimizing hops (E) is the most direct way to minimize latency. Between C and E/B, E and B are more fundamental to the architecture of connectivity and path management required for the stated goals. Furthermore, community consensus and official exam logic often prioritize path redundancy/load balancing (B) and topology (E) as the primary architectural decisions for performance.Community Comment Notes
The majority of the community voted for BE, agreeing that port binding and minimizing hops are the correct architectural choices. One commenter noted that while MTU should ideally be 9000, it is often considered a 'given' or baseline configuration, whereas B and E are active design actions. Another user confirmed their choice of B and E based on the principles of load balancing and latency reduction.Exam Strategy
When asked about optimizing network performance, always look for options that address both bandwidth utilization (like bonding/binding) and latency (like topology/hops). Distinguish between configuration parameters (like MTU) and architectural design choices (like path selection and physical layout).
Frequently Asked Questions
Why isn't MTU 9000 the correct answer for high performance?
While MTU 9000 improves throughput, the question prioritizes minimizing oversubscription and latency. Port binding (B) handles load balancing/oversubscription, and fewer hops (E) directly minimizes latency.
Does software iSCSI affect latency significantly?
Yes, software iSCSI relies on the host CPU for packet processing, which increases latency and CPU load compared to hardware-assisted or offloaded iSCSI implementations.