EX188 Container Operations And Lifecycle Practice Test 5 — 15 Questions

Question 1

An administrator is troubleshooting container exit codes and low-level state details. Which TWO of the following inspect format expressions correctly extract container state attributes? (Choose TWO)

Accepted Answer

podman inspect --format='{{.State.StartedAt}}' container_name. Option B is correct because podman inspect exposes the container's low-level state under the .State object, and .State.StartedAt is the valid field holding the container start timestamp. Option E is correct because the container exit code is stored at .State.ExitCode in the inspect JSON, so this Go-template expression properly extracts the exit status the administrator is troubleshooting. Option A is wrong because .Metadata.ExitCode does not exist in podman inspect output; exit codes live under .State, not .Metadata. Option C is wrong because .Status.Running is not a valid path — running state is reported via .State.Running. Option D is wrong because there is no top-level .Exit field; the exit code must be referenced as .State.ExitCode.

Answer

podman inspect --format='{{.Metadata.ExitCode}}' container_name

Answer

podman inspect --format='{{.Status.Running}}' container_name

Answer

podman inspect --format='{{.Exit}}' container_name

Question 2

An administrator wants to check container port mappings and process listings inside containers. Which TWO commands provide these insights? (Choose TWO)

Accepted Answer

podman port. Option A, `podman port`, is correct because it displays the port mappings for a container, showing which container ports are forwarded to which host ports, exactly the insight the administrator needs for port mappings. Option D, `podman top`, is correct because it runs a process listing inside a running container (similar to `ps`), letting the administrator inspect the processes running within that container. Option B, `podman ps-ports`, is not a valid podman subcommand, so it cannot provide port mapping information. Option C, `podman processes`, is not a valid podman subcommand for listing processes. Option E, `podman netstat`, is not a valid podman subcommand; network inspection is done via other tools or commands, not `podman netstat`.

Answer

podman ps-ports

Answer

podman processes

Answer

podman netstat

Question 3

An administrator needs to export container contents or create new images from containers. Which TWO commands accomplish these actions? (Choose TWO)

Accepted Answer

podman commit. Option C, podman commit, is correct because it creates a new image from a container's current state (including its filesystem and specified configuration), which directly satisfies the requirement to create new images from containers. Option D, podman export, is correct because it exports a container's filesystem as a tar archive, which directly satisfies the requirement to export container contents. Option A, podman extract, is not a valid Podman command for this purpose, so it does not belong. Option B, podman push-container, is not a valid Podman command; pushing is done with podman push for images, not containers. Option E, podman save, saves an existing image to an archive rather than exporting container contents or creating a new image from a container, so it does not meet the scenario.

Answer

podman extract

Answer

podman push-container

Answer

podman save

Question 4

An administrator needs to run a container named 'web01' using Podman in the background using the image registry.access.redhat.com/ubi8/httpd-24:latest. Which command correctly starts this container in detached mode and maps port 8080 on the host to port 80 in the container?

Accepted Answer

podman run -d --name web01 -p 8080:80 registry.access.redhat.com/ubi8/httpd-24:latest. 'podman run' is the command that creates and starts a container in one step, and -d puts it in detached (background) mode. The -p 8080:80 flag maps host port 8080 to container port 80 in the correct host:container order, and --name web01 assigns the required container name. This is the canonical Podman invocation for starting a named, detached, port-mapped container.

Answer

podman start -d --name web01 -p 8080:80 registry.access.redhat.com/ubi8/httpd-24:latest

Answer

podman container create -d --name web01 -p 8080:80 registry.access.redhat.com/ubi8/httpd-24:latest

Answer

podman run -b --name web01 -p 80:8080 registry.access.redhat.com/ubi8/httpd-24:latest

Question 5

A running Podman container named 'dbapp' is unresponsive, and a technician needs to immediately and forcefully terminate it without waiting for a graceful shutdown timeout. Which Podman command should be executed?

Accepted Answer

podman kill dbapp. The `podman kill` command sends a SIGKILL signal to the main process of the container by default, which immediately and forcefully terminates it without any graceful shutdown period. This matches the requirement to 'immediately and forcefully terminate' the unresponsive container. Unlike `podman stop`, which sends SIGTERM and waits for a timeout, `podman kill` does not wait and is the correct tool for this scenario.

Answer

podman stop --force dbapp

Answer

podman terminate dbapp

Answer

podman rm -f dbapp

Question 6

A container named 'metrics' has been running for several hours, and an engineer needs to inspect its current resource consumption (CPU, memory, and network I/O usage). Which Podman command provides a live-updating stream of resource usage statistics for running containers?

Accepted Answer

podman stats metrics. `podman stats` is the Podman equivalent of `docker stats` and provides a live, continuously updating stream of CPU, memory, network I/O, and block I/O statistics for one or more running containers. When a container name is passed (e.g., `podman stats metrics`), it filters the output to just that container and refreshes on an interval until interrupted.

Answer

podman inspect metrics

Answer

podman top metrics

Answer

podman system df metrics

Question 7

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 8

A container named 'worker' was configured with a health check command during build time, but an administrator needs to temporarily override or define a new health check command while running the container. Which flag should be passed to 'podman run' to achieve this?

Accepted Answer

--health-cmd. The `--health-cmd` flag in `podman run` allows overriding the health check command defined in the image. It specifies a command to run inside the container to check its health. This is the correct flag to temporarily define or override a health check at runtime.

