Pass the LPIC-2 Certified Linux Engineer 202-450 Questions and answers with ExamsMirror

The netfilter table that contains built-in chains called INPUT, OUTPUT and FORWARD is the filter table. The filter table is the default table for netfilter and iptables, and it is used to filter packets based on their source, destination, protocol, port, state, etc. The filter table has three built-in chains, which correspond to the netfilter hooks that trigger them:

INPUT: This chain is used to process incoming packets that are destined for the local system. The packets must have passed through the PREROUTING chain and the routing decision before reaching this chain.

OUTPUT: This chain is used to process outgoing packets that are originated from the local system. The packets must have passed through the routing decision before reaching this chain.

FORWARD: This chain is used to process packets that are neither originated from nor destined for the local system, but are routed through the system. The packets must have passed through the PREROUTING and POSTROUTING chains and the routing decision before reaching this chain.

The filter table can have user-defined chains as well, which can be created with the -N option of the iptables command. User-defined chains can be used to organize rules and simplify the management of the firewall. Rules can be added to any chain in the filter table with the -A option of the iptables command, and they can specify the target action to take if the packet matches the rule. The target can be one of the following:

ACCEPT: This target allows the packet to pass through the chain and continue to the next netfilter hook.

DROP: This target drops the packet and stops its processing.

REJECT: This target drops the packet and sends back an error message to the sender.

LOG: This target logs the packet information to the kernel log and continues to the next rule in the chain.

RETURN: This target returns from the current chain to the calling chain, or to the default policy if there is no calling chain.

A user-defined chain name: This target jumps to the user-defined chain and executes its rules until a terminal target (ACCEPT, DROP, REJECT, or RETURN) is reached or the end of the chain is reached.

References:

A Deep Dive into Iptables and Netfilter Architecture

Iptables Tutorial 1.2.2

How To List and Delete Iptables Firewall Rules

The ldappasswd command is used to change user passwords in an OpenLDAP directory. It allows users to change their own passwords or administrators to change other users’ passwords. It requires the user to bind to the LDAP server with the current password and then specify the new password using various options. The ldappasswd command follows the same general syntax as the other OpenLDAP tools and supports various options to modify the password operation. The ldappasswd command is part of the OpenLDAP software package and is compliant with the LDAP Password Modify Extended Operation defined in RFC 3062. References:

How To Change Account Passwords on an OpenLDAP Server

OpenLDAP ACL to allow users to change their password

[ldappasswd(1) - Linux man page]

[RFC 3062 - LDAP Password Modify Extended Operation]

The status parameter in an OpenVPN server configuration file specifies the name of a file where OpenVPN writes information about the current status of the VPN tunnel, such as the time, bytes sent and received, and the IP address and port of each connected client. This file can be used to monitor the VPN activity and troubleshoot any issues. The file does not contain any information about errors and warnings generated by the openvpn daemon, as those are written to the log file specified by the log or log-append parameter. The file also does not contain any historical information about the clients who have connected at some point, as it only shows the current state of the VPN tunnel. 

https://openvpn.net/community-resources/reference-manual-for-openvpn-2-4/

https://openvpn-status.readthedocs.io/en/latest/api.html

The samba-tool testparm command is a simple test program to check a Samba configuration file for internal correctness. It verifies that the file can be parsed and loaded by Samba without errors or warnings. If the command reports no problems, it means that the configuration file is valid and can be used by Samba. However, this does not guarantee that the services defined in the configuration file will operate as expected, or that the Samba services are running or enabled on the system. The command also does not check the firewall or netfilter rules on the Samba server, or the version of the configuration file used by the running Samba processes. Therefore, the only correct answer is A.

 The Apache HTTPD directive that enables HTTPS protocol support is SSLEngine on. This directive activates the SSL/TLS protocol engine for the current virtual host. HTTPS is a secure version of HTTP that uses SSL/TLS to encrypt the communication between the client and the server. To enable HTTPS, the server must have a valid SSL certificate and a corresponding private key, and configure them using the SSLCertificateFile and SSLCertificateKeyFile directives123 References:

LPIC-2 Overview

LPIC-2 202-450

SSL/TLS Strong Encryption: How-To - Apache HTTP Server Version 2.4