Question 100
A data center implementation team investigates the following fault: An MDS monitoring analyst receives a network-admin role and can edit SAN zoning despite requiring only fabric health visibility. Which design or configuration error caused the described issue?
Explanation
Correct Answer
The technical cause is The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. The appropriate response is: Replace the overly broad MDS role with an approved read-only or scoped monitoring role. Confirm successful repair: The analyst inspects FCNS and port health but cannot activate or change production zonesets.
Incorrect Answers
Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. “Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs” would address that alternative cause, not the condition in this question: the MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs.
“Correct the ACI contract consumer-provider bindings and permit only the required application port” responds to this separate finding: the contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. This question instead needs “Replace the overly broad MDS role with an approved read-only or scoped monitoring role”, so the alternative does not meet the stated condition.
Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. “Configure supported MDS port-security bindings for the intended server initiator and affected VSAN” applies to that separate problem. The observed case is an MDS monitoring analyst receives a network-admin role and can edit SAN zoning despite requiring only fabric health visibility; choosing this alternative would address the wrong failure mode.