Network Protocols Vocabulary
Understand key network protocol vocabulary: TCP vs. UDP trade-offs, HTTP/2 vs. HTTP/3 (QUIC), TLS handshake, WebSockets, and gRPC over HTTP/2.
0 / 30 completed
1 / 30
The primary trade-off between TCP and UDP is:
TCP's reliability mechanisms (SYN/SYN-ACK/ACK handshake, sequence numbers, acknowledgements, retransmission) add overhead. UDP skips all this — suitable for real-time applications (video calls, gaming, DNS) where speed matters more than guaranteed delivery.
2 / 30
HTTP/3 uses QUIC instead of TCP as its transport. The main benefit is:
HTTP/2 over TCP still suffers from head-of-line blocking at the TCP layer — a lost packet stalls all multiplexed streams. QUIC implements multiplexing at the transport level so each stream is independent. QUIC also combines the transport and TLS 1.3 handshake, reducing connection setup to 0-RTT or 1-RTT.
3 / 30
During a TLS handshake, the term 'cipher suite' refers to:
An example cipher suite: TLS_AES_256_GCM_SHA384 (TLS 1.3). It specifies: key exchange (ECDHE), authentication (RSA/ECDSA), bulk cipher (AES-256-GCM), and MAC (SHA-384). TLS 1.3 reduced the list to a few strong suites and removed weak algorithms like RC4 and 3DES.
4 / 30
WebSockets differ from standard HTTP requests in that:
After the WebSocket upgrade handshake (an HTTP Upgrade request), both client and server can send frames at any time. This enables real-time applications (chat, live dashboards, multiplayer games) without the overhead of repeated HTTP request-response cycles.
5 / 30
gRPC uses Protocol Buffers (protobuf) over HTTP/2. The advantage over REST/JSON is:
Protobuf binary payloads are typically 3-10x smaller than equivalent JSON. HTTP/2 multiplexing means thousands of concurrent RPC calls share one connection. The .proto IDL auto-generates type-safe clients in many languages, reducing integration errors compared to untyped REST.
6 / 30
Code Review Comment: "The server response time is consistently high when processing these API calls. Consider using a persistent connection to reduce overhead."Which network protocol concept does this comment primarily relate to?
This comment directly addresses the trade-off between TCP's connection establishment overhead and persistent connections. The core issue is minimizing latency, which is a key benefit of TCP's connection-oriented design when repeated requests are involved. Options A, C, and D represent different aspects of performance optimization, but don't capture this specific protocol concern.
7 / 30
Slack Message: "@john.doe - Just ran some diagnostics on the new microservice deployment. We're seeing a significant packet loss rate – around 8%. Looking into potential issues with UDP congestion control."What does 'packet loss rate' most directly relate to in the context of network protocols?
Packet loss rate is a critical metric when using UDP. Because UDP lacks built-in error correction and sequencing mechanisms, it's vulnerable to packet loss during transmission. The high rate indicates a problem with the network or protocol's ability to reliably deliver data – something that TCP handles via its reliable delivery guarantees.
8 / 30
PR Description: "Implemented gRPC for communication between the backend and frontend. Using Protocol Buffers (protobuf) to serialize messages for increased efficiency."Why is using Protocol Buffers with gRPC a benefit over simply using JSON?
The key advantage of Protocol Buffers (protobuf) over JSON lies in its binary encoding and schema definition. This results in significantly smaller message sizes due to the lack of text-based formatting and allows for faster serialization/deserialization, which is crucial for performance-sensitive applications like gRPC.
9 / 30
Standup Update: "I'm working on optimizing the data transfer between our database server and the API gateway. We're exploring using WebSockets for real-time updates."What is a primary reason why WebSockets are often preferred over traditional HTTP requests in scenarios like this?
The core benefit of WebSockets is their persistent, full-duplex communication. Unlike HTTP, which operates on a request/response model, WebSockets maintain an open connection allowing for continuous data flow in both directions without the overhead of repeatedly establishing and closing connections.
10 / 30
Code Review Comment: "The server is returning a 502 Bad Gateway error intermittently. We need to investigate potential issues with the upstream service's network connectivity."Which networking concept does this comment primarily focus on?
A 502 Bad Gateway error indicates that the server acting as a gateway (in this case, likely an API server) couldn't reach or process a request from another server. This directly relates to HTTP status codes and their specific meanings – particularly understanding what a 'Bad Gateway' error signifies in terms of network connectivity problems.
11 / 30
Code Review Comment: "The server response time is consistently high when processing these API calls. Consider using a persistent connection to reduce overhead."Which network protocol concept does this comment primarily relate to?
This comment directly addresses the trade-off between TCP's connection establishment overhead and persistent connections. The core issue is minimizing latency, which is a key benefit of TCP's connection-oriented design when repeated requests are involved. Options A, C, and D represent different aspects of performance optimization, but don't capture this specific protocol concern.
12 / 30
Slack Message: "@john.doe - Just ran some diagnostics on the new microservice deployment. We're seeing a significant packet loss rate – around 8%. Looking into potential issues with UDP congestion control."What does 'packet loss rate' most directly relate to in the context of network protocols?
Packet loss rate is a critical metric when using UDP. Because UDP lacks built-in error correction and sequencing mechanisms, it's vulnerable to packet loss during transmission. The high rate indicates a problem with the network or protocol's ability to reliably deliver data – something that TCP handles via its reliable delivery guarantees.
13 / 30
PR Description: "Implemented gRPC for communication between the backend and frontend. Using Protocol Buffers (protobuf) to serialize messages for increased efficiency."Why is using Protocol Buffers with gRPC a benefit over simply using JSON?
The key advantage of Protocol Buffers (protobuf) over JSON lies in its binary encoding and schema definition. This results in significantly smaller message sizes due to the lack of text-based formatting and allows for faster serialization/deserialization, which is crucial for performance-sensitive applications like gRPC.
14 / 30
Standup Update: "I'm working on optimizing the data transfer between our database server and the API gateway. We're exploring using WebSockets for real-time updates."What is a primary reason why WebSockets are often preferred over traditional HTTP requests in scenarios like this?
The core benefit of WebSockets is their persistent, full-duplex communication. Unlike HTTP, which operates on a request/response model, WebSockets maintain an open connection allowing for continuous data flow in both directions without the overhead of repeatedly establishing and closing connections.
15 / 30
Code Review Comment: "The server is returning a 502 Bad Gateway error intermittently. We need to investigate potential issues with the upstream service's network connectivity."Which networking concept does this comment primarily focus on?
A 502 Bad Gateway error indicates that the server acting as a gateway (in this case, likely an API server) couldn't reach or process a request from another server. This directly relates to HTTP status codes and their specific meanings – particularly understanding what a 'Bad Gateway' error signifies in terms of network connectivity problems.
16 / 30
Code Review Comment: "The server response time is consistently high when processing these API calls. Consider using a persistent connection to reduce overhead."Which network protocol concept does this comment primarily relate to?
This comment directly addresses the trade-off between TCP's connection establishment overhead and persistent connections. The core issue is minimizing latency, which is a key benefit of TCP's connection-oriented design when repeated requests are involved. Options A, C, and D represent different aspects of performance optimization, but don't capture this specific protocol concern.
17 / 30
Slack Message: "@john.doe - Just ran some diagnostics on the new microservice deployment. We're seeing a significant packet loss rate – around 8%. Looking into potential issues with UDP congestion control."What does 'packet loss rate' most directly relate to in the context of network protocols?
Packet loss rate is a critical metric when using UDP. Because UDP lacks built-in error correction and sequencing mechanisms, it's vulnerable to packet loss during transmission. The high rate indicates a problem with the network or protocol's ability to reliably deliver data – something that TCP handles via its reliable delivery guarantees.
18 / 30
PR Description: "Implemented gRPC for communication between the backend and frontend. Using Protocol Buffers (protobuf) to serialize messages for increased efficiency."Why is using Protocol Buffers with gRPC a benefit over simply using JSON?
The key advantage of Protocol Buffers (protobuf) over JSON lies in its binary encoding and schema definition. This results in significantly smaller message sizes due to the lack of text-based formatting and allows for faster serialization/deserialization, which is crucial for performance-sensitive applications like gRPC.
19 / 30
Standup Update: "I'm working on optimizing the data transfer between our database server and the API gateway. We're exploring using WebSockets for real-time updates."What is a primary reason why WebSockets are often preferred over traditional HTTP requests in scenarios like this?
The core benefit of WebSockets is their persistent, full-duplex communication. Unlike HTTP, which operates on a request/response model, WebSockets maintain an open connection allowing for continuous data flow in both directions without the overhead of repeatedly establishing and closing connections.
20 / 30
Code Review Comment: "The server is returning a 502 Bad Gateway error intermittently. We need to investigate potential issues with the upstream service's network connectivity."Which networking concept does this comment primarily focus on?
A 502 Bad Gateway error indicates that the server acting as a gateway (in this case, likely an API server) couldn't reach or process a request from another server. This directly relates to HTTP status codes and their specific meanings – particularly understanding what a 'Bad Gateway' error signifies in terms of network connectivity problems.
21 / 30
Code Review Comment: "The server response time is consistently high when processing these API calls. Consider using a persistent connection to reduce overhead."Which network protocol concept does this comment primarily relate to?
This comment directly addresses the trade-off between TCP's connection establishment overhead and persistent connections. The core issue is minimizing latency, which is a key benefit of TCP's connection-oriented design when repeated requests are involved. Options A, C, and D represent different aspects of performance optimization, but don't capture this specific protocol concern.
22 / 30
Slack Message: "@john.doe - Just ran some diagnostics on the new microservice deployment. We're seeing a significant packet loss rate – around 8%. Looking into potential issues with UDP congestion control."What does 'packet loss rate' most directly relate to in the context of network protocols?
Packet loss rate is a critical metric when using UDP. Because UDP lacks built-in error correction and sequencing mechanisms, it's vulnerable to packet loss during transmission. The high rate indicates a problem with the network or protocol's ability to reliably deliver data – something that TCP handles via its reliable delivery guarantees.
23 / 30
PR Description: "Implemented gRPC for communication between the backend and frontend. Using Protocol Buffers (protobuf) to serialize messages for increased efficiency."Why is using Protocol Buffers with gRPC a benefit over simply using JSON?
The key advantage of Protocol Buffers (protobuf) over JSON lies in its binary encoding and schema definition. This results in significantly smaller message sizes due to the lack of text-based formatting and allows for faster serialization/deserialization, which is crucial for performance-sensitive applications like gRPC.
24 / 30
Standup Update: "I'm working on optimizing the data transfer between our database server and the API gateway. We're exploring using WebSockets for real-time updates."What is a primary reason why WebSockets are often preferred over traditional HTTP requests in scenarios like this?
The core benefit of WebSockets is their persistent, full-duplex communication. Unlike HTTP, which operates on a request/response model, WebSockets maintain an open connection allowing for continuous data flow in both directions without the overhead of repeatedly establishing and closing connections.
25 / 30
Code Review Comment: "The server is returning a 502 Bad Gateway error intermittently. We need to investigate potential issues with the upstream service's network connectivity."Which networking concept does this comment primarily focus on?
A 502 Bad Gateway error indicates that the server acting as a gateway (in this case, likely an API server) couldn't reach or process a request from another server. This directly relates to HTTP status codes and their specific meanings – particularly understanding what a 'Bad Gateway' error signifies in terms of network connectivity problems.
26 / 30
Code Review Comment: "The server response time is consistently high when processing these API calls. Consider using a persistent connection to reduce overhead."Which network protocol concept does this comment primarily relate to?
This comment directly addresses the trade-off between TCP's connection establishment overhead and persistent connections. The core issue is minimizing latency, which is a key benefit of TCP's connection-oriented design when repeated requests are involved. Options A, C, and D represent different aspects of performance optimization, but don't capture this specific protocol concern.
27 / 30
Slack Message: "@john.doe - Just ran some diagnostics on the new microservice deployment. We're seeing a significant packet loss rate – around 8%. Looking into potential issues with UDP congestion control."What does 'packet loss rate' most directly relate to in the context of network protocols?
Packet loss rate is a critical metric when using UDP. Because UDP lacks built-in error correction and sequencing mechanisms, it's vulnerable to packet loss during transmission. The high rate indicates a problem with the network or protocol's ability to reliably deliver data – something that TCP handles via its reliable delivery guarantees.
28 / 30
PR Description: "Implemented gRPC for communication between the backend and frontend. Using Protocol Buffers (protobuf) to serialize messages for increased efficiency."Why is using Protocol Buffers with gRPC a benefit over simply using JSON?
The key advantage of Protocol Buffers (protobuf) over JSON lies in its binary encoding and schema definition. This results in significantly smaller message sizes due to the lack of text-based formatting and allows for faster serialization/deserialization, which is crucial for performance-sensitive applications like gRPC.
29 / 30
Standup Update: "I'm working on optimizing the data transfer between our database server and the API gateway. We're exploring using WebSockets for real-time updates."What is a primary reason why WebSockets are often preferred over traditional HTTP requests in scenarios like this?
The core benefit of WebSockets is their persistent, full-duplex communication. Unlike HTTP, which operates on a request/response model, WebSockets maintain an open connection allowing for continuous data flow in both directions without the overhead of repeatedly establishing and closing connections.
30 / 30
Code Review Comment: "The server is returning a 502 Bad Gateway error intermittently. We need to investigate potential issues with the upstream service's network connectivity."Which networking concept does this comment primarily focus on?
A 502 Bad Gateway error indicates that the server acting as a gateway (in this case, likely an API server) couldn't reach or process a request from another server. This directly relates to HTTP status codes and their specific meanings – particularly understanding what a 'Bad Gateway' error signifies in terms of network connectivity problems.
Frequently Asked Questions
What does the "Network Protocols Vocabulary" exercise cover?
Understand key network protocol vocabulary: TCP vs. UDP trade-offs, HTTP/2 vs. HTTP/3 (QUIC), TLS handshake, WebSockets, and gRPC over HTTP/2.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Network Protocols Vocabulary"?
This exercise has 30 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Networking Language exercises?
Browse the full Networking Language hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.