The journalctl command is used to query and display logs from the systemd journal.

B: The -p or --priority option filters messages by a specified priority level and all levels that are more severe. Specifying -p err (priority 3) will display messages logged at the err, crit (2), alert (1), and emerg (0) levels. While the wording "only error log level" is imprecise, it is interpreted in this context as filtering based on the error level, which is correct.

D: The -k or --dmesg flag is a shortcut to show only kernel messages. This option implicitly applies the -b flag, which restricts the output to messages from the current boot only.

E: The -p option accepts numerical priority values. info corresponds to priority 6. Therefore, journalctl -p 6 will display all messages with a priority of 6 (info) or a more severe priority (0-5).

A. The command will not fail. The -b flag shows logs from the current boot, which are stored in memory (/run/log/journal) and are available even if persistence to /var/log/journal is not configured.

C. This command shows messages in the notice and warning priority range from all available journals. It does not limit the output to only the last boot, as the -b flag was not specified.

1. systemd Project

journalctl Manual Page:

For options B and E: "-p

--priority= Filter output by message priorities. ... If a single priority is specified

all messages with this or a more important priority are shown. ... The priorities are the usual syslog priorities as documented in syslog(3)

i.e. "emerg" (0)

"alert" (1)

"crit" (2)

"err" (3)

"warning" (4)

"notice" (5)

"info" (6)

"debug" (7)."

For option D: "-k

--dmesg Show only kernel messages. This implies -b and adds the match TRANSPORT=kernel."

For options A and C: "-b [[ID][±offset]]

--boot=[[ID][±offset]] Show messages from a specific boot. ... The argument may be empty

in which case logs for the current boot will be shown."

Source: freedesktop.org

journalctl(1) man page.

2. Oracle® Linux 8 Documentation

Managing Core System Configuration:

Section 12.3.2. Filtering Log Output: "To view only kernel messages

use the -k or --dmesg option. By default

this command displays kernel messages from the current boot." This supports option D.

Section 12.3.2. Filtering Log Output: "To filter output by message priority

use the -p or --priority option. You can use either the name or the corresponding number for the priority level... For example

to view only messages with a priority of error or higher

type: sudo journalctl -p err -b" This supports the functionality described in options B and E.

Source: Oracle Linux 8 Documentation

Chapter 12. Managing Log Files With journald.

The /etc/sysconfig directory in Oracle Linux 8 contains static configuration files and scripts that control the behavior of system services and utilities. When a software package that provides a system service (e.g., chronyd, sshd, network-scripts) is installed, it often places a corresponding configuration file in this directory. For example, installing the chronyd package creates /etc/sysconfig/chronyd. Therefore, the contents of the /etc/sysconfig directory are directly dependent on which packages are installed on the system, allowing administrators to customize service parameters.

A. Device and driver information is dynamically exposed through the /sys and /proc virtual filesystems, not stored in /etc/sysconfig.

B. Information about running processes is located in the /proc virtual filesystem, with each process having a subdirectory named by its process ID.

D. System hardware information is made available by the kernel through virtual filesystems like /proc (e.g., /proc/cpuinfo) and /sys.

1. Oracle Linux 8 Documentation: In the "Managing Core System Configuration" guide

the description of the /etc directory states it contains system configuration files. The /etc/sysconfig subdirectory is a convention in RHEL-based distributions like Oracle Linux for holding configuration files for services installed by packages. For instance

the networking service configuration is detailed in /etc/sysconfig/network-scripts/

which is provided by the network-scripts package.

Source: Oracle® Linux 8: Managing Core System Configuration

Chapter 1

"About System Configuration Files".

2. systemd Documentation (man pages): The systemd.exec(5) man page

which is part of the official Oracle Linux 8 system documentation

describes the EnvironmentFile= directive used in service unit files. This directive often points to a file in /etc/sysconfig to load service-specific configuration variables. This establishes a direct link between a service (installed by a package) and its configuration file in /etc/sysconfig.

Source: man systemd.exec

Section "EnvironmentFile="

Oracle Linux 8.

3. Red Hat Enterprise Linux 8 Documentation: As Oracle Linux is derived from RHEL

its documentation is highly relevant. The "Configuring and managing networking" guide explicitly details the role of files within /etc/sysconfig/network-scripts. The presence and content of these files depend on the network-scripts package being installed and the network interfaces configured.

Source: Red Hat Enterprise Linux 8 Documentation

"Configuring and managing networking

" Section 2.3

"Configuring an Ethernet connection using ifcfg files".

An rsyslog rule defines how to process a specific log message and consists of two fundamental components. The first is a filter (also known as a selector), which specifies the conditions a message must meet to be selected, such as its facility (e.g., kern, mail) and priority level (e.g., info, err). The second component is the action, which defines what to do with the selected message, such as writing it to a specific file, sending it to a remote server, or discarding it. This filter-action structure forms the basis of all rules in the rsyslog.conf file.

C. parser: A parser is a component that interprets the structure and content of a log message, but it is not a direct part of the rule's filter/action syntax.

D. module: Modules extend rsyslog functionality (e.g., for input or output). While an action may utilize a module, the module itself is not a primary component of the rule's syntax.

E. security policy: A security policy is a high-level set of rules and procedures. It is not a syntactic component used to construct an individual rsyslog rule.

