Free Salesforce Administrator ADM-201 Actual Exam Questions

A, since Geolocation fields are designed specifically for latitude and longitude data.

It’s A, since only Geolocation stores exact coordinates, others don’t fit here.

A imo, because creating a queue for the new product cases and a criteria-based sharing rule that grants read/write access to the two engineers seems more straightforward and fully automated. Predefined case teams with assignment rules (B) might work, but assignment rules usually assign ownership, not necessarily add users to case teams automatically. User-based sharing rules (C) require manual maintenance if engineers change, and ad-hoc case teams aren’t automatic. Auto-response rules (D) don’t affect access. So A looks like the best fit for fully automated access control here.

C imo, because user-based sharing rules can grant access directly to specific users like the two engineers, ensuring they get read/write without needing ownership changes. Ad-hoc case teams might seem manual, but combining it with a sharing rule can automate access better than relying on assignment or queues. A seems close but queues don’t directly give read/write access to individuals unless you own the case, which might not fit here. So, user-based sharing rule targeting the engineers sounds more straightforward for the exact need.

Probably A, B, and E since picklist values, help text, and field names directly affect how the field works.

Maybe D is out because decimal places are more about formatting numbers, not really customizing the field’s core properties. Field history tracking (C) feels more like an admin setting tied to audit rather than field customization itself. A (picklist values), B (help text), and E (field name) seem like actual elements you’d tweak directly on the field to fit your org’s needs. So I’d go with A, B, and E too, since they’re the parts that change the user experience or field identity more than just tracking or display details.

B. Get Records is the only element that actually searches for records and lets you save values to variables, so it fits best for this task. Assignment won’t find or retrieve data.

Guessing B since Assignment doesn’t actually search records.

D imo, standard fiscal years are always 12 months by definition, so specifying the duration isn’t really needed or even an option. The key is picking a start month, and since standard fiscal years typically start in January, that rules out C and D. Custom fiscal years let you choose any start month, so A fits best. B doesn’t really make sense because fiscal years are defined by months, not just quarters, so setting duration to 4 quarters doesn’t change the 12-month length.

A/C? Standard fiscal years usually start in January, so C might not allow February. Custom definitely lets you pick any start month, so A feels safer to meet the exact request.

A, D, and E—Assistant is phased out, so better to stick with these for daily insights.

It’s A, D, and E for me. Activities give daily tasks, Key Deals spotlight important opportunities, and Performance Chart tracks overall progress—perfect for a quick start of day update for sales managers.

Maybe C makes sense too since setting org-wide defaults to the strictest level limits who can see or do what inside Salesforce after login, so even if someone unauthorized gets in, their access is limited.

B makes the most sense since disabling TLS (A) would weaken security and autocomplete (D) could expose info. Org-wide defaults (C) control data access but don’t stop unauthorized logins.

C imo, because you need to explicitly remove Delete permission which only a custom profile can do.

C. Since permission sets can only add permissions and can’t take any away, if the user’s base profile already has Delete rights, a custom profile without Delete is the way to go. Creating a custom profile ensures you can explicitly remove Delete while keeping Read, Create, and Edit intact. Options A and B are definitely out since System Admin has full access and “View all” with highest role doesn’t restrict deletes either. So it really comes down to creating a tailored profile to control delete permissions precisely.

Maybe A and C. Approval Process (C) for the review part is a no-brainer, and Quick Action (A) could help users start expense reports easily in Salesforce before sending them out.

C/B imo since approval handles reviews, outbound messages automate data push.

Maybe A because using component visibility filters lets you tailor what each user role sees without losing access to other info entirely. It keeps the page dynamic by role.

B tbh, removing unnecessary fields simplifies the page and cuts down distractions, making it easier for users to focus on what's important for their role without complicating the layout.

Option A could work if someone already has basic skills; training might be faster than starting from scratch or dealing with unknown apps. Plus, no extra cost involved.

D imo, if the budget can’t increase and the deadline is tight, building dashboards manually might be fastest since training or hunting for apps could waste time.

Makes sense to exclude User and Case since those aren't typically used for personal data tracking. C fits because Contacts, Leads, and Person Accounts hold that info by default. So I’d go with C.

If you think about where personal data is primarily stored, it’s usually under Contact, Lead, and Person Account. User and Case records don’t typically hold that info directly, so including those layouts seems unlikely for the Individual field. Could the field even appear on User without customization?

Not A, since Stages just track progress and don’t assign credit. B Splits is the best fit because it’s designed to break down contributions among team members, not just by revenue but by effort too.

B, since only Splits can allocate credit proportionally among team members.

Maybe B, since permission sets can easily add lead access without messing with roles or sharing.

It’s D because manual sharing lets you give specific users access without changing profiles or roles, perfect if it’s just a few users who need lead access temporarily.

B/D makes sense since Import Wizard can undo imports and Mass Delete handles quick removals.

Maybe B and D here. Mass Delete is good, but the Import Wizard lets you undo recent imports directly, which can be quicker than using Data Loader for deletes.