Oracle 1z0-106 Dumps

To use a file as swap space, it must first be initialized with themkswapcommand. Theddcommand creates an empty file, butmkswapformats this file to be used as swap space. This command writes the necessary swap header to the file, making it recognizable by the system as a valid swap area.

Explanation of Answer D:After initializing the swap file withmkswap, you can optionally assign a label to the swap file using theswaplabelcommand. This is not strictly required, but it can be useful for identifying swap files, especially if you are using multiple swap devices.

Option B: journalctl -p err shows only error log level.

Explanation:

The -p or --priority option in journalctl filters messages by their priority level.

When specifying asingle priority level, journalctl shows messagesonlyat that level.

The priority levels, as per syslog standards, are:

0: emerg

1: alert

2: crit

3: err

4: warning

5: notice

6: info

7: debug

Therefore, journalctl -p err displays messages with priorityerr (3)only.

Oracle Linux Reference:

Oracle® Linux 8: Managing Log Files- Section onFiltering Output withjournalctl:

"Use the -p option to display messages from the journal that have a specific priority level."

Example:

# journalctl -p err

Option D: journalctl -k shows kernel logs since the last boot.

Explanation:

The -k or --dmesg option filters messages from the kernel, equivalent to the output of the dmesg command.

This option implies -b, which limits the output to messages from the current boot.

Therefore, journalctl -k displays kernel messages since the last boot.

Oracle Linux Reference:

Oracle® Linux 8: Managing Log Files- Section onViewing Kernel Messages:

"Use the journalctl -k command to display kernel messages since the last system boot."

Example:

# journalctl -k

Option E: journalctl -p 6 shows all info log level messages and above.

Explanation:

When specifying a single numeric priority, journalctl displays messages withthat priority level and higher priority levels(i.e., lower severity).

Priority levels are ordered from 0 (highest severity) to 7 (lowest severity).

Therefore, journalctl -p 6 shows messages with priorities:

0 (emerg)

1 (alert)

2 (crit)

3 (err)

4 (warning)

5 (notice)

6 (info)

This includesinfo level messages (6)and all higher priority messages.

Oracle Linux Reference:

Oracle® Linux 8: Managing Log Files- Section onFiltering Output with journalctl:

"When you specify a single priority level, journalctl shows messages at that level and higher severity."

Example:

# journalctl -p 6

Why Other Options Are Not Correct:

Option A:journalctl -bl -p err fails if journal persistence is not configured.

Explanation:

The -b option displays messages from the current boot. This works even if journal persistence isnotconfigured because the logs from the current boot are stored in volatile memory (/run/log/journal).

Therefore, the command doesnot failif journal persistence is not configured.

Oracle Linux Reference:

Oracle® Linux 8: Managing Log Files- Section onJournal Volatility:

"By default, the journal stores logs in volatile memory and does not persist logs across reboots unless persistent storage is configured."

Option C:journalctl -p notice..warning shows all messages from notice to warning log level since the last boot.

Explanation:

The -p option allows specifying arangeof priorities. However, the correct order for the range should be from thehigher priority (lower number)to thelower priority (higher number).

Also, the priorities should be specified in the correct sequence, and ranges are inclusive.

Moreover, journalctl by default shows messages from all boots unless limited by the -b option.

Therefore, without -b, it does not limit messages to "since the last boot," making the statement incorrect.

Correct Command:

To display messages fromwarning (4)tonotice (5), the command should be:

# journalctl -p warning..notice -b

But even then, the priorities need to be specified correctly, and the command in Option C is incorrect.

Conclusion:

OptionsB,D, andEare correct because they accurately describe the behavior of the journalctl command in filtering and displaying log messages based on priority levels and sources.

Explanation of Answer C:Thesscommand can be used to display all available internal TCP information, including established connections with detailed TCP metrics, which matches the output in Answer C.

