LPI 102-500 Dumps Questions Answers

T The ssh command is used to connect to a remote host using the Secure Shell (SSH) protocol, which provides encrypted and authenticated communication. The ssh command has the following syntax:

ssh [options] [user@]hostname [command]

The options can modify the behavior of the ssh command, such as specifying the port number, the identity file, the cipher, the compression, and the timeout. The user@hostname specifies the username and the hostname of the remote host to connect to. The command is an optional argument that specifies the command to execute on the remote host.

To connect to the remote host example.com which has OpenSSH listening on TCP port 2222, two possible options are:

B. ssh -p 2222 example.com: This option uses the -p flag to specify the port number of the remote host. The -p flag is a shortcut for the Port option, which can also be used with the -o flag.

C. ssh -o Port=2222 example.com: This option uses the -o flag to specify a configuration option for the ssh command. The -o flag can be followed by any option that is valid in the ssh_config file, such as Port, IdentityFile, Cipher, Compression, and ConnectTimeout. The Port option sets the port number of the remote host.

The other options in the question are not correct for this task. The --port option is not a valid option for the ssh command. The GatewayPort option is used to specify whether remote hosts are allowed to connect to local forwarded ports. The example.com:2222 syntax is not valid for the ssh command.

References:

LPI 102-500 Exam Objectives, Topic 110.1: Perform security administration tasks

LPI 102-500 Study Guide, Chapter 10: Securing Your System, Section 10.1: Configuring SSH

ssh man page

opic 7, Misc Questions New

The command systemctl list-timers shows all active systemd timers, which are units that can be used to schedule the execution of other units at specific times or after certain intervals. The output of the command includes the following columns:

NEXT: The next time the timer will trigger.

LEFT: The time left until the next trigger.

LAST: The last time the timer triggered.

PASSED: The time passed since the last trigger.

UNIT: The name of the timer unit.

ACTIVATES: The name of the unit that is activated by the timer.

For example, the following output shows two active timers: apt-daily.timer and apt-daily-upgrade.timer, which are used to perform automatic updates on Debian-based systems.

NEXT LEFT LAST PASSED UNIT ACTIVATES Mon 2021-11-15 06:00:00 UTC 9h left Sun 2021-11-14 06:00:01 UTC 20h ago apt-daily.timer apt-daily.service Mon 2021-11-15 06:23:51 UTC 9h left Sun 2021-11-14 06:23:51 UTC 20h ago apt-daily-upgrade.timer apt-daily-upgrade.service 2 timers listed.

The other commands in the options are either invalid or unrelated to systemd timers:

systemctl-timer show is not a valid command. To show the details of a specific timer unit, the command systemctl show unit.timer can be used, where unit is the name of the unit that is activated by the timer.

timectl list is not a valid command. To list the available time zones, the command timedatectl list-timezones can be used. To list the current time and date settings, the command timedatectl can be used without any arguments.

systemctl -t is not a complete command. To list all units of a specific type, the command systemctl -t type can be used, where type is the name of the unit type, such as service, timer, socket, etc.

timeq is not a valid command. It may be confused with the time command, which measures the time taken by a command or program to execute.

References:

LPIC-1 Exam 102 Objectives, Topic 107: Administrative Tasks, Subtopic 107.2: Automate system administration tasks by scheduling jobs, Weight: 4, Key Knowledge Areas: Use cron and systemd timers to run jobs at regular intervals and to use anacron to manage system cron jobs. Objective: Use systemd timers to run jobs at regular intervals and to use anacron to manage system cron jobs.

LPIC-1 Exam 102 Learning Materials, Topic 107: Administrative Tasks, Subtopic 107.2: Automate system administration tasks by scheduling jobs, Section 107.2.3: systemd timers, Page 21-22.

The sudo configuration file (/etc/sudoers) defines the rules for granting privileges to users or groups to execute commands as another user, usually the superuser or root. The format of the sudo configuration file is as follows:

user_list host_list=effective_user_list tag_list command_list

The user_list specifies the users who can run the commands, the host_list specifies the hosts where the commands can be run, the effective_user_list specifies the user as whom the commands can be run, the tag_list specifies some options for the commands, and the command_list specifies the commands that can be run.

In this case, the user_list is jane, the host_list is ANY (meaning any host), the effective_user_list is not specified (meaning root by default), the tag_list is NOPASSWD or PASSWD (meaning whether a password is required or not), and the command_list is /bin/kill, /bin/id, or /sbin/fdisk.

Therefore, the sudo configuration file allows jane to run /bin/kill, /bin/id, or /sbin/fdisk as root on any host, but with different password requirements. Specifically:

Jane can run /bin/kill without specifying a password, because the tag_list is NOPASSWD for this command. This means that jane can execute sudo /bin/kill and the command will run as root without asking for any password. This makes option D true.

Jane can run /bin/id without specifying a password, because the tag_list is also NOPASSWD for this command. This means that jane can execute sudo /bin/id and the command will run as root without asking for any password. This makes option E true.

Jane can run /sbin/fdisk after specifying her password, because the tag_list is PASSWD for this command. This means that jane can execute sudo /sbin/fdisk and the command will ask for jane’s password before running as root. This makes option C true.

The other options are false because:

Jane cannot run /bin/id only after specifying her password, because the tag_list is NOPASSWD for this command. This makes option A false.

Jane cannot run /sbin/fdisk after specifying root’s password, because the password that is required is jane’s password, not root’s password. This makes option B false.

References:

LPI Linux Essentials: 1.4. Using sudo

LPI Linux Administrator: 102.5. Use Debian package management

LPI Linux Engineer: 201.1. Measure and Troubleshoot Resource Usage

LPI Linux Professional Certification Program