CompTIA Updated 220-1202 Exam Questions and Answers by fleur

Hardening focuses on reducing default attack surface and removing predictable access paths. Quentin Docter explains that default accounts are risky and highlights that Windows creates a Guest account that “represents a weakness that can be exploited,” so you “should disable all accounts that are not needed, especially the Guest account.” That directly supports option B.

Docter also emphasizes changing defaults as part of hardening: “Changing the default password to a complex password is also a good practice in hardening the device.” That maps to option E (change the default administrator password). These actions reduce common credential-based attacks and limit unauthorized access.

Other options are either unrelated to workstation hardening (remote collaboration tools, virtual assistants) or weaken security (disabling screensavers may remove automatic lock behavior). Thus, the best two hardening steps are disable Guest and change the default admin password.

Mobile OS updates can sometimes cause compatibility issues with specific apps, including corporate email clients. The most likely resolution is to check for and apply an update to the affected application, especially if it hasn’t been updated to support the latest OS version.

B. Registering with MDM might be required for access but wouldn’t address app crashes due to incompatibility.

C. A third-party client might help, but it’s not the best first step if the default app is expected to work.

D. Clearing the cache can help resolve some minor issues, but updating the app directly addresses compatibility concerns.

When DHCP isn’t enabled, static IPs must be assigned manually, so the engineering team provides the IP details.

From Travis Everett – All-in-One Exam Guide:

“If DHCP is unavailable, technicians need the static IP configuration to connect devices to the network.” .

Multi-Factor Authentication (MFA) apps, especially time-based one-time password (TOTP) apps (e.g., Google Authenticator, Authy), rely on accurate time synchronization between the device and the authentication server. If the user recently traveled internationally, the device may have incorrect date/time settings due to time zone changes or failed synchronization, leading to MFA failure.

The most logical and non-intrusive first step is to verify and correct the date and time settings. This aligns with basic troubleshooting principles—start with the simplest and most likely cause before taking more drastic action.