Question 100
At fictional Sparrow Research, the network architecture group is preparing a proposal for innovation campus during the architecture feasibility review (case HPE7A11-3.1-125). The review identified this issue: a design describes a role-based access model but never states how legacy devices will be handled. Which architecture or design action best addresses this issue?
Explanation
Correct Answer
This action addresses the stated design issue: A design describes a role-based access model but never states how legacy devices will be handled. The proposed response is to document supported authentication exceptions and their compensating restrictions. The observable acceptance result is that the proposal has a validated onboarding path for constrained endpoints.
Incorrect Answers
This option — “Write requirement-to-design traceability with specific topology and acceptance evidence” — checks write technical proposal document, not whether the design resolves the stated fault: a design describes a role-based access model but never states how legacy devices will be handled. The selected direct criterion is “Document supported authentication exceptions and their compensating restrictions.”.
“Explain why topology tiers are necessary or simplify the proposal to suit scale” is a test of write technical proposal document. That does not establish “Document supported authentication exceptions and their compensating restrictions.” for the reported issue (a design describes a role-based access model but never states how legacy devices will be handled).
“Include coverage and capacity assumptions with representative client load evidence” evaluates write technical proposal document. The reported design gap is this: a design describes a role-based access model but never states how legacy devices will be handled. The required response is “Document supported authentication exceptions and their compensating restrictions.”.