200-901 Network Fundamentals Practice Question
An HTTP/2 connection uses multiple concurrent streams over a single TCP connection. Which feature of HTTP/2 enables this?
⚠ Common exam trap
Cisco often tests the distinction between the enabling mechanism (binary framing) and the resulting capability (multiplexing), so candidates mistakenly choose 'binary framing layer' because it sounds technical, but it is the foundation, not the feature that directly enables concurrency.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Multiplexing
Multiplexing is the HTTP/2 feature that allows multiple concurrent streams to share a single TCP connection. This eliminates head-of-line blocking at the application layer by enabling the interleaving of frames from different streams, so a slow response on one stream does not block others.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Binary framing layer
Why it's wrong here
Binary framing splits messages into frames tagged with a stream identifier, but that identifier alone does not multiplex; it merely provides the envelope. Multiplexing arises from interleaving those frames across streams. The framing layer is genuinely required for HTTP/2's wire format, so it looks like the enabler, yet the stem asks what permits concurrency.
- ✓
Multiplexing
Why this is correct
Multiplexing allows multiple request/response streams to be interleaved concurrently over one TCP connection, each identified by a stream ID. This removes HTTP/1.1's head-of-line blocking at the connection level and is the specific HTTP/2 feature enabling concurrent streams.
- ✗
Server push
Why it's wrong here
Server push lets the server send resources the client has not requested; it does not create concurrent streams. It is tempting because it is an HTTP/2 multiplexing-related feature, but multiplexing itself, achieved through binary framing that interleaves independent stream frames on one TCP connection, is what enables concurrency.
- ✗
Header compression (HPACK)
Why it's wrong here
HPACK compresses header fields to cut overhead on repeated requests; it operates on header blocks, not on stream scheduling. Concurrent streams are carried by frames tagged with stream identifiers, which HPACK does not create. HPACK would be the answer if the question asked how HTTP/2 reduces per-request header bytes.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 975 original 200-901 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.