1. Oracle Linux 8 Documentation: Managing Core System Configuration

Chapter 22. Viewing and Managing Log Files

Section 22.3.1. Understanding the rsyslog.conf file format. The documentation states

"Each rule consists of two fields: a selector field and an action field... The selector field

also called a filter

specifies a message source and a priority level."

2. rsyslogd Official Documentation: The documentation for rsyslog.conf format specifies the basic rule structure. "Every rule line consists of two parts: a selector and an action... The selector

now also called filter

specifies which messages to select for the action." (Reference: rsyslog.com

Documentation

Configuration

rsyslog.conf).

3. Linux man pages: The rsyslog.conf(5) man page

available on Oracle Linux systems

describes the rule format. Under the "RULES" section

it details that lines are composed of a "Filter Part" and an "Action Part".

The OpenSSH client (ssh) processes configuration settings in a specific hierarchical order to determine the final value for any given parameter. The command-line options are evaluated last, granting them the highest precedence. This allows a user to override any pre-configured settings from the system-wide (/etc/ssh/sshconfig) or user-specific (~/.ssh/config) files for a single, specific connection attempt. For any given keyword, the first value obtained will be used.

A. /etc/ssh/sshconfig is the system-wide configuration file and has the lowest precedence; its settings are overridden by both user-specific files and command-line options.

B. ~/.ssh/config is the user-specific configuration file. It overrides the system-wide file but is, in turn, overridden by options specified on the command line.

D. /etc/ssh/sshdconfig is the configuration file for the SSH server daemon (sshd), not the ssh client program, and is therefore irrelevant to this question.

1. OpenBSD Manual Pages (Official source for OpenSSH): The sshconfig(5) man page explicitly states the order of precedence.

Source: sshconfig(5) Manual Page

OpenBSD.

Reference: In the "DESCRIPTION" section

it states: "ssh(1) obtains configuration data from the following sources in the following order: 1. command-line options

2. user's configuration file (~/.ssh/config)

3. system-wide configuration file (/etc/ssh/sshconfig)."

2. Oracle Linux 8 Documentation: The official documentation for Oracle Linux

which is the basis for the 1Z0-106 exam

confirms this hierarchy.

Source: Oracle® Linux 8: Securing Oracle Linux

Chapter 10. Securing Remote Connections with OpenSSH.

Reference: Section 10.2.2

"OpenSSH Client Configuration Files

" details that command-line options override settings in configuration files

and user-specific files override system-wide files.

3. MIT OpenCourseWare: Course materials often cover fundamental tools like SSH

reinforcing standard behavior.

Source: MIT 6.NULL

"The Missing Semester of Your CS Education

" Lecture 2: Shell Tools and Scripting.

Reference: The lecture notes on SSH describe the use of ~/.ssh/config to set user-level defaults

which implicitly exist within the standard precedence hierarchy confirmed by official documentation.

A Kubernetes Deployment is a controller that manages the lifecycle of pods. Its primary function, as defined by the replicas field in its specification, is to ensure that a specified number of pod replicas are running and available. It continuously monitors the state of its pods and automatically replaces any that fail, are terminated, or become unresponsive, thereby guaranteeing the desired state. The containerPort field within the pod template is a declarative way to specify the network port on which a container will listen for traffic. While this field is informational, it correctly documents the port the container exposes.

B. The Deployment's name is explicitly defined as nginx-deployment in the metadata.name field of the YAML, not nginx.

C. The Deployment creates pods with unique, auto-generated names based on the ReplicaSet hash (e.g., nginx-deployment-5c689d88bb-h9k7l), not a static name like nginx.

E. The kubectl create command only submits the object definition to the API server. The command succeeds if the YAML is valid. An unavailable image causes a pod to fail later during the scheduling/pulling phase, not the initial Deployment creation.

1. Kubernetes Documentation

"Deployments": A Deployment's primary purpose is to provide declarative updates for Pods and ReplicaSets. "You describe a desired state in a Deployment

and the Deployment Controller changes the actual state to the desired state at a controlled rate." This supports option A's statement about guaranteeing a number of pods.

Source: kubernetes.io/docs/concepts/workloads/controllers/deployment/

Section: "What is a Deployment?".

2. Kubernetes Documentation

"Container v1 core" API Reference: The containerPort field is officially defined as the "Number of port to expose on the pod's IP address. This must be a valid port number

0 < x < 65536." This confirms the purpose described in option D.

Source: kubernetes.io/docs/reference/generated/kubernetes-api/v1.28/

Section: "Container v1 core".

3. Kubernetes Documentation

"Object Names and IDs": "Each object in your cluster has a Name that is unique for that type of resource." The YAML clearly specifies name: nginx-deployment

making option B incorrect. The document also explains that pods owned by a ReplicaSet have unique

generated names

making option C incorrect.

Source: kubernetes.io/docs/concepts/overview/working-with-objects/names/

Section: "Names".

4. Kubernetes Documentation

"Container Images": The process of pulling an image is handled by the kubelet on a node after a pod has been scheduled. If an image cannot be pulled

the pod enters a failure state like ImagePullBackOff. The initial kubectl create command

which creates the Deployment object

would have already succeeded. This invalidates the premise of option E.

Source: kubernetes.io/docs/concepts/containers/images/

Section: "Image pull policy".