Explanation of Answer D:Thesscommand can display listening ports (TCP in this case) with details like congestion control algorithms (cubic), which aligns with Answer D. The output indicates a listening TCP socket on port 80.

The correct command to create a RAID-1 device (mirroring) consisting of two block volumes with one spare device is optionC:mdadm –create /dev/md0 –level=1 –raid-devices=2 /dev/xvdd1 /dev/xvdd2 –spare-devices=1 /dev/xvdd3.

RAID Level 1:RAID-1, also known as mirroring, involves creating an exact copy (or mirror) of a set of data on two or more disks. This ensures data redundancy; if one disk fails, the other can still provide the data.

mdadm Command Structure:Themdadmcommand is used to manage and monitor RAID devices on Linux. To create a new RAID array, the--createoption is used, followed by several parameters:

/dev/md0: The name of the RAID device to be created.

--level=1: Specifies RAID level 1 (mirroring).

--raid-devices=2: Indicates the number of active devices (two in this case) to be used in the RAID array.

/dev/xvdd1 /dev/xvdd2: The two block devices that will form the RAID-1 array.

--spare-devices=1 /dev/xvdd3: Specifies one spare device (/dev/xvdd3). A spare device is used to automatically replace a failed device in the RAID array.

Option Analysis:

A.Incorrect because it specifies RAID level 5 (--level=5), which requires at least three devices and does not match the requirement for RAID-1.

B.Incorrect because it does not include the--spare-devices=1option, meaning there is no spare device included in this configuration.

C.Correct as it specifies RAID-1 (--level=1), two active devices (--raid-devices=2), and one spare device (--spare-devices=1).

D.Incorrect because it specifies RAID level 0 (--level=0), which is a striped set (no redundancy), not a mirrored set (RAID-1).

Oracle Linux Reference:For more detailed information aboutmdadmand RAID configurations in Oracle Linux 8, refer to the following Oracle Linux documentation:

Oracle® Linux 8 Managing Storage Devices - RAID Configuration

Oracle® Linux 8 mdadm Manual

These references provide comprehensive details on RAID levels,mdadmcommand syntax, and options for creating and managing RAID arrays in Oracle Linux.

Option B (Correct):The-Ior--interpretoption inausearchconverts the numerical system call numbers into their corresponding text names, making the output easier to understand.

Option C (Correct):The-scoption specifies the system call by name (mkdir), which helps in finding audit logs related to that particular system call in text format.

Option A, D, E (Incorrect):These options do not specifically translate the numeric system call numbers into human-readable text. OptionAfilters by the numeric ID,Dis an invalid option, andEreverses the search order but does not affect the format.

Oracle Linux Reference:Refer to:

Oracle® Linux 8: Auditing and System Logs

man ausearchfor more details on audit search and interpretation commands.

To remove a physical volume (PV) from a volume group (VG), it must first be removed using thevgreducecommand. This operation ensures that the VG no longer contains any references to the PV being removed.

Explanation of Answer D:A physical volume can be removed if there are no active logical volumes (LVs) on the VG that require space from that PV. If the LV is inactive, the PV can be safely removed from the VG.

Option A (Correct):In rsyslog, afilteris used to determine which messages should be selected for further processing. Filters can be based on different criteria such as facility, severity, or specific message content.

Option B (Correct):Anactionin rsyslog defines what to do with messages that match a filter. Actions can include writing to a log file, sending to a remote server, running a script, etc.

Option C (Incorrect):A parser is not typically a component for creating a new rsyslog rule; it is involved in interpreting message formats.

Option D (Incorrect):A module in rsyslog is a loadable component that provides additional capabilities, such as support for different protocols or output formats. It is not a direct component of a logging rule.

Option E (Incorrect):Security policy is unrelated to the basic components used for defining rsyslog rules.

Oracle Linux Reference:Refer to:

Oracle® Linux 8: Configuring Rsyslog

