hardmulti selectObjective-mapped

A development team signs branch-router firmware before deployment. The same code-signing private key is stored on two build servers, and a compromise of either server would let an attacker sign malicious updates that look legitimate. Which two changes best reduce the cryptographic risk while preserving the ability to sign trusted releases? Select two.

Question 1hardmulti select
Full question →

A development team signs branch-router firmware before deployment. The same code-signing private key is stored on two build servers, and a compromise of either server would let an attacker sign malicious updates that look legitimate. Which two changes best reduce the cryptographic risk while preserving the ability to sign trusted releases? Select two.

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Move the signing private key into a non-exportable hardware security module or managed key service.

Keeping the signing key in an HSM or managed key service prevents attackers from copying it off the server. If the build host is compromised, the attacker still cannot easily extract the private key. That preserves trusted signing while materially reducing the chance of key theft and unauthorized firmware signing.

B

Best answer

Use separate signing keys for each product line or release environment to limit blast radius.

Separate keys reduce the impact of a compromise because one stolen key cannot sign every product or environment. If a single build path is abused, the attacker is constrained to a smaller trust boundary. This is a strong key-management control when operationally feasible.

C

Distractor review

Encrypt the build server disks with full-disk encryption so the private key stays protected.

Full-disk encryption protects data at rest, but it does not stop an attacker who has already compromised the running server. Once the system is booted and unlocked, the key can still be accessed by malware or an interactive intruder. It reduces theft risk, not signing-key exposure during operation.

D

Distractor review

Store the private key in a read-only artifact repository so all build agents can access it.

Putting the private key in a repository makes distribution easier, but it increases exposure dramatically. Read-only access does not matter if an attacker can clone or exfiltrate the repository contents. A private signing key should be tightly protected, not broadly shared.

E

Distractor review

Replace the signing process with file hashes and checksums to verify release integrity.

Hashes and checksums can show that a file changed, but they do not prove authenticity or source. An attacker who can replace the firmware can also replace the hash value. Digital signatures are needed when the goal is trusted origin and tamper evidence.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Move the signing private key into a non-exportable hardware security module or managed key service. — The best improvements are to isolate the signing key from export and to reduce how many releases depend on one key. An HSM or managed key service makes key extraction much harder, even if the build server is breached. Separate keys also contain damage by limiting what one compromised key can sign. Together, these changes preserve trusted signing while sharply reducing the blast radius of a compromise. Why others are wrong: Disk encryption, read-only repository storage, and hashes all fail to solve the main problem: protecting a live signing key and preserving authenticity. Disk encryption only helps when the server is off. A repository makes the key easier to copy. Hashes verify integrity, but not who created the file. They are useful controls, but they do not replace hardened key management.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.