Ember Data quiz

Test your Ember Data knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.

What is a reasonable use case for `store.query()` as distinct from `store.findRecord()` or `store.findAll()`?

1. What is a reasonable use case for `store.query()` as distinct from `store.findRecord()` or `store.findAll()`?
2. What is a "relationship" in Ember Data, and how is a "belongs-to" relationship typically declared on a model?
3. What does calling `.rollbackAttributes()` on a "dirty" (locally modified but not-yet-saved) Ember Data record do?
4. What is the purpose of Ember Data's built-in caching/identity-map behavior, and how does it relate to fetching the "same" record multiple times?
5. What is a reasonable comparison between Ember Data and a more general-purpose data-fetching library (like a plain `fetch()` wrapper, or React Query in a different framework), given that Ember Data is specifically integrated with Ember.js?
6. What is the purpose of an Ember Data "Serializer"?
7. What is a reasonable justification for Ember Data's adapter/serializer separation -- keeping "how to talk to the API" (adapter) distinct from "how to translate the data format" (serializer) as two separate concerns?
8. What is a reasonable mental model for how Ember Data's Store, Models, Adapters, and Serializers work together as a system, when a route calls `this.store.findRecord('user', 5)`?
9. What is the purpose of the Ember Data "Store", and how is it typically accessed within an application?
10. What does it mean for an Ember Data record to be in an "invalid" state, and what typically causes this?
11. What is the purpose of an Ember Data "Adapter"?
12. What does `store.createRecord()` do, and how does the resulting record relate to the backend until it's actually saved?

More quizzes