Authentic Apple Certification Exam App-Development-with-Swift-Certified-User Questions Answers

This question belongs to View Building with SwiftUI , specifically stacking views and applying modifiers. A ZStack layers views from back to front, so the first item becomes the background and later items appear on top. To match the screenshot, the black background must be the back layer, so Color.black goes first. The large white circle sits above that, so Circle() followed by .foregroundStyle(.white) comes next. Finally, the red heart image sits on top of the circle, so Image(systemName: " heart " ).resizable() followed by .foregroundStyle(.red).frame(width: 200, height: 200) must be last. SwiftUI’s Image.resizable() allows the symbol image to scale to the frame you apply, and foregroundStyle sets the visible color styling for the shape and symbol.

So the intended structure is:

ZStack {

Color.black

Circle()

.foregroundStyle(.white)

Image(systemName: " heart " ).resizable()

.foregroundStyle(.red)

.frame(width: 200, height: 200)

}

This produces a black background, a white circular shape, and a centered red heart on top, exactly as shown.

This question belongs to Swift Programming Language , specifically the objective on managing data using collection types , including dictionaries and arrays . In the dictionary shown, the emojis are the keys and the text descriptions are the values . Swift provides a keys property on dictionaries that returns a collection containing all dictionary keys. To convert that keys collection into an array, you use the Array(...) initializer. Therefore, the correct code is let emojis = Array(faces.keys). Apple documents both the Dictionary.keys property and the Array type used to store a sequence of values of the same type.

Option B is incorrect because faces.values would return the descriptions like " grinning " , " thinking " , and " happy " , not the emoji keys. Options A and C are incorrect because List is a SwiftUI view type, not the correct collection type for creating an array from dictionary contents. Also, the dictionary interface uses properties like .keys and .values, not method calls like .keys() or .values(). Apple’s dictionary documentation makes clear that keys is a property returning a collection of the dictionary’s keys.

Comprehensive and Detailed Explanation From App Development with Swift domains:

This question belongs to View Building with SwiftUI , specifically the objective about extracting subviews to simplify the structure of an overlarge view . The correct answer is C because the standard SwiftUI approach to modularizing a large interface is to create a separate custom view, usually as a new struct conforming to View, and then use that view inside the main view. Apple’s tutorials and documentation repeatedly show this pattern: move part of the UI into its own SwiftUI view type, then compose the main screen from smaller view components.

Option A is not the primary SwiftUI pattern for extracting a reusable subview. Option B does the opposite of modularization, because it keeps everything in the same large body. Option D is about state management and data flow, not about extracting a visual component into its own reusable subview. Apple’s SwiftUI materials emphasize composition, where views are lightweight and can be split into smaller reusable pieces for clarity, maintainability, and reuse. WWDC guidance also shows Xcode’s “Extract Subview” workflow, which creates a separate view structure from selected UI code.