Assessment 3 Diagnose and prepare a release Answer guide
Each answer is a scoring guide, not the only acceptable wording. Score the technical conclusion (2), explanation (2), and requested evidence or clarity (1). A correct guess without reasoning earns at most the conclusion points.
Question 1
Check the requested stylesheet path, actual filename and case, and whether the file is in the moved package. Use Network evidence when available. Only after successful loading check selector matches, declarations, and cascade. Rewriting CSS cannot repair a missing file.
Question 2
The query tests available viewport width, not device identity. Window size, user settings, and content all matter. The breakpoint should be chosen where the actual content fits. A desktop window can be narrow and a phone can have different effective conditions.
Question 3
Keep a visible native outline or supply a contrasting focus-visible replacement. Tab through every control, check clipping and actual backgrounds, and ensure order makes sense. Mouse hover alone is not a keyboard-focus test.
Question 4
Use an honest message such as “Practice check complete. No registration was created.” Static navigation plus native validation does not save a booking or notify an organizer. POST by itself does not create that service.
Question 5
Suitable checks include local paths, 320px layout, 200% zoom, keyboard focus, native invalid/valid form entries, and no-data result navigation. Only award evidence points for checks actually performed. Gaps might be a physical phone, a second browser engine, screen-reader use, or human beginner testing.
Question 6
A fresh folder reveals accidental dependencies outside the package. A loopback local server serves files on the local machine rather than creating a public hosting arrangement. Publication requires an authorized host, visibility decisions and release checks; this course’s completion does not depend on paid accounts or publishing.
Use the result
For a missed question, return to the related lesson and apply the concept to a different event or different numeric values. Keep your first attempt so you can see what changed in your reasoning.