This question belongs to View Building with SwiftUI , especially the domain on creating multiple views to implement app logic and sharing values between views. In FirstView, the value typed into the TextField is stored in number, which is a String. When the NavigationLink is tapped, the code passes Int(number) ?? 0 into SecondView. In Swift, converting a string to an integer with Int(...) uses an optional initializer, which means it returns an optional value and will produce nil if the string cannot be converted. The ?? 0 nil- coalescing operator then supplies 0 if conversion fails.
Inside SecondView, the body is:
Color(passedNumber == 3 ? .blue : .red)
This uses the ternary conditional operator. If passedNumber equals 3, the displayed color is blue; otherwise, it is red. Therefore, entering 3 into the TextField causes Int(number) to become 3, which makes the condition passedNumber == 3 true and displays a blue canvas. Any other listed number results in red.
So the correct answer is A. 3 . This matches the SwiftUI pattern of taking user input, converting it to the needed type, passing it into another view, and rendering UI conditionally based on that value.

Explanation:
* RedCircleView()
* GreenTriangleView()
* BlueSquareView()
* BlueSquareView()
* GreenTriangleView()
This question belongs to View Building with SwiftUI , specifically arranging views with HStack , VStack , and ZStack . In SwiftUI, an HStack lays views out horizontally, a VStack lays them out vertically, and a ZStack overlays views front-to-back. Apple's stack layout guidance describes these three containers exactly this way.
To match the canvas, the main HStack must show three items from left to right: a red circle , a green triangle
, and then a right-side vertical group. That means the first two blanks inside HStack are RedCircleView() and GreenTriangleView(). On the right side, the VStack shows a blue square on top, so the next blank is BlueSquareView(). Under that, the lower-right shape is made by layering a green triangle on top of a blue square , which means the ZStack must contain BlueSquareView() first as the background and GreenTriangleView() second as the foreground. SwiftUI's documentation notes that ZStack aligns and overlays its children in depth order, which is why the square goes before the triangle.
So the correct placement order is:
HStack {
RedCircleView()
GreenTriangleView()
VStack {
BlueSquareView()
ZStack {
BlueSquareView()
GreenTriangleView()
}
}
}
That arrangement reproduces the exact layout shown in the canvas.

This question is from Swift Programming Language , especially the domains for Optional types , safe and unsafe unwrapping , and control flow . The code uses the ternary conditional operator :
nextApplePhone.releaseDate != nil ? _____
In Swift, the ternary operator follows this structure:
condition ? valueIfTrue : valueIfFalse
So if nextApplePhone.releaseDate != nil is true, the expression must return the new release date. If it is false, it must keep lastReleaseDate unchanged. That means the missing part must be:
nextApplePhone.releaseDate! : lastReleaseDate
which is option D .
This works because nextApplePhone.releaseDate is declared as String?, so it is an optional. Once the condition confirms it is not nil, the code force-unwraps it with ! to access the underlying String value. If the optional is nil, the expression returns lastReleaseDate instead. Apple's Swift documentation describes the ternary conditional operator as a shortcut for choosing one of two expressions based on a condition, and it explains that force unwrapping with ! accesses an optional's wrapped value when you know it is not nil.
The other options are incorrect because they reverse the true/false logic, omit the needed unwrap, or contain invalid identifiers. Therefore, the correct completion is D .

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.

This question belongs to Swift Programming Language , specifically the domain on functions , including internal and external parameter names and default parameter values .
The function is defined as:
func rightSum(_ num1: Int, by num2: Int, and num3: Int = 25) - > Int {
return num1 + num2 + num3
}
This means:
* the first parameter uses _, so it has no external label
* the second parameter must use the external label by
* the third parameter must use the external label and
* the third parameter also has a default value of 25, so it may be omitted Now evaluate each option:
* A is invalid because it uses num2: instead of the required external label by:
* B is valid because it correctly uses no label for the first argument, then by: and and:
* C is invalid because the first parameter cannot be called with num1: since the external label is omitted with _
* D is valid because it correctly passes the first argument unlabeled and the second with by:, while omitting the third argument so Swift uses the default value 25
* E is invalid because it uses num1: and num2: instead of the required calling syntax So the two correct function calls are B and D .