Explanation of Answer E:This option correctly matches the Kubernetes components with their descriptions:

Kubectl- d. Command-line interface used to control Kubernetes

Etcd- f. Stores configuration data relating to the cluster

Kubelet- c. Agent that allows nodes to communicate with the API

Kube-proxy- e. Performs networking functions and routes network traffic

Kube-apiserver- a. Processes and validates requests and performs operations

Kube-scheduler- b. Determines where containers should run based on resource availability

Understanding the Command:

$ podman run --name=oracleshell -it oraclelinux:8-slim

(Note: The image is likely oraclelinux:8-slim without a space.)

podman run:Creates and starts a new container.

--name=oracleshell:Assigns the name oracleshell to the container.

-it:Runs the container in interactive mode with a pseudo-TTY.

oraclelinux:8-slim:Specifies the image to use.

Option A: The container creates and starts an interactive shell.

Explanation:

The -it option runs the container interactively.

If no command is specified, it executes the default command in the image (usually /bin/bash).

This provides an interactive shell inside the container.

Oracle Linux Reference:

Oracle® Linux 8: Managing Containers-Running Containers Interactively:

"You can run a container in interactive mode using the -i and -t options together."

Option D: The container is created and started in a single command.

Explanation:

The podman run command handles both creation and starting of the container.

There's no need to create the container separately.

Oracle Linux Reference:

Oracle® Linux 8: Managing Containers-Creating and Running Containers:

"The podman run command creates and starts a container in one operation."

Why Other Options Are Incorrect:

Option B:The container does not need to pre-exist; podman run creates it if it doesn't exist.

Option C:If the image doesn't exist locally, podman will attempt to pull it from the registry.

Oracle Linux Reference:

Oracle® Linux 8: Managing Containers-Pulling Images:

"If you attempt to run a container with an image that does not exist locally, Podman automatically pulls the image from a registry."

Option E:The container is not removed upon exit unless the --rm option is used.

Oracle Linux Reference:

Oracle® Linux 8: Managing Containers-Automatically Removing Containers:

"Use the --rm option to automatically remove the container when it exits."

Conclusion:

Correct Options:A, D

Summary:The command creates and starts a new container named oracleshell and opens an interactive shell session inside it.

Explanation of Answer C:Bothatandbatchcan accept commands from standard input or from a file specified using the-foption. This allows scheduling of tasks by providing the commands directly or reading them from a file.

Explanation of Answer E:Theatcommand schedules a one-time task to run at a specified time. It is used to execute commands once at a particular time in the future.

Option A (Correct):Boot parameters are set in/etc/default/grubunder theGRUB_CMDLINE_LINUXdirective. After modifying this file, thegrub2-mkconfigcommand must be run to apply changes.

Option C (Correct):The/boot/loader/entries/directory contains configuration files for each kernel version, which store the boot parameters separately.

Option B (Incorrect):Boot parameters specified at the GRUB command line are not persistent across reboots unless added to the configuration file.

Option D (Incorrect):Parameters set from the GRUB menu are temporary and do not apply to subsequent reboots.

Oracle Linux Reference:Refer to:

Oracle® Linux 8: Configuring GRUB2

Understanding the anacrontab Entries:

The /etc/anacrontab file contains the following variables and job definitions:

SHELL=/bin/sh

PATH=/sbin:/bin:/usr/sbin:/usr/bin

MAILTO=root

# the maximal random delay added to the base delay of the jobs

RANDOM_DELAY=45

# the jobs are started during the following hours only

START_HOURS_RANGE=3-22

# period in days delay in minutes job-identifier command

1 5 dailyjob nice run-parts /etc/cron.daily

7 25 weeklyjob nice run-parts /etc/cron.weekly

@monthly 45 monthlyjob nice run-parts /etc/cron.monthly

Variables Explained:

RANDOM_DELAY=45

Specifies that arandom delaybetween 0 and 45 minutes is added to the base delay of each job.

