A customer is evaluating device profiles on a CX 6300 switch. The test device has the following attribute: MAC address = 81:cd:93:13:ab:31 The test device needs to be assigned the "iot-prod" role…

Question

Options

• AEnter the command port-access onboarding-method precedence to set device profiles with a
• BEnter the command port-access device-profile mode block-until-profile-applied globally
• CEnter the command port-access fallback-role iot-default globally
• DEnter the command port-access onboarding-method precedence to set device profiles with a

• A
  2% (1)
• B
  12% (5)
• C
  79% (33)
• D
  7% (3)

Explanation

Option C is correct because the requirement specifies that any other device (not matching the specific MAC) on interface 1/1/1 must receive the "iot-default" role - this is precisely what a fallback role does: it acts as a catch-all for devices that don't match any device profile. The command port-access fallback-role iot-default applied globally ensures unmatched devices get that role without needing an external authentication server.

Why the distractors are wrong:

• A & D (both truncated, but referring to port-access onboarding-method precedence) deal with controlling the order in which authentication/profiling methods are evaluated - they don't assign a default role to unmatched devices, so they don't solve the problem.
• B (port-access device-profile mode block-until-profile-applied) would block any device that doesn't match a profile from gaining network access, which is the opposite of what's needed - you want unmatched devices to get the "iot-default" role, not be denied.

Memory tip: Think "Fallback = catch-all net." Just like a safety net catches what slips through, fallback-role catches every device that doesn't match a specific profile. If the question mentions "any other device" needs a role, the answer involves fallback-role.

No community discussion yet for this question.