Explanation:
* @AppStorage # This property wrapper reads and writes values from UserDefaults.
* @Environment # This property wrapper allows you to access data from the system, such as knowing the size class of the device, or dismissing a view.
* @Binding # When a variable is declared with this property wrapper, changes to its value will be returned to the calling view.
* @State # When a variable is declared with this property wrapper, it is used to store small amounts of data local to the view whose value may affect the appearance of the view.
This question belongs to View Building with SwiftUI , specifically the objective about using @State,
@Binding, @Environment, and related wrappers to share and manage data between views. @AppStorage is the wrapper that connects a SwiftUI value to UserDefaults, so it is the correct match for reading and writing persisted user defaults data. Apple documents AppStorage as a property wrapper type that reflects a value from UserDefaults and updates the view when that value changes.
@Environment is used to read values supplied by the system or ancestor views, including interface context like size classes and actions such as dismissing a presented view. Apple's environment documentation explains that SwiftUI automatically sets and updates many environment values for layout and behavior, and App Dev Training materials show environment values being used to dismiss a view.
@Binding represents a two-way connection to a value owned elsewhere, typically in a parent view, so changes made through the binding are reflected back in the source of truth. Apple's SwiftUI data-flow guidance describes bindings as the mechanism used when a child view needs shared control of state with another view.
@State is the correct wrapper for small, local, mutable view state. Apple describes State as the source of truth for data local to a view and recommends it for interface state that affects rendering.

This question belongs to Swift Programming Language , specifically the objective on functions , including internal and external parameter names and default parameter values .
The function is defined as:
func schedule(who name: String, from starting: String, to ending: String, _ place: String = " Zoom " ) { print( " Appointment: meeting \(name) from \(starting) to \(ending) at \(place) " )
}
This means:
* the external parameter names are who, from, and to
* the internal parameter names are name, starting, and ending
* the last parameter uses _, which means it has no external label
* the last parameter also has a default value of " Zoom "
Now evaluate the options:
* A is incorrect because it uses place: as an external label, but _ place means no external label is allowed.
* B is correct because it uses the required external names who, from, and to, and it omits the last parameter, which is allowed because it has a default value.
* C is incorrect because it uses who:, from:, and to: correctly, but this function's first three parameters are not declared that way in the provided option set; the valid matching call style from the choices is not this one because the function's labels are paired with internal names in the declaration syntax shown in the question.
* D is incorrect because it uses the internal names name, starting, and ending as if they were external labels.
* E is correct because it uses the external labels who, from, and to, and omits the final unlabeled parameter, letting Swift use the default " Zoom " .
So the two correct answers are B and E .

Explanation:

This question belongs to View Building with SwiftUI , especially the objectives for using List views to iterate through collections and structuring views with standard SwiftUI containers. The screenshot shows two grouped sets of rows: one headed MY FRIENDS and one headed MY PETS . In SwiftUI, the correct container for a scrollable table-style presentation of rows is List, and the correct way to divide that list into labeled groups is Section. Apple documents List as a container that presents data in a single-column row- based layout, and Section as a way to organize list content into grouped areas with headers and optional footers. That is exactly the structure shown in the image. ( developer.apple.com , developer.apple.com ) The ForEach(names, id: \.self) and ForEach(pets, id: \.self) lines are already iterating through the arrays, so each ForEach should be wrapped inside a Section. The section labels such as " My Friends " and " My Pets
" are provided with the header: label. So the intended code structure is:
List {
Section {
ForEach(names, id: \.self) { name in Text(name) }
} header: {
Text( " My Friends " )
}
Section {
ForEach(pets, id: \.self) { pet in Text(pet) }
} header: {
Text( " My Pets " )
}
}
This matches the UI shown in the image and aligns directly with SwiftUI list and section composition patterns in App Development with Swift.

Answer the question by typing in the box.
10
Explanation:
This question belongs to Swift Programming Language , specifically the domain covering structs, classes, properties, methods, and the difference between structures and classes .
The key point is that Printer is declared as a class :
class Printer {
var copies: Int
init(copies: Int) {
self.copies = copies
}
}
In Swift, classes are reference types . That means when you assign one class instance to another variable, both variables refer to the same object in memory rather than creating a separate copy. Apple's Swift language guide explains that classes are passed by reference, while structures are value types. So in this code:
var printer1 = Printer(copies: 2)
var printer2 = printer1
both printer1 and printer2 point to the same Printer instance.
Next, this line changes the shared object:
printer2.copies = 10
Because printer2 refers to the same instance as printer1, changing printer2.copies also changes printer1.
copies. Therefore, when the code executes:
print(printer1.copies)
the output is 10 .
This question tests one of the most important Swift concepts: classes are reference types , while structs are value types . If Printer had been a struct instead of a class, the result would have been different because assignment would copy the value rather than share the same instance.