An administrator at Universal Containers is reviewing current security settings in the company's Salesforce org. What Should the administrator do to…

Multi-Factor Authentication (MFA) is a core security feature that significantly strengthens access control. It requires users to provide two or more pieces of evidence (or "factors") to prove their identity before being granted access to the Salesforce org. This typically combines something the user knows (password) with something they have (a code from an authenticator app or a physical security key). By implementing MFA, an organization ensures that even if a user's password is compromised, an unauthorized individual cannot log in without the second verification factor, directly preventing unauthorized access.

A. Disabling TLS (Transport Layer Security) requirements would remove encryption for data in transit, severely weakening security and increasing the risk of unauthorized access.

C. Customizing organization-wide defaults controls the baseline visibility of records after a user has successfully logged in; it does not prevent the initial unauthorized login.

D. Enabling caching and autocomplete on the login page is a security risk, as it can expose credentials on shared or public computers, making unauthorized access easier.

---

1. Salesforce Help & Training

"Multi-Factor Authentication": This document outlines the purpose of MFA. It states

"Multi-factor authentication (MFA) is one of the easiest

most effective tools for enhancing login security and safeguarding your business and your data against security threats like phishing attacks

credential stuffing

and account takeovers." (See the "What Is Multi-Factor Authentication?" section).

2. Salesforce Help & Training

"How Multi-Factor Authentication Works to Secure Account Access": This resource details the mechanism of MFA. It explains that MFA "adds another layer of security to your login process by requiring users to enter two or more pieces of evidence... to prove they are who they say they are." This directly supports its role in preventing unauthorized access.

3. Salesforce Help & Training

"Configure Session Security Settings": This documentation covers session settings

including TLS. It recommends requiring TLS 1.2 or higher for HTTPS connections to provide a "higher standard of security." Disabling this requirement would be contrary to best practices for preventing unauthorized access. (See the "Session Settings" section).

4. Salesforce Help & Training

"Organization-Wide Sharing Defaults": This official guide defines OWDs. It specifies

"Organization-wide sharing settings specify the default level of access that users have to each other’s records." This confirms that OWDs manage post-authentication data access

not the authentication process itself. (See the "Organization-Wide Sharing Defaults Overview" section).