Ember Data quiz

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

How does Ember Data typically handle saving changes made to an already-fetched record (e.g. updating a user's email address)?

1. How does Ember Data typically handle saving changes made to an already-fetched record (e.g. updating a user's email address)?
2. 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?
3. How does Ember Data typically handle asynchronous relationships (like the default behavior of `@belongsTo`/`@hasMany`) when a related record hasn't been loaded yet?
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 the purpose of an Ember Data "Adapter"?
6. What is a reasonable justification for defining explicit relationships (via `@belongsTo`/`@hasMany`) on Ember Data models, rather than just storing a raw foreign-key ID as a plain attribute and manually fetching the related record separately when needed?
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 the difference between `store.findRecord()` and `store.peekRecord()` in Ember Data?
9. What is the purpose of the Ember Data "Store", and how is it typically accessed within an application?
10. What does `store.createRecord()` do, and how does the resulting record relate to the backend until it's actually saved?
11. What is the purpose of an Ember Data "Serializer"?
12. What does calling `.rollbackAttributes()` on a "dirty" (locally modified but not-yet-saved) Ember Data record do?

More quizzes