App Development with Swift Certified User Exam App-Development-with-Swift-Certified-User Exam Questions with Experts Answers Updated Recently

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.

You can treat a NavigationLink like a button, and run some Swift code when it is pressed. — False

NavigationSplitView can be used to do navigation differently on different device sizes. — True

You can put a header on your present View in a NavigationStack using .navigationTitle. — True

If you have a NavigationLink that goes to another View with a NavigationLink, you need to declare a NavigationStack at each level. — False

This question belongs to View Building with SwiftUI , specifically the objective on creating a multi-view app with navigation stacks, links, and sheets . Statement 1 is False because NavigationLink is primarily a navigation control that pushes or presents a destination in a navigation container; Apple documents it as creating a navigation link that presents a destination, not as a general-purpose action control like Button.

Statement 2 is True because NavigationSplitView is designed for adaptive navigation and can present navigation in different ways depending on platform and available space. Apple documents NavigationSplitView as a container for navigation across multiple columns, and this adaptive behavior is exactly why it is used differently across device sizes.

Statement 3 is True because .navigationTitle(...) sets the navigation title for a view shown inside a navigation container. Apple explicitly describes a view’s navigation title as something used to visually display the current navigation state of an interface.

Statement 4 is False because you do not need a separate NavigationStack at every level. Apple describes NavigationStack as the container that manages a stack of views, and NavigationLink pushes additional destinations onto that stack. Nested destinations can keep navigating within the same stack.

This question belongs to Xcode Developer Tools , specifically the objective domain on identifying and using the features of the Xcode interface . In the screenshot, the correct area is the upper-right corner of the editor toolbar , where Xcode provides the control for editor display options. Apple’s documentation explains that to show previews, you can use the editor controls and specifically notes that you can click the Adjust Editor Options button and choose Preview , which displays the preview canvas to the right of the editor.

So, in hotspot terms, the correct selection is the editor options control near the top-right of the code editor , not the Run button, not the Inspector, and not the Project navigator. This aligns with Apple’s preview workflow for SwiftUI in Xcode, where the canvas is shown from the editor display controls. Apple also describes the preview canvas as part of Xcode’s interface for quickly visualizing UI changes while editing code.

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

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 .