EX188 Practice Test 4 — 10 Questions

Question 1

What is the primary benefit of utilizing multi-stage builds in Containerfiles?

Accepted Answer

It allows you to produce a final production image containing only the application binary and runtime dependencies, significantly reducing image size and attack surface.. Multi-stage builds allow developers to use multiple FROM statements, leaving behind build tools and heavy SDKs in earlier stages and keeping production images small and secure.

Answer

It automatically encrypts environment variables stored in the image layers.

Answer

It bypasses the need for a container registry when sharing images.

Answer

It speeds up local DNS resolution during container execution.

Question 2

An administrator has created a systemd service file named container-web.service using podman generate systemd. Where should this file be placed for a rootless user to manage it as a user-level service?

Accepted Answer

~/.config/systemd/user/. For rootless Podman containers, systemd user services must reside in the user's systemd configuration directory, which is ~/.config/systemd/user/. This allows the user to manage the service with systemctl --user commands without requiring root privileges. Placing the unit file here ensures it is loaded when the user's systemd instance starts, typically at login.

Answer

~/.local/share/podman/systemd/

Answer

/etc/systemd/system/

Answer

/var/lib/containers/systemd/

Question 3

An administrator is configuring a systemd service using podman generate systemd and wants the generated service to stop and remove the container automatically when the service stops, and create a fresh container when it starts. Which flag should be added?

Accepted Answer

--new. The --new flag in podman generate systemd creates a systemd unit that removes the existing container when the service stops and creates a fresh container when it starts. This ensures a clean state on each service start, which is useful for stateless or ephemeral workloads.

Answer

--ephemeral

Answer

--recreate

Answer

--auto-remove

Question 4

A developer wants to push a locally built container image named webapp:v1 to a private container registry located at registry.local:5000/myteam/. Which sequence of commands correctly tags and pushes the image?

Accepted Answer

podman tag localhost/webapp:v1 registry.local:5000/myteam/webapp:v1 followed by podman push registry.local:5000/myteam/webapp:v1. The correct workflow requires first creating a new tag that includes the full registry path (registry.local:5000/myteam/webapp:v1) pointing to the existing local image, then pushing that fully-qualified reference. The 'podman tag' command creates an additional name for the same image without copying layers, and 'podman push' uses the registry-qualified name to determine the destination. This two-step approach is required because podman push does not accept a separate --registry flag to redirect an existing local name.

Answer

podman push webapp:v1 --registry registry.local:5000/myteam/

Answer

podman commit webapp:v1 registry.local:5000/myteam/webapp:v1

Answer

podman export webapp:v1 > registry.local:5000/myteam/webapp:v1.tar

Question 5

An operator needs to troubleshoot a failing service inside a container named 'auth_api'. Which command should the operator run to view the standard output log stream generated by this container?

Accepted Answer

podman logs auth_api. The `podman logs` command retrieves the standard output (stdout) and standard error (stderr) logs from a container, exactly what the operator needs to troubleshoot the failing service. It works for both running and stopped containers, and supports options like `-f` to follow the stream in real time. This is the direct Podman equivalent of `docker logs`.

Answer

podman output auth_api

Answer

podman events auth_api

Answer

podman history auth_api

Question 6

An administrator needs to connect an already running container named 'web1' to an existing user-defined network named 'backend-net' without restarting the container. Which command accomplishes this?

Accepted Answer

podman network connect backend-net web1. The podman network connect command attaches a running container to an existing user-defined network without requiring a restart. Its syntax is 'podman network connect ', which matches option B. This is the supported way to add a live container to an additional network, and Podman updates the container's DNS and interfaces dynamically.

Answer

podman network attach backend-net web1

Answer

podman container modify --network backend-net web1

Answer

podman network join --container web1 backend-net

Question 7

An administrator needs to create a Podman secret from a file on disk named 'secret.txt'. Which command correctly performs this action?

Accepted Answer

podman secret create db_secret secret.txt. The correct syntax for creating a Podman secret from a file is `podman secret create `. Podman's secret subcommand mirrors Docker's `docker secret create` syntax, where the secret name comes first and the source file (or `-` for stdin) comes second. This command reads the file contents and stores them in Podman's secret store, making them available to containers via `--secret`.

Answer

podman secret import db_secret secret.txt

Answer

podman create secret db_secret secret.txt

Answer

podman secret add db_secret --file secret.txt

Question 8

An administrator needs to remove all stopped containers from the system to free up disk space in a single command. Which command should be used?

Accepted Answer

podman container prune. The podman container prune command removes all stopped containers in a single operation, freeing disk space and cleaning up the container runtime state. It is the purpose-built subcommand for this task and prompts for confirmation before deletion (unless --force is used). This is the correct and idiomatic Podman command for bulk removal of stopped containers.

Answer

podman rm stopped

Answer

podman system clean

Answer

podman rm --all

Question 9

An administrator wants to monitor real-time Podman system events, such as when containers are created, started, stopped, or removed, for auditing purposes. Which command should be executed?

Accepted Answer

podman events. The podman events command streams real-time events from the Podman service, including container create, start, stop, die, and remove actions, along with image and network events. It is the direct analog to 'docker events' and is the correct tool for auditing container lifecycle activity. Options like 'podman audit' and 'podman monitor' do not exist as Podman subcommands.

Answer

podman audit

Answer

podman system stream

Answer

podman monitor

Question 10

An administrator wants to ensure that a bind-mounted directory allows propagation of mounts from the host into the container. Which mount option configures mount propagation mode?

Accepted Answer

podman run -v /host/dir:/container/dir:shared myapp. The :shared mount option on a bind mount configures mount propagation mode to shared, allowing mounts performed on the host to propagate into the container (and vice versa). The syntax is -v /host/dir:/container/dir:shared, where shared is the propagation mode keyword.

Answer

podman run -v /host/dir:/container/dir:mtype=shared myapp

Answer

podman run -v /host/dir:/container/dir:sync myapp

Answer

podman run -v /host/dir:/container/dir:propagate myapp