Embedded Files
Q1 Local Repository Configuration and Verification
Q1 Local Repository Configuration and Verification
A development team requires access to a local software archive. Configure your system to utilize an existing repository network path, ensuring it persists across reboots and functions correctly without cryptographic signatures.
Requirements
Configure a new repository named exam-baseos.
Set the repository base URL to http://content.example.com/rhel10/x86_64/dvd/BaseOS.
Ensure that GPG signature verification is disabled for this specific repository so that package installations do not fail due to missing keys.
Clear any existing package metadata cache and verify that the repository is active and recognized by the package manager.
Solution
Add the Repository URL
sudo dnf config-manager --add-repo="http://content.example.com/rhel10/x86_64/dvd/BaseOS"
Direct to repository directory
cd /etc/yum.repos.d/
List all content to check repository name
ls
Open repository configuration file
sudo vim /etc/yum.repos.d/content.example.com_rhel10_x86_64_dvd_BaseOS.repo
Disable GPG Checking and change repository name
Press Esc --> I
Add/Edit line gpgcheck=0
Edit [content.example.com_rhel10_x86_64_dvd_BaseOS] to [exam-baseos]
Press Esc --> :wq --> Enter
Clear the Package Cache
sudo dnf clean all
Verify
sudo dnf repolist
[Cleanup] Delete the repository
rm -f content.example.com_rhel10_x86_64_dvd_BaseOS.repo
Q2 Package Auditing and File Provenance
Q2 Package Auditing and File Provenance
An unidentified diagnostic binary or software package is suspected of altering system behaviour. You are required to trace the origin of specific commands; audit installed files and inspect uninstalled package headers to verify their safety.
Requirements
Determine the exact absolute path of the mkdir executable and identify the exact name and version of the RPM package that installed it.
The package gnome-remote-desktop is installed. Generate a complete list of all files installed by this package to audit its file footprint.
Check if the gnome-remote-desktop package executed any pre-installation or post-installation shell scripts when it was deployed.
Locate any uninstalled .rpm file residing inside the system directories. Without extracting or installing it, list its entire internal file structure to verify its contents.
Solution
mkdir
Locate the command's physical file path
which mkdir
Query the RPM database using that file path
rpm -qf /usr/bin/mkdir
gnome-remote-desktop
Check if the software package is installed by name
rpm -q gnome-remote-desktop
View content of RPM package without extracts it
rpm -ql gnome-remote-desktop
Find the hidden setup scripts of the software
If it outputs nothing, it means the software was simple enough to not require setup scripts.
rpm -q --scripts gnome-remote-desktop
uninstalled .rpm file
Find RPM file
find / -name "*.rpm" 2>/dev/null
View content of RPM package without extracts it
rpm2cpio.rpm | cpio -tv
Q3 Bulk Software Deployment and Dependency Management
Q3 Bulk Software Deployment and Dependency Management
The system must be prepared as a development workstation. You must locate, inspect, and deploy a suite of development tools using the system package manager.
Requirements
Search the package database to find all available packages or information related to the term python.
Locate the specific package group responsible for Development Tools. Inspect its contents to ensure it contains core compilation utilities.
Install the Development Tools package group onto the system.
Install an individual package named python3-devel if it is not already pulled in by the group.
Solution
Search the package related to the python.
dnf list "python*"
dnf search python
Inspecting group's Contents
sudo dnf group info "Development Tools"
Install the Development Tools
sudo dnf group install "Development Tools"
Install python3-devel
sudo dnf install python3-devel
Cleanup
sudo dnf remove python3-devel
sudo dnf group remove "Development Tools"
Page updated
Google Sites
Report abuse