Practice Free App-Development-with-Swift-Certified-User App Development with Swift Certified User Exam Exam Questions Answers With Explanation

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.

This question belongs to Swift Programming Language , specifically the domain covering structs, properties, methods, and initializers .

A computed property does not store a value directly. Instead, it returns a value calculated from other data. That is why description is a computed property: it returns a string based on content.

A memberwise initializer is automatically provided by Swift for structs when their stored properties are initialized through parameters. So Document(content: " Greetings! " ) is using the struct’s memberwise initializer.

A type property belongs to the type itself rather than to an instance. In Swift, static var docCount = 0 is a type property because it is declared with static.

An instance method is a function that belongs to an instance of the struct or class. The display() method uses the instance’s content, so it is an instance method.

A type method is a method declared with static and belongs to the type itself. So static func increment() is a type method because it changes the shared type property docCount.

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 .

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.

This question belongs to Swift Programming Language , specifically the objectives covering arrays , loops , and range operators . The array has 6 elements, so menuItems.count is 6. The loop uses the half-open range operator:

for index in 1.. < (menuItems.count - 1)

That becomes:

for index in 1.. < 5

In Swift, the half-open range operator a.. < b includes the lower bound but does not include the upper bound. So this loop runs with index values 1, 2, 3, 4, not 0 and not 5.

Array subscripting uses those indexes to print:

menuItems[1] ? " Burger "

menuItems[2] ? " Chicken "

menuItems[3] ? " Pasta "

menuItems[4] ? " Salad "

That means " Pizza " at index 0 is skipped, and " Steak " at index 5 is also skipped. Swift arrays use zero-based indexing, and count returns the number of elements in the array.

Therefore, the program prints only " Burger " , " Chicken " , " Pasta " , and " Salad " , so the correct answer is A .

This question belongs to View Building with SwiftUI , specifically the domain on extracting subviews to simplify the structure of an overlarge View .

When you create a custom SwiftUI view and add a stored property like:

let text: String

that property becomes part of the view’s initializer. Since the property name is text, Swift expects you to pass the value using the parameter label text: when creating the view. So the correct call is:

BigGreenTextView(text: " That ' s all folks " )

That makes B the correct answer.

Why the others are wrong:

A is incorrect because this is not using the expected parameter label.

C would only be correct if there were already another variable named text in the calling scope and you wanted to pass that variable instead of the literal string shown in the question.

D is incorrect because it omits the parameter label.

This is a standard SwiftUI pattern: extract reusable formatting into a separate custom View, give it an input property, and then pass the needed value through the initializer using the property label.

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.