Container networking in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Container Network Isolation

Which option best describes how container network isolation is typically achieved in Docker?

A Each container gets its own network namespace, isolating its network stack from others.

B Containers share the host's network stack without any isolation.

C Containers use a shared IP address but different ports without network namespaces.

D Containers communicate only through shared volumes, not networks.

💡 Hint

Think about how containers keep their network traffic separate.

Docker uses network namespaces to give each container its own isolated network stack, including interfaces and IP addresses.

❓ Architecture

intermediate

Choosing a Container Network Model

You need to design a microservices system where containers on different hosts must communicate securely and efficiently. Which container network model is best suited?

A Host network model, where containers share the host's network stack.

B Bridge network model, where containers communicate only on the same host.

C Overlay network model, which allows containers across hosts to communicate securely.

D None, containers cannot communicate across hosts.

💡 Hint

Consider multi-host communication with security.

Overlay networks create a virtual network that spans multiple hosts, enabling secure container communication across hosts.

❓ scaling

advanced

Scaling Container Networking for High Traffic

Your containerized application experiences high traffic and you want to scale networking without bottlenecks. Which approach best supports scalable container networking?

A Use a single bridge network for all containers to simplify routing.

B Assign static IPs to containers and manually configure routing tables.

C Disable container networking and use host networking for all containers.

D Implement a distributed service mesh to manage container communication and load balancing.

💡 Hint

Think about dynamic routing and load balancing at scale.

Service meshes provide dynamic routing, load balancing, and observability, which help scale container networking efficiently.

❓ tradeoff

advanced

Tradeoffs Between Host and Overlay Networking

What is a key tradeoff when choosing host networking over overlay networking for containers?

A Host networking provides better performance but less network isolation compared to overlay.

B Overlay networking has no encryption, while host networking encrypts all traffic.

C Host networking offers better isolation but worse performance than overlay.

D Overlay networking requires containers to share the host's IP address.

💡 Hint

Consider isolation versus performance.

Host networking shares the host's network stack, improving performance but reducing isolation, while overlay networks isolate containers but add overhead.

❓ estimation

expert

Estimating Network Capacity for Containerized Microservices

You run 1000 containers, each sending 1 Mbps traffic continuously. What is the minimum network bandwidth your container host cluster must support to avoid bottlenecks?

A 100 Gbps

B 10 Gbps

C 100 Mbps

D 1 Gbps

💡 Hint

Multiply containers by their traffic and convert units.

1000 containers × 1 Mbps = 1000 Mbps = 1 Gbps minimum; considering overhead and peak, 10 Gbps is safer.

Practice

1. What is the main purpose of container networking in microservices?

easy

A. To allow containers to communicate with each other

B. To store container data persistently

C. To build user interfaces for containers

D. To monitor container CPU usage

Solution

1. Step 1: Understand container networking role

   Container networking connects containers so they can send data and messages to each other.

2. Step 2: Compare with other options

   Storing data, building interfaces, and monitoring CPU are not related to networking.

3. Final Answer:

   To allow containers to communicate with each other -> Option A

4. Quick Check:

   Container networking = communication [OK]

Hint: Networking means communication between containers [OK]

Common Mistakes:

• Confusing networking with storage
• Thinking networking builds UI
• Mixing monitoring with networking

2. Which Docker command creates a user-defined network named mynet?

easy

A. docker create network mynet

B. docker network create mynet

C. docker network new mynet

D. docker net create mynet

Solution

1. Step 1: Recall Docker network creation syntax

   The correct command is docker network create <name>.

2. Step 2: Match options with syntax

   Only docker network create mynet matches the correct syntax exactly.

3. Final Answer:

   docker network create mynet -> Option B

4. Quick Check:

   docker network create = correct syntax [OK]

Hint: Remember: 'docker network create' is the right command [OK]

Common Mistakes:

• Swapping 'create' and 'network' order
• Using 'new' instead of 'create'
• Shortening 'network' to 'net' incorrectly

3. Given two containers web and db connected on a user-defined network mynet, what happens when web tries to ping db by container name?

medium

A. Ping succeeds because containers can resolve names on the same user-defined network

B. Ping fails because container names are not resolvable

C. Ping succeeds only if IP addresses are used, not names

D. Ping fails because containers cannot communicate on user-defined networks

Solution

1. Step 1: Understand user-defined network DNS resolution

   User-defined Docker networks provide automatic DNS resolution of container names.

2. Step 2: Apply to ping scenario

   Since both containers are on mynet, web can ping db by name successfully.

3. Final Answer:

   Ping succeeds because containers can resolve names on the same user-defined network -> Option A

4. Quick Check:

   User-defined network = name resolution works [OK]

Hint: User-defined networks enable container name resolution [OK]

Common Mistakes:

• Assuming container names are never resolvable
• Thinking IP addresses are always required
• Believing user-defined networks block communication

4. You created two containers on the default bridge network but they cannot communicate by container name. What is the likely cause?

medium

A. Container names must be IP addresses on default bridge

B. Containers must be on different networks to communicate

C. Default bridge network does not support automatic container name resolution

D. Docker daemon is not running

Solution

1. Step 1: Recall default bridge network limitations

   The default bridge network does not provide automatic DNS for container names.

2. Step 2: Analyze communication failure

   Without name resolution, containers cannot reach each other by name on default bridge.

3. Final Answer:

   Default bridge network does not support automatic container name resolution -> Option C

4. Quick Check:

   Default bridge = no name resolution [OK]

Hint: Default bridge lacks container name DNS [OK]

Common Mistakes:

• Thinking containers must be on different networks to communicate
• Confusing container names with IP addresses
• Assuming Docker daemon is stopped without checking

5. You want to isolate microservices into separate networks for security but allow only the api service to communicate with db. Which design best achieves this?

hard

A. Create separate networks but connect all containers to all networks.

B. Connect all services to a single network and use firewall rules inside containers.

C. Use the default bridge network for all containers and rely on container names.

D. Create two networks: api-net and db-net. Connect api to both networks, db only to db-net.

Solution

1. Step 1: Understand network isolation and selective communication

   Separating services into different networks isolates traffic. Connecting api to both networks allows it to talk to db while others cannot.

2. Step 2: Evaluate options for security and communication

   Create two networks: api-net and db-net. Connect api to both networks, db only to db-net. isolates db and allows only api access. Other options either lack isolation or allow unwanted access.

3. Final Answer:

   Create two networks: api-net and db-net. Connect api to both networks, db only to db-net. -> Option D

4. Quick Check:

   Separate networks + selective connection = secure communication [OK]

Hint: Use multiple networks and connect only needed containers [OK]

Common Mistakes:

• Putting all containers on one network without isolation
• Connecting all containers to all networks
• Relying on default bridge network for security