Customer 360 tradeoffs · Data Modeling scenario

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You are the data architect for LoopCRM’s Customer 360. One person appears across CRM, billing, and support under different ids, attributes change over time, and the business wants a fast single profile — so hold a normalized source of truth and a denormalized serving view, and prove the two still agree.

your ERD must answer

01Resolve one canonical customer from records arriving from many source systems.
02How did a customer’s attributes (segment, tier) look at any point in time?
03Serve a fast denormalized 360 profile — and prove it still matches the source of truth.

out of scopeReal-time streaming · ML feature store · GDPR erasure · campaigns

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

68%

You built the model in the Studio. Now defend it.Customer 360 tradeoffs

Design review

The reviewer reads your model.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You are the data architect for LoopCRM’s Customer 360. One person appears across CRM, billing, and support under different ids, attributes change over time, and the business wants a fast single profile — so hold a normalized source of truth and a denormalized serving view, and prove the two still agree.

your ERD must answer

01Resolve one canonical customer from records arriving from many source systems.
02How did a customer’s attributes (segment, tier) look at any point in time?
03Serve a fast denormalized 360 profile — and prove it still matches the source of truth.

out of scopeReal-time streaming · ML feature store · GDPR erasure · campaigns

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

68%

You built the model in the Studio. Now defend it.Customer 360 tradeoffs

Design review

The reviewer reads your model.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules