Core Data overview in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of Core Data in iOS apps?

Core Data is a framework used in iOS development. What is its main role?

A To manage app navigation and screen transitions

B To handle network requests and API communication

C To create user interface elements and layouts

D To manage the app's data model and persist data locally on the device

💡 Hint

Think about where your app stores data that should stay after closing the app.

Core Data helps apps save, retrieve, and manage data on the device efficiently. It is not for UI or networking.

❓ ui_behavior

intermediate

What happens when you save a managed object context in Core Data?

In Core Data, when you call save() on a managed object context, what is the expected behavior?

A Changes in the context are written to the persistent store on disk

B The app's UI automatically refreshes without any additional code

C The app deletes all stored data from the device

D The app crashes if there are unsaved changes

💡 Hint

Saving means making changes permanent, not deleting or crashing.

Calling save() commits changes in memory to the device's storage so data is not lost.

❓ lifecycle

advanced

Which Core Data component manages the lifecycle of your data objects?

In Core Data, which component is responsible for managing the lifecycle (creation, deletion, and tracking) of your data objects?

A NSFetchRequest

B NSManagedObjectContext

C NSManagedObjectModel

D NSPersistentStoreCoordinator

💡 Hint

This component acts like a workspace where you create and edit data objects.

NSManagedObjectContext tracks changes to data objects and manages their lifecycle before saving.

❓ navigation

advanced

How do you fetch data from Core Data to display in a list?

You want to show saved data in a list on your app screen. Which Core Data class helps you fetch this data?

A NSPersistentContainer

B NSManagedObjectContext

C NSFetchRequest

D NSPredicate

💡 Hint

This class defines what data to get and how to filter it.

NSFetchRequest specifies which data to retrieve from Core Data for display or processing.

🔧 Debug

expert

What error occurs if you try to save a managed object context without setting required attributes?

You created a new Core Data object but forgot to set a required attribute. What error will you get when calling save() on the context?

A NSValidationError

B NSFetchRequestError

C NSPersistentStoreSaveError

D NSManagedObjectContextConcurrencyError

💡 Hint

The error relates to missing or invalid data before saving.

NSValidationError occurs when required attributes are missing or invalid during save.

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