App-Development-with-Swift-Certified-User Exam Dumps - App Development with Swift Certified User Exam

This question belongs to View Building with SwiftUI , specifically the objective on positioning and laying out a single SwiftUI view with standard views and modifiers.

The correct answer is D because it uses the right combination of SwiftUI image modifiers for all three requirements:

the image is made resizable with .resizable()

it is given rounded corners with .clipShape(RoundedRectangle(cornerRadius: 50))

it displays the entire image with .aspectRatio(contentMode: .fit)

it is sized with .frame(width: 300)

The key part is .aspectRatio(contentMode: .fit) . In SwiftUI, .fit scales the image so the whole image remains visible inside the available frame. That matches the requirement “displays the entire image, regardless of size.” By contrast, .fill may crop part of the image, so options using .fill do not satisfy the requirement.

Why the others are wrong:

Option A uses .fill, so the full image may not remain visible.

Option B uses invalid modifiers such as .sizablc() and .size(width: 300), and also uses Rectangle(cornerRadius: 50), which is not the correct rounded-rectangle shape syntax.

Option C also uses invalid syntax and .fill, which can crop the image.

Option D uses valid SwiftUI syntax and the correct content mode.

So the correct choice is D , because it is the only option that correctly creates a 300-width image with rounded corners while ensuring the entire image is shown.

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 belongs to Swift Programming Language , specifically the objective covering structs, properties, and initializers .

In the struct, both the property and the initializer parameter are named age:

struct person {

var age: Int

init(age: Int) {

self.age = age

}

}

Here, age inside the initializer could refer to either the property of the struct or the parameter passed into the initializer. Swift uses self.age to clearly mean the property that belongs to the current instance , while plain age refers to the initializer parameter . So self.age = age means: assign the parameter value to the instance property.

That is why C is correct. The keyword self is required here to remove ambiguity between two identifiers with the same name.

The other options are incorrect:

A is wrong because self here is not pointing to the parameter; it points to the instance property.

B is wrong because self is not always required in every initializer assignment. It is specifically needed here because of the naming conflict.

D is wrong because whether the property has a default value is not the reason self is needed in this example.

So the correct answer is C. self is needed to distinguish between the property and the parameter with the same name.

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 domain for building and running an app on the iOS simulator . In Xcode, the place where you choose whether the app runs on a simulator or a connected device is the run destination / scheme destination selector in the toolbar. This control appears near the top center of the Xcode window and displays the current destination, such as a simulator model or device target. To run the app on iPhone 14 , you click that selector and choose iPhone 14 from the available simulator list. Apple’s Xcode documentation describes choosing a run destination before building and running the app in Simulator or on a device.

So, for the hotspot, the correct place is the device/simulator dropdown in the top toolbar , not the preview canvas controls, not the project navigator, and not the code editor. That selector determines where the app launches when you press Run.