START_HOURS_RANGE=3-22

Jobs are allowed to start only between03:00 (3 AM)and22:00 (10 PM).

Job Delays Calculated:

First Job (dailyjob):

Base Delay:5 minutes

Random Delay:0 to 45 minutes

Total Delay:5 + (0 to 45) =5 to 50 minutes

Second Job (weeklyjob):

Base Delay:25 minutes

Random Delay:0 to 45 minutes

Total Delay:25 + (0 to 45) =25 to 70 minutes

Third Job (monthlyjob):

Base Delay:45 minutes

Random Delay:0 to 45 minutes

Total Delay:45 + (0 to 45) =45 to 90 minutes

Option B: Jobs defined in this anacrontab file can be executed between 15:00 and 22:00

Explanation:

The START_HOURS_RANGE=3-22 setting allows jobs to start between03:00 and 22:00.

Therefore, it's true that jobscan be executed between 15:00 (3 PM) and 22:00 (10 PM).

This statement is correct because the specified time range falls within the allowed start hours.

Oracle Linux Reference:

Oracle® Linux 8: Scheduling Tasks- Section on "Anacron Configuration Files":

"The START_HOURS_RANGE variable defines the time window during which Anacron jobs can run."

Option C: Scripts run by the third job are delayed between 45 and 90 minutes.

Explanation:

The third job (monthlyjob) has abase delay of 45 minutes.

With a RANDOM_DELAY of up to 45 minutes, thetotal delaybefore execution is between45 and 90 minutes.

Therefore, this statement is accurate.

Oracle Linux Reference:

Oracle® Linux 8: Scheduling Tasks- Section on "Understanding Anacron Job Delays":

"Each job's delay is calculated by adding its defined delay to a random value between 0 and RANDOM_DELAY."

Why Other Options Are Not Correct:

Option A:Scripts run by the first job are delayed between 11 and 45 minutes.

Explanation:

The first job (dailyjob) has a total delay between5 and 50 minutes(5-minute base delay plus up to 45 minutes random delay).

Therefore, the statement specifying11 to 45 minutesis incorrect.

Option D:Jobs defined in this anacrontab file are randomly delayed by up to 51 minutes.

Explanation:

The maximum random delay is set by RANDOM_DELAY=45, so the random delay is up to45 minutes, not 51.

Therefore, this statement is false.

Option E:Scripts run by the second job are delayed between 31 and 70 minutes.

Explanation:

The second job (weeklyjob) has a total delay between25 and 70 minutes(25-minute base delay plus up to 45 minutes random delay).

The statement specifies a delay between31 and 70 minutes, which is incorrect because the minimum delay is 25 minutes.

Conclusion:

Options B and C are correct based on the configuration specified in /etc/anacrontab. They accurately reflect the possible execution times and delays for the jobs defined.

Explanation of Answer C:When configuring SSH, the command-line options take the highest precedence. Any configuration specified directly on the command line will override settings in user-specific (~/.ssh/config) or system-wide configuration files (/etc/ssh/ssh_config).

Option A (Correct):The rule is applied to both IPv4 and IPv6 packets. Theinettable is used for filtering both IPv4 and IPv6 traffic, and since the rule is added to theinettable, it affects both IP versions.

Option E (Correct):The rule drops TCP packets inbound on port 80. The rule specifies theinputchain in thefiltertable, and it drops (drop) all TCP traffic (tcp) destined for port 80 (dport 80), which means any incoming TCP traffic on port 80 will be dropped.

Option B (Incorrect):The command does not automatically update the configuration on disk; the rule is applied immediately in memory but does not persist across reboots unless explicitly saved.

Option C (Incorrect):The rule specifies TCP packets only, not all traffic. Therefore, it does not drop traffic for protocols other than TCP.

Option D (Incorrect):Although this statement is correct, it is less specific than Option A, which is more accurate because it mentions both IP versions.

