IBM AIX v7.3 Administrator Specialty Free Sample Questions

AIX 7.3 and later versions increasingly rely on YUM (or its successor DNF) to manage open-source RPM packages. These tools are designed to automatically resolve and install dependencies from configured repositories, which is the most efficient and reliable method. Manually installing dependencies is tedious and error-prone. The installp command is for AIX-native packages, not RPMs.

The chdev command is used to modify device attributes. By default, it only changes the running configuration. To make the change permanent so that it is applied after a reboot, the -P flag must be used. This flag updates the device's attributes in the Object Data Manager (ODM) database.

The /etc/inittab file is the primary control file for the init process, defining which processes and scripts to run at different run levels during system startup.

The /etc/inittab file often calls scripts located in the /etc/rc.d/ directory structure (like /etc/rc.d/rc2.d/) to start and stop services for a specific run level. A faulty script here is a common cause of boot hangs.

This solution correctly maps each requirement to the appropriate AIX tool: mksysb is for creating a bootable OS backup (Req 1). savevg is designed for backing up non-root volume groups (Req 2). snap -a gathers comprehensive system configuration data for reporting (Req 3). cron is the standard utility for automating recurring tasks (Req 4).

The -f (force) flag with stopsrc sends a SIGKILL (kill -9) signal to the subsystem process but does so under the control of the SRC. This ensures that the SRC updates its status for the subsystem to 'inoperative' and performs necessary cleanup. This is the preferred method over using a manual kill -9, which would leave the SRC with an incorrect status for the subsystem.

This statement is false. The at command is used to schedule a command or script to be executed once at a specific time in the future. For recurring tasks, the cron daemon and crontab files are used.

To achieve maximum redundancy, each copy of a logical partition should reside on a different physical volume. By creating three copies of the logical volume (mklv -c 3 ...) and ensuring the volume group has a strict inter-disk allocation policy, LVM will place one copy on hdisk1, one on hdisk2, and one on hdisk3. This configuration can survive the failure of any two disks.

The correct procedure is to first increase the size of the underlying logical volume (datalv) using the extendlv command. Once the logical volume has been expanded, the chfs command is used to grow the JFS2 file system to utilize the newly available space on the logical volume.

A Physical Partition (PP) is the fundamental building block of LVM storage on a physical volume (disk). The size of the PPs is defined when the volume group is created. Logical Volumes are created from a collection of PPs, and there is typically a one-to-one mapping between a Logical Partition (LP) and a Physical Partition (PP).

The correct command is find / -user root -perm -4000 -ls. Let's break it down: find / starts the search from the root directory. -user root specifies that the file must be owned by root. -perm -4000 searches for files where the SUID bit (octal value 4000) is set. The hyphen prefix means that at least this permission bit must be set. -ls provides a detailed listing of the found files.