EX188 Practice Test 14 — 15 Questions

Question 1

An administrator needs to view the processes running inside a specific container named worker_node, along with custom ps options like -ef to see full command arguments. Which command accomplishes this?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

podman top worker_node -ef. podman top runs a ps-like command inside the container's PID namespace and accepts custom ps arguments, so 'podman top worker_node -ef' shows all processes with full command lines. This is the purpose-built command for inspecting in-container processes with tailored output.

Answer

podman ps --processes worker_node

Answer

podman exec worker_node ps -ef

Answer

podman inspect --processes worker_node

Question 2

An administrator wants to inspect the container storage configuration settings, such as graph root and storage driver, on a RHEL system. Which configuration file should they examine?

Accepted Answer

/etc/containers/storage.conf. The /etc/containers/storage.conf file is the primary configuration file for container storage on RHEL systems using Podman. It defines settings such as the storage driver (e.g., overlay) and the graph root directory where container images and layers are stored. Administrators inspect this file to understand or modify how container storage is managed.

Answer

/etc/containers/podman.conf

Answer

/etc/containers/registries.conf

Answer

/etc/sysconfig/docker

Question 3

Which TWO instructions in a Containerfile can be used to set metadata or default execution parameters that influence how a container runs? (Choose two.)

Accepted Answer

CMD. CMD [CORRECT] is right because it sets the default command (and/or default arguments) that the container executes when it starts if no command is supplied at runtime, directly influencing how the container runs. ENTRYPOINT [CORRECT] is also right because it configures the executable that the container always runs, defining the container's primary process and default execution behavior. Both are runtime metadata instructions stored in the image config, unlike build-time instructions. RUN (A) executes commands during image build to create layers and does not set runtime defaults. COPY (D) only copies files from the build context into the image filesystem. FROM (E) merely specifies the base image for the build stage and has no role in runtime execution parameters.

Answer

RUN

Answer

COPY

Answer

FROM

Question 4

An administrator wants to create a named volume using a specific volume driver instead of the default local driver. Which flag should be used with 'podman volume create'?

Accepted Answer

podman volume create --driver nfs my_vol. 'podman volume create --driver nfs my_vol' correctly specifies the volume driver using the '--driver' flag. Podman supports pluggable volume drivers, and '--driver' is the documented option to select a non-default driver such as nfs, glusterfs, or a custom plugin.

Answer

podman volume create --storage-driver nfs my_vol

Answer

podman volume create --plugin nfs my_vol

Answer

podman volume create -t nfs my_vol

Question 5

A user needs to download an image from Docker Hub named 'library/alpine' using its explicit transport prefix. Which command demonstrates the correct transport syntax?

Accepted Answer

podman pull docker://alpine:latest. The correct transport for pulling from a Docker registry like Docker Hub is 'docker://'. The command 'podman pull docker://alpine:latest' explicitly tells Podman to use the Docker transport to fetch the 'library/alpine' image from Docker Hub. This syntax is part of Podman's support for multiple transports, where 'docker://' is the standard prefix for registry-based images.

Answer

podman pull registry://alpine:latest

Answer

podman pull remote://alpine:latest

Answer

podman pull OCI://alpine:latest

Question 6

An administrator needs to run a container that requires access to the host's network stack directly, bypassing network isolation. Which flag should be passed to 'podman run'?

Accepted Answer

--network host. The `--network host` flag makes the container share the host's network namespace, so it uses the host's IP address, routing table, and ports directly without network isolation. This is the correct way to bypass network isolation and give the container direct access to the host network stack.

Answer

--share network

Answer

--privileged

Answer

--net bridge

Question 7

An administrator needs to check the disk space consumption of all containers, images, and volumes managed by Podman. Which command should be run?

Accepted Answer

podman system df. `podman system df` is the correct command because it reports disk usage for Podman-managed objects — images, containers, volumes, and the build cache — in a single summary table, mirroring `docker system df`. It shows total size, reclaimable space, and active counts, making it the canonical way to audit storage consumption. The other options are not valid Podman subcommands.

Answer

podman storage show

Answer

podman disk usage

Answer

podman inspect --disk

Question 8

An administrator wants to modify container settings or state. Which TWO of the following commands are valid Podman subcommands for container management? (Choose TWO)

Accepted Answer

podman restart. Option D, 'podman restart', is a valid Podman subcommand that stops and starts one or more running containers, which directly modifies container state and is used for container management. Option E, 'podman rename', is also a valid Podman subcommand that changes the name of an existing container, thereby modifying container settings/state. The other options are not Podman subcommands: 'podman reconfigure', 'podman alter', and 'podman modify' do not exist in Podman's CLI, so they cannot be used to manage containers.

Answer

podman reconfigure

Answer

podman alter

Answer

podman modify

Question 9

An administrator creates a custom CNI network using 'podman network create mynet' and wants to assign a static IP address to a container upon creation. Which option achieves this?

Accepted Answer

