Learn container networking vocabulary: bridge network, host networking, ClusterIP, DNS between containers, port mapping, network namespaces — the language of professional container networking discussions.
0 / 22 completed
1 / 22
The engineer says: 'The container is on the bridge network.' What is Docker's bridge network?
The bridge network is Docker's default network driver. When containers are started without specifying a network, they are attached to the default bridge network (docker0). Containers on the same bridge network can communicate with each other using their IP addresses. The bridge is isolated from the host network; outbound traffic goes through NAT. Custom bridge networks also support DNS-based container discovery by container name.
2 / 22
The developer says: 'We use host networking for this container because it needs direct access to the host's network interfaces.' What is host networking?
In host networking mode (--network=host in Docker), the container shares the host machine's network namespace. The container uses the host's IP address and can bind to host ports directly, with no NAT. This maximises network performance and allows access to host network interfaces, but it eliminates network isolation between the container and the host. It is used for performance-sensitive applications or those requiring raw socket access.
3 / 22
The Kubernetes engineer explains: 'The service is accessed via the ClusterIP.' What is a ClusterIP?
ClusterIP is the default Kubernetes Service type. It assigns a virtual IP address that is only reachable from within the cluster. Other pods access the service using this stable virtual IP (or the DNS name) rather than connecting directly to pod IPs (which change as pods are rescheduled). ClusterIP is used for internal service-to-service communication where no external access is needed.
4 / 22
The developer asks: 'How does DNS resolution between containers work in Docker Compose?' What is the answer?
In Docker Compose, when services are on the same user-defined network (which Compose creates by default), Docker's embedded DNS server resolves container names. Each service can reach another by its service name as a hostname (e.g., a web service can connect to 'db:5432'). This name-based resolution is more reliable than IP addresses, which can change between container restarts.
5 / 22
The container configuration shows: 'ports: - 8080:80'. What does this port mapping mean?
Port mapping (or port publishing) connects a port on the host machine to a port inside the container. The format is HOST_PORT:CONTAINER_PORT. '8080:80' means traffic arriving at port 8080 on the host is forwarded to port 80 inside the container. The container's application listens on port 80; external clients connect to port 8080 on the host. Without port mapping, the container's ports are only accessible from within Docker networks.
6 / 22
PR Description:
"Just merged the new microservice. It's running on the default bridge network and exposing port 8080. Seems straightforward."
This scenario highlights a common misunderstanding. While the default bridge network is convenient for simple setups, it doesn't always represent the *best* practice, particularly in more complex environments. The correct answer acknowledges that using the default is acceptable for basic microservices but also suggests further investigation into network policies is warranted – a crucial step when dealing with potential security or isolation concerns. Options A and C misinterpret the implications of using the default, while option D incorrectly praises the description without considering best practices.
7 / 22
During a code review of a new microservice deployment, Sarah says: 'The container is using a service mesh for ingress traffic. We're routing all requests through Envoy proxies.' John replies, 'But we've configured the container to use a sidecar proxy—it's running directly alongside the application.' What does John likely mean by 'sidecar proxy'?
John is referring to a 'sidecar proxy,' which is a very common architectural pattern in modern microservice deployments. A sidecar proxy runs alongside the application container as a separate process – often using Docker's `sidecars` feature – and handles network traffic independently. This allows for features like request routing, security policies, and observability monitoring to be applied without requiring changes to the main application itself, improving modularity and maintainability. The key distinction is that it's *parallel* to the app, not a separate namespace or firewall.
8 / 22
During a code review with Mark, you ask, "Can you elaborate on the 'default bridge network'? What does that actually *do*?" Mark responds: 'It just handles internal communication between containers within this pod.' Which of the following best describes Mark's statement about the 'default bridge network'?
Mark's statement accurately describes the function of the default bridge network. It's a virtual interface that facilitates communication *within* a Docker pod by translating IP addresses. A common misconception is that it provides external access or creates a completely isolated network; this is achieved through other networking configurations like port mappings and service definitions.
9 / 22
PR Description:
"Just merged the new microservice. It's running on the default bridge network and exposing port 8080. Seems straightforward."
This scenario highlights a common misunderstanding. While the default bridge network is convenient for simple setups, it doesn't always represent the *best* practice, particularly in more complex environments. The correct answer acknowledges that using the default is acceptable for basic microservices but also suggests further investigation into network policies is warranted – a crucial step when dealing with potential security or isolation concerns. Options A and C misinterpret the implications of using the default, while option D incorrectly praises the description without considering best practices.
10 / 22
During a code review of a new microservice deployment, Sarah says: 'The container is using a service mesh for ingress traffic. We're routing all requests through Envoy proxies.' John replies, 'But we've configured the container to use a sidecar proxy—it's running directly alongside the application.' What does John likely mean by 'sidecar proxy'?
John is referring to a 'sidecar proxy,' which is a very common architectural pattern in modern microservice deployments. A sidecar proxy runs alongside the application container as a separate process – often using Docker's `sidecars` feature – and handles network traffic independently. This allows for features like request routing, security policies, and observability monitoring to be applied without requiring changes to the main application itself, improving modularity and maintainability. The key distinction is that it's *parallel* to the app, not a separate namespace or firewall.
11 / 22
During a code review with Mark, you ask, "Can you elaborate on the 'default bridge network'? What does that actually *do*?" Mark responds: 'It just handles internal communication between containers within this pod.' Which of the following best describes Mark's statement about the 'default bridge network'?
Mark's statement accurately describes the function of the default bridge network. It's a virtual interface that facilitates communication *within* a Docker pod by translating IP addresses. A common misconception is that it provides external access or creates a completely isolated network; this is achieved through other networking configurations like port mappings and service definitions.
12 / 22
PR Description:
"Just merged the new microservice. It's running on the default bridge network and exposing port 8080. Seems straightforward."
This scenario highlights a common misunderstanding. While the default bridge network is convenient for simple setups, it doesn't always represent the *best* practice, particularly in more complex environments. The correct answer acknowledges that using the default is acceptable for basic microservices but also suggests further investigation into network policies is warranted – a crucial step when dealing with potential security or isolation concerns. Options A and C misinterpret the implications of using the default, while option D incorrectly praises the description without considering best practices.
13 / 22
During a code review of a new microservice deployment, Sarah says: 'The container is using a service mesh for ingress traffic. We're routing all requests through Envoy proxies.' John replies, 'But we've configured the container to use a sidecar proxy—it's running directly alongside the application.' What does John likely mean by 'sidecar proxy'?
John is referring to a 'sidecar proxy,' which is a very common architectural pattern in modern microservice deployments. A sidecar proxy runs alongside the application container as a separate process – often using Docker's `sidecars` feature – and handles network traffic independently. This allows for features like request routing, security policies, and observability monitoring to be applied without requiring changes to the main application itself, improving modularity and maintainability. The key distinction is that it's *parallel* to the app, not a separate namespace or firewall.
14 / 22
During a code review with Mark, you ask, "Can you elaborate on the 'default bridge network'? What does that actually *do*?" Mark responds: 'It just handles internal communication between containers within this pod.' Which of the following best describes Mark's statement about the 'default bridge network'?
Mark's statement accurately describes the function of the default bridge network. It's a virtual interface that facilitates communication *within* a Docker pod by translating IP addresses. A common misconception is that it provides external access or creates a completely isolated network; this is achieved through other networking configurations like port mappings and service definitions.
15 / 22
PR Description:
"Just merged the new microservice. It's running on the default bridge network and exposing port 8080. Seems straightforward."
This scenario highlights a common misunderstanding. While the default bridge network is convenient for simple setups, it doesn't always represent the *best* practice, particularly in more complex environments. The correct answer acknowledges that using the default is acceptable for basic microservices but also suggests further investigation into network policies is warranted – a crucial step when dealing with potential security or isolation concerns. Options A and C misinterpret the implications of using the default, while option D incorrectly praises the description without considering best practices.
16 / 22
During a code review of a new microservice deployment, Sarah says: 'The container is using a service mesh for ingress traffic. We're routing all requests through Envoy proxies.' John replies, 'But we've configured the container to use a sidecar proxy—it's running directly alongside the application.' What does John likely mean by 'sidecar proxy'?
John is referring to a 'sidecar proxy,' which is a very common architectural pattern in modern microservice deployments. A sidecar proxy runs alongside the application container as a separate process – often using Docker's `sidecars` feature – and handles network traffic independently. This allows for features like request routing, security policies, and observability monitoring to be applied without requiring changes to the main application itself, improving modularity and maintainability. The key distinction is that it's *parallel* to the app, not a separate namespace or firewall.
17 / 22
During a code review with Mark, you ask, "Can you elaborate on the 'default bridge network'? What does that actually *do*?" Mark responds: 'It just handles internal communication between containers within this pod.' Which of the following best describes Mark's statement about the 'default bridge network'?
Mark's statement accurately describes the function of the default bridge network. It's a virtual interface that facilitates communication *within* a Docker pod by translating IP addresses. A common misconception is that it provides external access or creates a completely isolated network; this is achieved through other networking configurations like port mappings and service definitions.
18 / 22
Sarah says: 'Our microservice uses a service mesh and is routing all traffic through Envoy proxies.' Mark replies, 'That's great! But can you elaborate on what a 'service mesh' actually *does* in this context?'. What does 'service mesh' refer to?
A 'service mesh' isn't just a protocol; it's a dedicated layer that manages communication between your services. It provides features like traffic control, security policies, and monitoring – all handled by proxies like Envoy. This allows for granular routing and observability without modifying the application code itself.
19 / 22
During a Slack discussion about container networking, David says: 'We're using port forwarding to expose the service.' What does 'port forwarding' describe?
'Port forwarding' is a fundamental concept. It allows external clients to access services running inside containers as if they were running directly on the host machine. This is typically achieved by mapping a port on the host to a port within the container, effectively creating a tunnel.
20 / 22
True or False: When you define 'ports: - 8080:80' in a Docker Compose file, the host machine is directly listening on port 8080 and forwarding all traffic to the container's port 80.
The `-` in 'ports: - 8080:80' indicates a *published* port. This means the container's port 80 is exposed externally, and traffic arriving on host port 8080 will be forwarded to the container. It's crucial to understand this difference from a regular port mapping.
21 / 22
You're reviewing a PR that introduces a new Kubernetes deployment for a microservice. The YAML definition includes: 'networking: podSubnet: '10.244.1.0/28''. What does 'podSubnet' represent?
'podSubnet' defines the range of IP addresses available for pods within a Kubernetes namespace. This is fundamental to how pods can communicate with each other – they use these IPs to form their local networks.
22 / 22
Mark says: 'We're using a 'daemon' network for our containers. It automatically creates a private network and allows them to communicate directly with each other without needing explicit configuration.' What is the primary benefit of using a daemon network?
Daemon networks are designed to simplify container networking. They automatically create a private network and assign IP addresses to containers within the same pod, allowing them to communicate directly without needing manual configuration or complex routing rules. This greatly reduces operational overhead.
What does the "Container Networking Vocabulary" exercise practise?
Learn container networking vocabulary: bridge network, host networking, ClusterIP, DNS between containers, port mapping, network namespaces — the language of professional container networking discussions.
How many questions are in this exercise?
This exercise has 22 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Containers & Virtualization category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Container Networking Vocabulary" part of a larger series?
Yes — it's one exercise in the Containers & Virtualization category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Containers & Virtualization category page for related exercises, or browse the main Exercises hub for other IT English topics.