Milestone 1: Environment explored

✅ Navigated to a live, pre-configured blueprint — SE Demo or SE Flow
✅ Explored the blueprint dashboard and understood what each panel represents
✅ Opened the topology view and examined a rendered device configuration
✅ Reviewed active anomalies and seen the level of context Apstra provides

The key idea in this section is the difference between reactive monitoring and intent-driven monitoring. A conventional tool tells you what state a device is in. Apstra tells you whether that state matches your design — and if it does not, it tells you exactly how and where it differs.

That context is the foundation for everything that comes next. Every change you make, every anomaly you investigate, and every rollback you consider is anchored to the intended state you defined in the blueprint.

In the next section you will make real Day 2 changes to a running data centre fabric. You will add physical capacity, create network segmentation, and deploy new virtual networks — without touching a command line.

Ready? Let’s move on!