D8LooP - Practise Data Engineering

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You've joined SensorCo. A device that loses signal in a tunnel uploads three hours of backlog at once — out of order and sometimes duplicated. Ops has a wall dashboard refreshing every five seconds with a threshold that differs per device; analysts want months of daily averages; and keeping every raw reading at full resolution is not affordable.

your model must answer

01The latest reading for a given device and metric?
02Devices currently above their own threshold?
03Daily average per device and metric for last week?

out of scopeAlert delivery · provisioning · firmware · maintenance

This exercise’s brief could not be loaded.The guided questions and their model answers come from the review service. It looks like it is not reachable — start it with pnpm dev:api and reload.The canvas below still works, so you can model now and run the review once the service is up.

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

Start with the data model, then layer system context

Use entities and relationships for the real ERD. Add notes, containers, or curated cloud shapes only when they sharpen the story you are architecting.

68%

You built the model in the Studio. Now defend it.A hot dashboard over cold history

Design review

The reviewer reads your model.

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

your model must answer

01The latest reading for a given device and metric?
02Devices currently above their own threshold?
03Daily average per device and metric for last week?

out of scopeAlert delivery · provisioning · firmware · maintenance

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

Start with the data model, then layer system context

Use entities and relationships for the real ERD. Add notes, containers, or curated cloud shapes only when they sharpen the story you are architecting.

68%

You built the model in the Studio. Now defend it.A hot dashboard over cold history

Design review