SCA in SUSE Linux Enterprise Server 15 (2025 Update) Free Sample Questions

The correct procedure is to first initialize the new disk as a physical volume using pvcreate. Then, add this new physical volume to the existing volume group with vgextend. Finally, extend the logical volume to use the newly available space in the volume group using lvextend -l +100%FREE. Note that this only extends the logical volume; the filesystem on it must be resized separately (e.g., with resize2fs or xfs_growfs).

The journalctl command uses the -p flag to filter by priority. A single numeric value (e.g., -p 2) will show all messages with that priority level and higher (more severe). The priorities are: emerg (0), alert (1), crit (2), err (3), warning (4), notice (5), info (6), debug (7). Therefore, -p 2 shows critical, alert, and emergency messages. The -b flag restricts the output to the current boot.

The After= directive ensures that this service unit will only be started after the network-online.target and the specified mount unit have been successfully started. This enforces the order of operations.

Requires= specifies a hard dependency. If network-online.target or the mount unit fails to start, this service unit will also fail. remote-fs.target is the standard target that is reached after all remote filesystems (like NFS) listed in /etc/fstab are mounted.

This statement is false. Btrfs snapshots are lightweight and use Copy-on-Write (CoW) technology. When a snapshot is created, it initially consumes almost no additional space. It only starts to consume space as files in the original subvolume are modified or deleted, as the snapshot needs to retain the original data blocks.

A systemd timer unit is the modern and recommended method on SLES 15 for complex scheduling. A single .timer file can be configured with OnBootSec=10min to handle the initial run and OnUnitActiveSec=6h to handle the recurring schedule. This provides more robust control and better logging integration with the systemd journal compared to cron or at.

The btrfs balance command is used to rebalance data across devices in a Btrfs filesystem. Running btrfs balance start /data without any filters will re-stripe all data and metadata chunks across the available devices, leading to a more even distribution. This is particularly useful after adding or removing devices.

The find command uses the -perm option to search for files with specific permissions. The SUID bit corresponds to the octal value 4000. Using a forward slash (/4000) tells find to match files where any of the specified permission bits are set. This is the correct way to find all files with the SUID bit, regardless of their other permissions.

Btrfs natively integrates volume management and filesystem capabilities. Creating a Btrfs filesystem with RAID1 profile (mkfs.btrfs -d raid1 -m raid1 /dev/sdb /dev/sdc) directly meets the mirroring requirement. Furthermore, Btrfs provides built-in, highly efficient Copy-on-Write snapshots, which perfectly satisfies the need for instantaneous, space-efficient backups. This single technology elegantly solves both requirements.

When adding a new repository with zypper addrepo, it is often added in a disabled state by default as a safety measure. The administrator must explicitly enable it using the command zypper modifyrepo --enable new_repo (or -e). Until it is enabled, zypper will not use it to search for or install packages.

The renice command is used to alter the scheduling priority of a running process. A higher nice value (from -20 to 19) means a lower priority. To decrease the priority of the process, you must provide a positive nice value. The command renice 10 25123 sets the nice value of PID 25123 to 10, making it yield CPU time more readily to other processes. A regular user can only increase the nice value (decrease priority), while root can also decrease the nice value (increase priority).