200-901 Network Fundamentals Practice Question
A network engineer configures an HTTP/2 server. Which feature of HTTP/2 reduces overhead by compressing headers using HPACK?
⚠ Common exam trap
Cisco often tests the distinction between features that improve performance (multiplexing, server push) versus the specific mechanism for header compression (HPACK), leading candidates to confuse multiplexing or binary framing with compression.
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
✓
HPACK
HPACK is the header compression mechanism specified for HTTP/2 (RFC 7541). It reduces overhead by encoding HTTP headers into a compact binary format using static and dynamic tables, eliminating redundant header data across requests. This directly addresses the question's focus on reducing overhead through header compression.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Server push
Why it's wrong here
Server push lets the server send resources before the client requests them, reducing round trips, but it performs no header compression. It would be the correct choice if the question asked how HTTP/2 proactively delivers assets the client will soon need.
- ✗
Binary framing layer
Why it's wrong here
Binary framing splits messages into frames but performs no header compression itself; HPACK is a separate mechanism. It is tempting because framing underpins HTTP/2's wire format, and would be the answer if the question asked how HTTP/2 structures data into typed frames for multiplexing.
- ✓
HPACK
Why this is correct
HPACK is the header compression scheme defined specifically for HTTP/2, encoding header fields into a compact indexed format and eliminating redundant transfers across streams. This directly satisfies the stem's requirement to reduce overhead by compressing headers, unlike HTTP/1.1's uncompressed plaintext headers.
- ✗
Multiplexed streams
Why it's wrong here
Multiplexed streams let many requests share one TCP connection concurrently, eliminating head-of-line blocking at the application layer, but they do not compress headers. It would be correct if the question asked how HTTP/2 avoids opening multiple connections per origin.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.