EX188 Networking And Compose — 10 Questions

Question 1

How do you stop and remove containers, networks, and volumes created by a Podman Compose file?

Accepted Answer

podman-compose down. The `podman-compose down` command is the standard way to stop and remove all resources defined in a Compose file, including containers, networks, and (with the `-v` flag) volumes. It mirrors the behavior of `docker-compose down`, providing a clean teardown of the entire application stack. This command ensures that no orphaned resources remain, which is critical for maintaining a clean environment.

Answer

podman-compose rm --all

Answer

podman-compose destroy

Answer

podman-compose stop --purge

Question 2

You are using Podman Compose and need to generate Kubernetes YAML manifests from your compose file. Which command achieves this?

Accepted Answer

podman-compose -f compose.yaml k8s. 'podman compose -f compose.yml generate' or 'podman-compose' equivalents can output Kubernetes YAML depending on the exact tooling, but podman-compose / podman compose supports translation flags or subcommands. Specifically, podman-compose provides a way to output K8s resources.

Answer

podman compose convert --kubernetes

Answer

podman-compose export --format kubernetes

Answer

podman generate kubernetes --compose compose.yaml

Question 3

When inspecting the networking of a container using 'podman inspect', where is the IP address of the container located in the output JSON structure?

Accepted Answer

NetworkSettings.IPAddress. In `podman inspect` output, the container's IP address is found under `NetworkSettings.IPAddress`. This field contains the IPv4 address assigned to the container on its network. For IPv6, it would be under `NetworkSettings.GlobalIPv6Address`.

Answer

HostConfig.PortBindings.IP

Answer

Config.Network.IP

Answer

State.Networking.Address

Question 4

You are writing a Podman Compose file and want to ensure a service depends on another service being fully started before it initializes. Which directive should you use?

Accepted Answer

depends_on. `depends_on` is the Compose directive that declares a startup dependency between services, ensuring the dependent service is started after its dependency. In Podman Compose and Docker Compose, this is the standard way to express ordering in a compose file.

Answer

requires

Answer

wait_for

Answer

links_to

Question 5

Which TWO commands or flags can be used to publish a container port to the host in Podman? (Choose two.)

Accepted Answer

-p. Both -p and --publish are valid flags for publishing ports in Podman.

Answer

--port

Answer

--expose

Question 6

Which THREE networking modes are natively supported out-of-the-box by Podman container execution? (Choose three.)

Accepted Answer

bridge. Podman natively supports bridge, host, and none network modes.

Answer

macvlan

Answer

overlay

Question 7

When configuring a custom CNI network in Podman using 'podman network create', which TWO parameters can be explicitly defined via command-line flags during creation? (Choose two.)

Accepted Answer

--mtu. --subnet and --gateway can be specified during network creation.

Answer

--dns-server

Answer

--vlan-id

Question 8

Which TWO options are valid when specifying protocol restrictions on a port mapping in Podman (e.g., -p)? (Choose two.)

Accepted Answer

udp. Both tcp and udp can be specified as protocols in port mappings.

Question 9

Which TWO states or details does 'podman network inspect' provide about a network? (Choose two.)

Accepted Answer

Subnet configuration. Inspect provides JSON output detailing driver, subnet, and connected containers.

Answer

Host CPU utilization

Answer

Kernel version

Answer

Container disk usage

Question 10

When generating Kubernetes YAML using 'podman generate kubernetes', which TWO object types can be targeted or generated by the command? (Choose two.)

Accepted Answer

Deployment. Option A (Deployment) is correct because 'podman generate kube' (the Kubernetes YAML generator) can produce a Deployment object when the --type=deployment flag is used, wrapping the pod spec in a Deployment for replica management. Option C (Pod) is correct because the default output of 'podman generate kube' is a Pod object, which is the fundamental unit generated from a container or pod. Options B (DaemonSet), D (StatefulSet), and E (Ingress) are incorrect because the command does not support generating these object types; only Pod and Deployment are valid targets.

Answer

DaemonSet

Answer

StatefulSet

Answer

Ingress