D8LooP - Practise Data Engineering

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You've joined EventLog, an analytics backbone. Actions are recorded with device and session identifiers — and when a user logs in, previously anonymous actions become theirs, sometimes days later. Events arrive out of order and duplicated, and funnels must stay correct after a late merge.

your model must answer

01The sequence of actions for a user in a given session, including those stitched after login?
02Whether two events belong to the same user after all known identity stitches, at query time?
03By signup week, number of users, fraction who were anonymous before their first action, and conversion to a key event within 7 days?

out of scopeConsent · schema governance · experiments · attribution · streaming

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.User actions, sessions, and retroactive merges

Design review

The reviewer reads your model.

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

your model must answer

01The sequence of actions for a user in a given session, including those stitched after login?
02Whether two events belong to the same user after all known identity stitches, at query time?
03By signup week, number of users, fraction who were anonymous before their first action, and conversion to a key event within 7 days?

out of scopeConsent · schema governance · experiments · attribution · streaming

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.User actions, sessions, and retroactive merges

Design review