Option F (Incorrect):The rule applies to inbound traffic, not outbound, so it does not drop outbound traffic.

Oracle Linux Reference:Refer to:

Oracle® Linux 8: Managing Firewall Rules with nftables

Explanation of Answer B:When executingnmcli con mod ens4 ipv4.method auto, theipv4.methodparameter is set toauto, which configures the interface to obtain its IP address using DHCP. This means that theBOOTPROTOvalue in the configuration is set todhcp.

Explanation of Answer D:Whenipv4.methodis set toauto(DHCP), any static IP address specified inIPADDRis considered null because the interface will now obtain its IP address from a DHCP server, making the manually set IP address irrelevant.

Understanding the Automounter Configuration:

/etc/auto.master:

/net -hosts

/- auto.direct ro

The /- auto.direct ro line indicates:

Mount Point Prefix:/ (direct mounts)

Map File:auto.direct

Global Mount Options:ro (read-only)

/etc/auto.direct:

/nfs1 host01:/export/share1

/nfs2 -sync host01:/export/share2

/nfs3 host02:/export/share3

/nfs1 and /nfs3:

No specific mount options in auto.direct.

Inherit the ro option from /etc/auto.master.

/nfs2:

Specifies -sync option in auto.direct.

Inherits ro from /etc/auto.master.

Mount options are ro,sync.

Mount Options Resolution:

Global Options (ro) apply to all entries unless overridden.

Per-Entry Options in auto.direct override or supplement global options.

Effective Mount Options:

/nfs1:

ro (from /etc/auto.master)

Default NFS options (async unless sync is specified)

/nfs2:

ro (from /etc/auto.master)

sync (specified in auto.direct)

/nfs3:

ro (from /etc/auto.master)

Default NFS options (async)

Oracle Linux Reference:

Oracle® Linux 8: Configuring File Systems-Automounter Configuration:

"Options specified in the master map apply to all entries in the map unless overridden by entries in the map itself."

NFS Default Options:

"By default, NFS mounts are asynchronous (async) unless the sync option is specified."

Conclusion:

/nfs1 and /nfs3:Mounted with ro,async.

/nfs2:Mounted with ro,sync.

Correct Option:A

Option D (Correct):The commandsetfacl --modify user:user2:r-x my_directorysets an Access Control List (ACL) entry that givesuser2read (r) and execute (x) permissions onmy_directory. The execute (x) permission is required to allow navigation into the directory.

Option A (Incorrect):The--defaultoption would set the default ACL for future files or directories created withinmy_directory, not the directory itself.

Option B (Incorrect):This option gives only read (r) permission, but without execute (x) permission,user2cannot navigate into the directory.

Option C (Incorrect):The-xoption is used to remove an ACL entry, not modify it.

Option E (Incorrect):This modifies the ACL for the grouptestinstead of the useruser2.

Oracle Linux Reference:Refer to:

Oracle® Linux 8: Using Access Control Lists

Option B (Correct):Thefdisk -lcommand lists information about all available disks, including their sizes, partition tables, and partition details.

Option E (Correct):fdiskcannot handle disks larger than 2 TB because it is limited to the Master Boot Record (MBR) partitioning scheme. To manage larger disks (over 2 TB), the GUID Partition Table (GPT) is required, andfdiskdoes not fully support GPT.

Option A (Incorrect):fdiskdoes not support HFS (Hierarchical File System, used by macOS). It primarily supports MBR and has limited support for GPT.

Option C (Incorrect):fdiskdoes not support partitioning disks larger than 2 TB with GPT;gdiskorpartedshould be used instead.

Option D (Incorrect):fdiskdoes not divide logical devices into block disks called partitions; it operates on physical storage devices to create partitions.

Oracle Linux Reference:Refer to:

Oracle® Linux 8: Managing Disks and Partitions

man fdiskfor more details on the usage and limitations of thefdiskutility.