App-Development-with-Swift-Certified-User Exam Dumps - Apple App Development with Swift Questions and 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.

This question belongs to Swift Programming Language , specifically the objectives covering functions , control flow , and default parameter values . The function is declared as func getAgeCategory(_ age: Int = 20) - > Int, which means if no argument is supplied, Swift uses the default value 20. Apple’s Swift documentation explains that you can define a default value for any parameter, and that value is used when the caller omits that argument. Since the code calls getAgeCategory() with no parameter, the function executes using age = 20.

The conditional logic is then evaluated in order:

if age > 64 → false, because 20 is not greater than 64

else if age > 19 → true, because 20 is greater than 19

so the function returns 2

Because Swift’s if / else if control flow stops at the first true condition, the later checks are never reached once age > 19 succeeds. Apple describes Swift as supporting standard control flow including conditional branching, and this example is a direct use of that branching behavior.

Therefore, print(getAgeCategory()) outputs 2 , which corresponds to option B .

age — Variable

birthDate — Constant

socialSecurityNumber — Constant

salary — Variable

currentDepartment — Variable

This question belongs to Swift Programming Language , specifically the objective on demonstrating when to use constants and variables . In Swift, a constant is declared with let and is used for values that should not change after they are set. A variable is declared with var and is used for values that may change over time.

Birth date is a constant because a person’s date of birth does not change. Social security number is also a constant because it is intended to be a fixed identifier for that employee record. By contrast, age is a variable because it changes over time. Salary is a variable because compensation can be adjusted. Current department is also a variable because an employee may transfer to another department.

This matches Swift best practice: use let for fixed data and var for mutable data. So in a human resources record, identifiers that are permanent should be constants, while values that can change during employment should be variables.

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 .

Comprehensive and Detailed Explanation From App Development with Swift domains:

This question belongs to View Building with SwiftUI , especially the domain covering List Views to iterate through collections . In the code, fruits is an array of strings, and the List initializer is being used to create one row for each item in that collection. Apple’s SwiftUI documentation explains that List can present rows from a collection of data, and when the data elements are not supplied through a type that already provides identity, you can provide an id key path so SwiftUI can uniquely identify each row. Here, id: \.self tells SwiftUI to use each string value itself as the identifier.

Option D is therefore the correct statement because the List is clearly rendering the contents of the fruits array as separate rows, and each row shows a Text(fruit) view. Apple’s app development tutorials describe List as a container view that displays rows of data arranged in a single scrollable column, which matches exactly what this code is doing.

Option A is false because for an array of String values in this form, id: \.self is used to identify each row. Option B is false because the key path is not related to .font(.headline) or .padding(); those are standard view modifiers, not dynamic property extraction in this example. Option C is false because Swift key-path syntax uses a backslash, as in \.self, not /self. Apple’s KeyPath documentation shows that Swift key paths use the backslash form.

This question belongs to View Building with SwiftUI , especially the domain covering positioning and/or layout a single SwiftUI View with standard Views and modifiers and the foundational structure of a SwiftUI view. In SwiftUI, a custom screen is typically declared as a struct that conforms to the View protocol. Apple’s SwiftUI documentation shows the standard pattern:

struct ScreenView: View {

var body: some View {

Text( " Hello " )

}

}

Here, struct is required because SwiftUI views are commonly defined as structures. View is required after the colon because the type must conform to the View protocol. body is the required computed property that returns the content of the view as some View. Apple documents that every conforming View type must provide a body property that describes its content.

So the completed code is:

import SwiftUI

struct ScreenView: View {

var body: some View {

Text( " Hello " )

}

}

This is the canonical SwiftUI view declaration pattern and is one of the most fundamental concepts in App Development with Swift.

This question belongs to Xcode Developer Tools , specifically the objective on using debugging techniques including breakpoints, watchpoints, and logging to resolve errors . A watchpoint monitors a variable or memory location during a debugging session, so you first need the program to stop while being debugged. That is why the correct order begins with setting a breakpoint and then running the code so execution pauses at a useful point. Apple’s debugging guidance describes debugging as something done at runtime using the debugger, and LLDB’s watchpoint documentation explains that watchpoints are part of the debugger workflow rather than something you set before the program is stopped.

Once execution is paused, you use the debug area to inspect the current variables. After locating the variable you want to monitor, you right-click the variable and select Watch to create the watchpoint. This sequence is consistent with how Xcode and LLDB expose watchpoint functionality during an active debug session. LLDB also describes watchpoints as objects you create to stop execution when a watched value changes, which only makes sense after the debugger has access to the running program state.

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