Core Data overview in iOS Swift - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Core Data in iOS development?

Core Data is a framework by Apple that helps you save, manage, and organize data in your app. It acts like a smart storage system for your app's information.

beginner

What is an NSManagedObject in Core Data?

NSManagedObject is a class that represents a single record or object in your Core Data storage. Think of it like a row in a table that holds your app's data.

intermediate

What is an NSManagedObjectContext?

NSManagedObjectContext is like a workspace where you create, edit, and save your data objects before they are stored permanently. It helps manage changes safely.

intermediate

What role does the NSPersistentContainer play in Core Data?

NSPersistentContainer sets up the Core Data stack for you. It loads your data model and manages the saving and loading of data behind the scenes.

beginner

How does Core Data differ from using UserDefaults for data storage?

Core Data is designed for complex data with relationships and large amounts of information. UserDefaults is for simple settings or small pieces of data, not structured storage.

What is the main purpose of Core Data in an iOS app?

A To handle network requests

B To design the app's user interface

C To create animations

D To manage and persist app data efficiently

Core Data is used to manage and save data within an app, not for UI, networking, or animations.

Which Core Data class represents a single data record?

A UIViewController

B NSPersistentContainer

C NSManagedObject

D NSURLSession

NSManagedObject represents one data object or record in Core Data.

What does NSManagedObjectContext do?

A Manages network connections

B Manages the workspace for creating and saving data objects

C Handles user input

D Displays data on the screen

NSManagedObjectContext is the workspace where data objects are created, edited, and saved.

Which component sets up the Core Data stack automatically?

A NSPersistentContainer

B NSManagedObject

C UITableView

D AppDelegate

NSPersistentContainer loads the data model and manages the Core Data stack setup.

When should you use UserDefaults instead of Core Data?

A For storing simple app settings or small data

B For managing complex data with relationships

C For large databases

D For network data caching

UserDefaults is best for small, simple data like settings, not complex or large data.

Explain the main components of Core Data and their roles in managing app data.

Think about how data is created, edited, and saved in Core Data.

Describe when and why you would choose Core Data over UserDefaults for storing data in an iOS app.

Consider the type and amount of data your app needs to store.

Practice

1. What is the main purpose of Core Data in an iOS app?

easy

A. To manage app animations

B. To store and manage app data on the device

C. To handle network requests

D. To design the app's user interface

Solution

1. Step 1: Understand Core Data's role

   Core Data is used to save and manage data locally on the device.

2. Step 2: Compare with other options

   UI design, network handling, and animations are handled by other frameworks, not Core Data.

3. Final Answer:

   To store and manage app data on the device -> Option B

4. Quick Check:

   Core Data = Data storage [OK]

Hint: Core Data is about data storage, not UI or network [OK]

Common Mistakes:

• Confusing Core Data with UI frameworks
• Thinking Core Data manages network calls
• Assuming Core Data handles animations

2. Which class is used to set up Core Data stack easily in Swift?

easy

A. NSPersistentContainer

B. NSManagedObject

C. UIViewController

D. URLSession

Solution

1. Step 1: Identify Core Data setup class

   NSPersistentContainer simplifies setting up Core Data stack.

2. Step 2: Exclude unrelated classes

   NSManagedObject represents data, UIViewController manages UI, URLSession handles networking.

3. Final Answer:

   NSPersistentContainer -> Option A

4. Quick Check:

   Setup Core Data = NSPersistentContainer [OK]

Hint: NSPersistentContainer sets up Core Data stack [OK]

Common Mistakes:

• Choosing NSManagedObject for setup instead of data model
• Confusing UI or network classes with Core Data setup
• Using outdated Core Data setup methods

3. Given this Swift code snippet, what type is 'person'?

let person = Person(context: context)

medium

A. An instance of NSManagedObject subclass

B. A UIViewController instance

C. A plain Swift struct

D. A network request object

Solution

1. Step 1: Recognize 'Person' as NSManagedObject subclass

   In Core Data, entities are represented by NSManagedObject subclasses like Person.

2. Step 2: Exclude other types

   UIViewController is for UI, struct is not used here, network object unrelated.

3. Final Answer:

   An instance of NSManagedObject subclass -> Option A

4. Quick Check:

   Core Data entity = NSManagedObject subclass [OK]

Hint: Core Data entities are NSManagedObject subclasses [OK]

Common Mistakes:

• Thinking Person is a struct or class unrelated to Core Data
• Confusing UI or network classes with data entities
• Not recognizing Core Data context usage

4. What is wrong with this Core Data fetch request code?

let request = NSFetchRequest<NSFetchRequestResult>(entityName: "Person")
let results = try context.fetch(request) as? [Person]
print(results.count)

medium

A. NSFetchRequest cannot be used with context.fetch

B. Entity name "Person" is invalid

C. print(results.count) will cause a syntax error

D. Casting fetch results to [Person] may fail without specifying generic type

Solution

1. Step 1: Analyze fetch request generic type

   Using NSFetchRequest<NSFetchRequestResult> returns generic results; casting to [Person] may fail.

2. Step 2: Correct approach

   Use NSFetchRequest<Person> to get typed results and avoid unsafe casting.

3. Final Answer:

   Casting fetch results to [Person] may fail without specifying generic type -> Option D

4. Quick Check:

   Use typed NSFetchRequest to avoid cast issues [OK]

Hint: Use typed NSFetchRequest to avoid casting errors [OK]

Common Mistakes:

• Ignoring generic type in NSFetchRequest
• Assuming entity name is wrong without checking
• Thinking context.fetch is invalid usage

5. You want to save a new 'Task' entity with a 'title' attribute using Core Data. Which sequence correctly saves the data?

hard

A. Create Task object, set title, call URLSession to save

B. Create Task object, set title, call print() to save

C. Create Task object, set title, call context.save() inside do-catch

D. Create Task object, set title, no need to save context

Solution

1. Step 1: Create and set attributes on Task object

   Instantiate Task with context and assign the title attribute.

2. Step 2: Save context with error handling

   Call context.save() inside a do-catch block to persist changes safely.

3. Final Answer:

   Create Task object, set title, call context.save() inside do-catch -> Option C

4. Quick Check:

   Save Core Data changes with context.save() [OK]

Hint: Always call context.save() inside do-catch to persist data [OK]

Common Mistakes:

• Forgetting to call context.save() after changes
• Using print or network calls to save data
• Ignoring error handling when saving