Verify the Downloads Before You Install
A free SY0-801 performance-based question on Hashing, Salting, and Digital Signatures. Read the scenario, complete the task, and submit — it grades instantly with an explanation, no account needed.
Performance-Based Question
Verify the Downloads Before You Install
Scenario
Dana, the IT lead at a small accounting firm, asked you to put the Ridgeline Scan and Ridgeline Agent tools on this Ubuntu workstation. You downloaded ridgeline-scan_3.2.0_amd64.deb, ridgeline-agent_1.8.4_amd64.deb and the rescue disk image ridgeline-rescue-3.2.0-amd64.iso from the vendor's download page into your Downloads folder. The ISO is for next week's rebuild of the spare server. SHA256SUMS, the vendor's list of checksums, is in the same folder. You copied it from the vendor's separate security page. The vendor has warned that its download page was briefly altered, so some of the files you downloaded may not be its real build. Nothing has been installed yet. Check every download against SHA256SUMS, and leave SHA256SUMS exactly as the vendor published it: it is the reference, so don't change anything in it (not one line, not a comment), and don't move or delete it. Install each package that passes. Delete any file that fails, so nobody installs it by mistake. Don't try to repair a bad file: Dana will ask the vendor for a new copy. The workstation is at its boot menu. Log in as Bench Technician with the password Tech!23; sudo asks for the same password. Terminal, Files and Text Editor are all on the dock. Checking the files and installing a package are Terminal jobs: Files and Text Editor cannot hash a file or install a .deb (Text Editor can read SHA256SUMS, and Files can delete a file).
These instructions stay visible beside the lab while you work.You can reread these instructions in the lab at any time.
Study this section
Lessons and practice for Section 6 — Hashing, Salting, and Digital Signatures.