podman run --network mynet --ip 192.168.100.50 -d myimage. The `--ip` flag combined with `--network mynet` is the correct way to assign a static IP to a container on a custom CNI network in Podman. The syntax `podman run --network mynet --ip 192.168.100.50 -d myimage` attaches the container to the named network and requests the specified IP from the network's IPAM range. The IP must fall within the subnet defined when the network was created.

Answer

podman run --network mynet:192.168.100.50 -d myimage

Answer

podman network connect --ip 192.168.100.50 mynet container_id

Answer

podman run --net-static-ip 192.168.100.50 -d myimage

Question 10

Which TWO conditions are typically required for rootless container users to successfully map UIDs and GIDs from host accounts to container accounts? (Choose two.)

Accepted Answer

The user account must have assigned ranges in /etc/subuid and /etc/subgid.. Option A is correct because rootless containers rely on subordinate UID/GID mappings, which are defined per-user in /etc/subuid and /etc/subgid; without an assigned range, the user namespace cannot map container IDs to unprivileged host IDs. Option C is correct because user namespaces are the kernel feature that makes rootless UID/GID mapping possible, and on RHEL 9 this support is enabled by default. Option B is incorrect because rootless containers are specifically designed to run without root or sudo privileges on the host. Option D is incorrect because the vfs storage driver is not required for UID/GID mapping and is generally used only as a fallback due to poor performance. Option E is incorrect because disabling SELinux globally is not a prerequisite for rootless containers and would weaken host security.

Answer

The user must have root privileges via sudo on the host system.

Answer

The storage driver must be set to vfs exclusively.

Answer

SELinux must be set to disabled mode globally.

Question 11

A practitioner wants to view all container images currently stored in local storage, including their size, tag, and image ID. Which command should they execute?

Accepted Answer

podman images. The `podman images` command lists all container images in local storage, displaying repository, tag, image ID, creation time, and size. It is the direct equivalent of `docker images` and is the standard way to inspect the local image cache. Options A, C, and D are not valid Podman subcommands for listing images.

Answer

podman list images

Answer

podman show images

Answer

podman ps -a

Question 12

A user running rootless Podman wants to pull an image from an insecure registry running over HTTP on port 5000. When running 'podman pull', the command fails with a connection error. Where must the administrator define this registry as insecure for the user?

Accepted Answer

~/.config/containers/registries.conf. For rootless Podman, user-specific configuration files take precedence over system-wide ones. The correct location to define an insecure registry for a single user is ~/.config/containers/registries.conf, which is the per-user override for /etc/containers/registries.conf. Podman reads this file when running as a non-root user, allowing the user to specify registries as insecure without requiring root privileges. This is part of the containers/image configuration stack, and the user-level file is the proper place for such customizations.

Answer

~/.local/share/containers/storage.conf

Answer

/etc/sysconfig/podman

Answer

/etc/containers/registries.conf

Question 13

Two containers running on the same custom user-defined bridge network need to communicate using container names as hostnames. What is required for this to work natively in Podman?

Accepted Answer

Nothing extra; user-defined bridge networks include built-in DNS resolution.. User-defined bridge networks in Podman (and Docker) include an embedded DNS resolver, typically at 127.0.0.11 inside each container, that resolves container names and network aliases to their current IP addresses. Because both containers are attached to the same custom network, Podman's DNS plugin (dnsname/aardvark-dns) automatically registers each container's name, so no manual /etc/hosts editing or --link is needed. This is a core advantage of user-defined networks over the default bridge, which lacks automatic name resolution.

Answer

You must use the default 'podman' bridge network.

Answer

You must edit /etc/hosts inside the containers manually.

Answer

You must manually link containers using the --link flag.

Question 14

An administrator wants to retrieve only the IP address of a running container named web_svc by querying podman inspect with a specific format template. Which command is correct?

Accepted Answer

podman inspect --format='{{ .NetworkSettings.IPAddress }}' web_svc. podman inspect supports Go-template formatting via --format, and the container's IP address lives at .NetworkSettings.IPAddress in the inspect JSON. The command podman inspect --format='{{ .NetworkSettings.IPAddress }}' web_svc extracts exactly that field for the named container.

Answer

podman ps --format='{{ .IP }}' web_svc

Answer

podman inspect --ip web_svc

Answer

podman inspect --query=ip web_svc

Question 15

When utilizing Podman Compose, how are service dependencies and container startup orders typically managed within the YAML structure?

Accepted Answer

Using the 'depends_on' configuration key under the service definition. Podman Compose, like Docker Compose, uses the 'depends_on' key under a service definition to express startup dependencies. This ensures that when a service is started, its dependencies are started first, controlling the order in which containers are launched. The 'depends_on' key does not wait for the dependent service to be 'ready' (e.g., healthy), only that it has been started, unless combined with health checks and conditions in some versions.

Answer

By ordering the service keys alphabetically in the YAML file

Answer

Using the 'links' parameter exclusively

Answer

Through the 'startup_order' directive