Core Data overview in iOS Swift - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Core Data context from the persistent container.

iOS Swift

let context = persistentContainer.[1]

Drag options to blanks, or click blank then click option'

AdefaultContext

BviewContext

CbackgroundContext

DmainContext

Attempts:

3 left

💡 Hint

Common Mistakes

Using backgroundContext instead of viewContext for UI updates.

Trying to access a context property that does not exist.

The viewContext is the main managed object context used for UI updates in Core Data.

2fill in blank

medium

Complete the code to save changes in the Core Data context.

iOS Swift

do {
  try context.[1]()
} catch {
  print("Save failed")
}

Drag options to blanks, or click blank then click option'

Acommit

Bpersist

Csave

Dstore

Attempts:

3 left

💡 Hint

Common Mistakes

Using commit() which does not exist.

Forgetting to use try with save().

Calling save() on the context commits changes to the persistent store.

3fill in blank

hard

Fix the error in fetching Core Data objects by completing the fetch request code.

iOS Swift

let fetchRequest = NSFetchRequest<NSManagedObject>(entityName: [1])
let results = try context.fetch(fetchRequest)

Drag options to blanks, or click blank then click option'

AUserEntity

BuserEntity

C"userEntity"

D"UserEntity"

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes around the entity name string.

Using incorrect capitalization.

The entity name must be a string literal matching the Core Data model entity name exactly, including case.

4fill in blank

hard

Fill both blanks to create a new managed object and set its attribute.

iOS Swift

let entity = NSEntityDescription.entity(forEntityName: [1], in: context)!
let newObject = NSManagedObject(entity: entity, insertInto: [2])
newObject.setValue("John", forKey: "name")

Drag options to blanks, or click blank then click option'

A"Person"

Bcontext

CpersistentContainer

DviewContext

Attempts:

3 left

💡 Hint

Common Mistakes

Using persistentContainer instead of context for insertion.

Not quoting the entity name.

Use the entity name as a string and insert the new object into the current context.

5fill in blank

hard

Fill all three blanks to filter fetch results by a condition.

iOS Swift

let fetchRequest = NSFetchRequest<NSManagedObject>(entityName: [1])
fetchRequest.predicate = NSPredicate(format: "[2] == %@", [3])
let results = try context.fetch(fetchRequest)

Drag options to blanks, or click blank then click option'

A"Person"

Bage

C30

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Using attribute names without quotes in the format string.

Passing a string instead of a number for age.

The fetch request uses the entity name "Person" and filters where the attribute "age" equals 30.

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