Which two steps are mutual between Cisco secure boot and UEFI secure boot? (Choose two.)

Question

Options

• Abootloader
• Boperating system
• Cmicroloader
• Dkemel
• Ehardware anchor

• A
  71% (32)
• C
  9% (4)
• D
  4% (2)
• E
  16% (7)

Explanation

Both Cisco Secure Boot and UEFI Secure Boot include a bootloader verification stage (A) and an operating system verification stage (B) in their chain of trust - these are the two steps shared across both frameworks, making them the correct answers.

Why the distractors are wrong:

• C (Microloader): Exclusive to Cisco's secure boot chain; it sits between the hardware anchor and the bootloader and has no equivalent stage in UEFI secure boot.
• D (Kernel): In Cisco's chain, the kernel is subsumed within the OS verification step rather than treated as a discrete, separately-named stage the way UEFI might handle it - making it non-mutual as a distinct step.
• E (Hardware anchor): This is Cisco-specific terminology for the silicon-level Trust Anchor Module (TAm); UEFI secure boot uses UEFI firmware with stored keys instead, so it's not a shared step.

Memory tip: Think of the middle of the boot chain - both frameworks must hand off from a bootloader to an OS, regardless of what comes before or after. Cisco adds proprietary steps on either end (hardware anchor → microloader before; kernel distinction after), while UEFI handles those differently. If you remember "the middle two are mutual," you'll lock in A and B every time.

No community discussion yet for this question.