The correct action is to change the UCS boot policy to use the 'VMware LUN' target type and ensure the LUN is presented correctly, as this directly resolves the ESXi host profile compliance failure for the boot device in UCS without disrupting boot functionality. This works because the host profile compliance check compares the boot device name seen by ESXi against the expected 'VMware LUN' identifier; a generic 'SAN Target' setting in the UCS boot policy causes a mismatch even though the host boots fine from the same LUN. On the Cisco DCCOR / CCNP Data Center Core 350-601 exam, this scenario tests your understanding of how UCS boot policies interact with VMware host profiles, specifically that compliance is name-based, not path-based—a common trap is thinking you must modify the host profile or change the LUN ID. The key insight is that the boot device name must match exactly, and UCS Manager allows you to set the target type to 'VMware LUN' to align with vSphere’s naming convention. Memory tip: "Match the name, not the path—VMware LUN fixes the mismatch."
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.
Your company integrates UCS B-Series blades with VMware vSphere using UCS Manager and vCenter. You have configured a UCS service profile with a boot policy that boots from SAN. The virtual infrastructure administrator reports that a new ESXi host (blade 6) fails to meet host profile compliance for the 'Boot Device' policy. The host profile requires the boot LUN to be set to 'VMware LUN' but the UCS boot policy uses a generic 'SAN Target' setting. The ESXi host boots and runs, but compliance checks fail. You cannot modify the host profile because it is managed by a separate team. Which action should you take to resolve the compliance failure while maintaining boot functionality?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Change the UCS boot policy to use the 'VMware LUN' target type and ensure the LUN is presented correctly
Option D is correct because the host profile compliance failure is caused by the UCS boot policy using a generic 'SAN Target' type instead of the 'VMware LUN' target type. By changing the boot policy to 'VMware LUN' and ensuring the correct LUN is presented, the ESXi host will boot from the same LUN but now the boot device name will match what the host profile expects, resolving the compliance check without affecting boot functionality.
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.
✗
Create a new vCenter cluster with a different host profile
Why it's wrong here
Overly complex and disruptive
✗
Use a local disk boot policy and install ESXi locally
Why it's wrong here
Changes boot method, may not be desired
✗
Request the host profile to be updated to accept generic SAN targets
Why it's wrong here
Cannot modify host profile as per stem
✓
Change the UCS boot policy to use the 'VMware LUN' target type and ensure the LUN is presented correctly
Why this is correct
Aligns with host profile requirement
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 'functional boot' and 'compliance check'—candidates may assume that because the host boots fine, no change is needed, but the question explicitly requires resolving the compliance failure while maintaining boot functionality, meaning the boot policy must be adjusted to match the host profile's expected target type.
Detailed technical explanation
How to think about this question
In UCS Manager, the boot policy's 'SAN Target' setting presents the boot LUN as a generic SCSI device, while the 'VMware LUN' setting uses a specific VMware-defined SCSI target identifier that vCenter's host profile recognizes as the expected boot device. Under the hood, the host profile compares the boot device's SCSI ID or path against a predefined pattern; using 'VMware LUN' ensures the LUN is exposed with the correct vendor/model string that matches the profile's compliance criteria. In real-world deployments, this mismatch often occurs when UCS boot policies are created without coordinating with vSphere host profile requirements, leading to compliance failures even though the host boots successfully.
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: Change the UCS boot policy to use the 'VMware LUN' target type and ensure the LUN is presented correctly — Option D is correct because the host profile compliance failure is caused by the UCS boot policy using a generic 'SAN Target' type instead of the 'VMware LUN' target type. By changing the boot policy to 'VMware LUN' and ensuring the correct LUN is presented, the ESXi host will boot from the same LUN but now the boot device name will match what the host profile expects, resolving the compliance check without affecting boot functionality.
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.
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 →
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.