Correct Answer: C  🗳️

Explanation: Only visible for ActualTestsIT members. You can sign-up / login (it's free).

Correct Answer:

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.

Correct Answer:

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.

Correct Answer:

Answer the question by typing in the box.
2
Explanation:
This question belongs to Swift Programming Language , specifically the objectives covering functions , control flow , and default parameter values . The function is declared as func getAgeCategory(_ age: Int =
20) - > Int, which means if no argument is supplied, Swift uses the default value 20. Apple's Swift documentation explains that you can define a default value for any parameter, and that value is used when the caller omits that argument. Since the code calls getAgeCategory() with no parameter, the function executes using age = 20.
The conditional logic is then evaluated in order:
* if age > 64 # false, because 20 is not greater than 64
* else if age > 19 # true, because 20 is greater than 19
* so the function returns 2
Because Swift's if / else if control flow stops at the first true condition, the later checks are never reached once age > 19 succeeds. Apple describes Swift as supporting standard control flow including conditional branching, and this example is a direct use of that branching behavior.
Therefore, print(getAgeCategory()) outputs 2 , which corresponds to option B .