Answer

--check-command

Answer

--healthcheck-run

Answer

--health-test

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 is managing rootless Podman containers as a non-root user and wants to ensure that these containers automatically start upon system boot and persist across reboots using systemd. Which TWO steps or commands are required to accomplish this? (Choose TWO)

Accepted Answer

Run 'loginctl enable-linger ' to allow the user's systemd instance to run in the background when not logged in.. Option D is correct because rootless Podman containers run under the non-root user's own systemd instance, and 'loginctl enable-linger ' keeps that user manager (systemd --user) running after logout and across reboots, which is required for user services to start at boot without an interactive login. Option E is correct because the supported way to make a rootless container start via systemd is to generate a user unit with 'podman generate systemd' (or a Quadlet) and place it in '~/.config/systemd/user/', then enable it with 'systemctl --user enable --now '. Option A is not correct because '--restart always' is a Podman-level restart policy that only takes effect while the Podman service/container is running; it does not itself start containers at system boot without systemd integration. Option B is not correct because enabling the system-wide 'podman' service with root privileges does not manage a non-root user's rootless containers. Option C is not correct because '/etc/rc.local' is a legacy system-wide boot script and does not properly integrate with the user's systemd instance for rootless containers.

Answer

Configure the container restart policy to always using '--restart always' without systemd.

Answer

Run 'systemctl enable --now podman' with root privileges.

Answer

Modify the global '/etc/rc.local' script to execute 'podman start' on boot.

Question 11

An administrator needs to manage multiple containers simultaneously using Podman. Which THREE actions can be performed directly using Podman commands? (Choose THREE)

Accepted Answer

Stop all running containers using 'podman stop $(podman ps -q)'.. Option A is correct because 'podman stop $(podman ps -q)' uses command substitution: 'podman ps -q' returns the IDs of all running containers, and 'podman stop' then stops each of them in one command, enabling bulk management. Option D is correct because 'podman container prune' is a built-in Podman command that removes all stopped containers, which is a standard bulk cleanup action. Option E is correct because 'podman restart <container_name>' is a valid Podman command that restarts the specified container by name or ID. Option B is not valid because Podman has no 'podman edit --tag' command to directly edit a running container's image tag; image tags are managed with commands like 'podman tag' or 'podman build', not by editing a running container. Option C is not valid because Podman has no 'podman migrate' command to instantly move a running container to a remote physical server; container migration/checkpointing is handled by tools such as CRIU with 'podman container checkpoint' and 'podman container restore', not a simple 'migrate' subcommand.

Answer

Directly edit a running container's image tag using 'podman edit --tag'.

Answer

Instantly migrate a running container to a remote physical server using 'podman migrate'.

Question 12

An administrator needs to inspect the low-level configuration of a running container named net_tool, including its network settings, mounted volumes, and environment variables, in a JSON format for automation. Which command should the administrator use?

Accepted Answer

podman inspect net_tool. The podman inspect command provides comprehensive JSON output about a container's configuration, including network settings, volumes, environment variables, and other metadata. It is the correct tool for obtaining low-level details in a machine-readable format. Other commands like podman ps, podman logs, and podman top offer limited or unrelated information and do not fulfill the requirement for detailed configuration inspection.

Answer

podman top net_tool

Answer

podman ps --format json net_tool

Answer

podman logs net_tool

Question 13

An administrator has a running container named web_front that was started with podman run -d --name web_front nginx. The administrator needs to execute the command 'nginx -T' inside this already-running container to dump the full configuration. Which command accomplishes this?

Accepted Answer

podman exec web_front nginx -T. Running a diagnostic or interactive command inside a container that is already running requires podman exec, which spawns an additional process in the container's namespaces. Commands like podman run create new containers, podman attach links to PID 1, and podman start only starts stopped containers, so none of them can execute nginx -T within the existing web_front container.

Answer

podman run web_front nginx -T

Answer

podman attach web_front nginx -T

Answer

podman start web_front nginx -T

Question 14

An administrator wants to create a new container named app_test from the image registry.example.com/apps/web:v2, but the container should not start immediately so that environment variables can be adjusted first. Which command creates the container without starting it?

Accepted Answer

podman create --name app_test registry.example.com/apps/web:v2. To prepare a container without launching it, use podman create, which instantiates the container from the image and leaves it stopped. podman run starts immediately, podman pull only fetches the image, and podman start requires an existing container. Creating first and starting later allows configuration changes before the application initializes.

Answer

podman run --name app_test registry.example.com/apps/web:v2

Answer

podman start --name app_test registry.example.com/apps/web:v2

Answer

podman pull --name app_test registry.example.com/apps/web:v2

Question 15

An administrator has a container named legacy_api that has been stopped for several weeks. A teammate reports that the container's filesystem still contains an outdated configuration file at /etc/app/config.yml. The administrator wants to replace that file inside the stopped container's filesystem without starting it. Which command should the administrator use?

Accepted Answer

podman cp ./config.yml legacy_api:/etc/app/config.yml. podman cp transfers files between the host and a container's filesystem regardless of whether the container is running or stopped. Commands such as podman exec and podman attach require a running container, and podman update changes runtime resource settings rather than file contents, so podman cp is the only viable choice for modifying a stopped container's file.

Answer

podman update --file ./config.yml legacy_api

Answer

podman exec legacy_api sh -c 'echo > /etc/app/config.yml'

Answer

podman attach legacy_api sh