Question 360
An application server rack is designed as redundantly connected even though its Apstra generic-system object has only one attachment in the selected rack type. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
This control reduces recurrence of the same class of failure: A generic-system logical device and its links describe how external compute or storage endpoints attach to fabric leaf devices. Apply the recurring practice: Review endpoint attachment diversity in rack-type design approvals and connectivity tests. The previous example was: An application server rack is designed as redundantly connected even though its Apstra generic-system object has only one attachment in the selected rack type.
Incorrect Answers
An Apstra interface map binds a logical device's role and speed abstractions to concrete interfaces in a supported device profile. For the current prevention question, the evidence instead states: An application server rack is designed as redundantly connected even though its Apstra generic-system object has only one attachment in the selected rack type. Here, a generic-system logical device and its links describe how external compute or storage endpoints attach to fabric leaf devices.
Track object versions and dependencies between shared design catalogs and deployed blueprints. That concerns global design catalog versus blueprint-local copy, while the issue here is dual-attached generic system planning. Update the rack-type generic system connectivity so the intended separate leaf attachments are represented and validated against cabling.
Apstra templates compose reusable design elements and networking policies into a blueprint starting structure, including its supported fabric topology. For this issue, update the rack-type generic system connectivity so the intended separate leaf attachments are represented and validated against cabling.