The answer is a missing or unattached boot policy. This is correct because the boot policy is the configuration that tells the UCS Manager which boot parameters—specifically the target WWPN and LUN ID—to program into the server’s BIOS for a SAN boot. Even when the SAN zoning is correct and the vHBA WWPN is properly mapped, without a boot policy attached to the service profile, the BIOS receives no Fibre Channel boot target instructions, so the server simply does not know where to look for the boot LUN. On the Cisco DCCOR 350-601 exam, this scenario tests your understanding of the UCS boot chain: zoning and vHBA configuration are necessary but not sufficient; the boot policy is the final link that bridges SAN connectivity to the server’s firmware. A common trap is assuming that correct SAN zoning alone guarantees a boot, but the policy must explicitly define the target. Memory tip: “No policy, no boot—zoning gets you there, but the policy opens the door.”
350-601 Compute Practice Question
This 350-601 practice question tests your understanding of compute. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A data center engineer notices that a UCS B-Series blade server is failing to boot from a SAN LUN that is correctly mapped to the server's WWPN. The SAN switch shows that the LUN is accessible and the zone is configured correctly. The UCS Manager shows the server's vNIC is associated with a vHBA that has the correct WWPN, but the server's BIOS does not list the Fibre Channel boot target. Which configuration is most likely missing?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The boot policy is not defined or not attached to the service profile.
The boot policy defines the boot order and parameters (such as the SAN LUN target WWPN and LUN ID) for the server. If the boot policy is not defined or not attached to the service profile, the UCS Manager will not program the BIOS with the Fibre Channel boot target information, even though the SAN zoning and vHBA WWPN are correct. Without this policy, the server's BIOS has no instruction to attempt a SAN boot, resulting in the failure described.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The SAN connectivity policy is missing the Fibre Channel uplink pinning.
Why it's wrong here
SAN connectivity policies define uplink ports but not boot targets.
✗
The vNIC/vHBA placement policy is incorrectly set to 'Express' mode.
Why it's wrong here
Placement policies affect adapter placement, not boot.
✗
A QoS policy is not applied to the vHBA.
Why it's wrong here
QoS policies affect traffic prioritization, not boot.
✓
The boot policy is not defined or not attached to the service profile.
Why this is correct
UCS B-Series requires a boot policy to specify the boot order and target LUN.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between SAN connectivity (zoning, WWPN) and the boot policy configuration, trapping candidates who assume that correct zoning and vHBA setup alone are sufficient for SAN boot.
Detailed technical explanation
How to think about this question
In UCS Manager, the boot policy is a separate policy object that specifies the boot order (e.g., local disk, SAN, iSCSI) and includes the Fibre Channel target details (WWPN, LUN ID) for SAN boot. The service profile must reference this boot policy; otherwise, the BIOS will not receive the necessary boot parameters via the UCS management framework. A common real-world scenario is when a SAN LUN is correctly zoned and the vHBA is properly configured, but the engineer forgets to attach the boot policy to the service profile, leading to a 'No boot device found' error.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the 350-601 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Compute — This question tests Compute — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The boot policy is not defined or not attached to the service profile. — The boot policy defines the boot order and parameters (such as the SAN LUN target WWPN and LUN ID) for the server. If the boot policy is not defined or not attached to the service profile, the UCS Manager will not program the BIOS with the Fibre Channel boot target information, even though the SAN zoning and vHBA WWPN are correct. Without this policy, the server's BIOS has no instruction to attempt a SAN boot, resulting in the failure described.
What should I do if I get this 350-601 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An engineer is troubleshooting a UCS B-Series blade that fails to boot from SAN. Which TWO actions should be verified first? (Choose TWO.)
medium
✓ A.Verify that the vHBA WWPN is correctly zoned on the SAN switches.
✓ B.Confirm the boot policy includes the SAN target LUN.
C.Check the MAC address assigned to the vNIC.
D.Ensure the QoS policy for FC traffic is set to Platinum.
E.Verify the server's boot order lists local disk first.
Why A: Option A is correct because the vHBA WWPN must be properly zoned on the SAN switches to allow the blade to discover and connect to the storage target. Without correct zoning, the Fibre Channel initiator cannot communicate with the target, preventing SAN boot. This is a fundamental prerequisite for any Fibre Channel-based boot.
Variation 2. An engineer is troubleshooting a UCS B-Series server that fails to boot from SAN. The SAN boot LUN is correctly zoned and presented. The service profile has WWPNs configured. What is a likely cause?
medium
A.Server firmware mismatch
B.Missing vNIC template
C.VLAN mismatch
✓ D.Incorrect boot policy order
Why D: The SAN boot LUN is correctly zoned and presented, and the WWPNs are configured in the service profile, so the connectivity and identity are set. However, if the boot policy order is incorrect (e.g., the SAN boot target is listed after a local disk or another boot device), the server will attempt to boot from the wrong device first and fail to boot from the SAN. The boot policy defines the sequence of boot devices, and a misconfigured order is a common cause of boot failures in UCS B-Series.
Last reviewed: Jun 11, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This 350-601 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 350-601 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.