Free Salesforce Plat-101 Actual Exam Questions

It’s C because showing Grand Total and Subtotals gives a summary without all the detail rows, so you get group counts plus the overall count, but no individual records cluttering the view.

D imo, option B doesn’t fit because turning on Subtotals and Detail Rows would still show individual records and grouped totals, which is more info than needed. Option C with Grand Total and Subtotals still shows group breakdowns, so not just one clean count. Option A sounds right since Row Counts and Grand Total get rid of all the detail rows, leaving just the overall count. So it seems like the best way to only show the Record Count without extra data.

It’s B because if that feature isn’t enabled, making two separate contact records is the only way to show the contact working at multiple accounts without merging accounts.

A, keeps data clean without duplicates or confusion.

B. Permission sets are perfect for granting extra access on top of existing profiles without a full profile redesign, which fits the scenario better than changing profiles or relying on role hierarchy.

Option C doesn’t really fit here since role hierarchy controls record access, not field-level permissions. So between A and B, permission sets (B) are better for adding access without changing the whole profile.

C/B? Nonprofit Cloud clearly nails fundraising and grantmaking, which are core here. But since operations management and marketing are also key, Experience Cloud seems important for engagement and tailoring outreach. So it feels like Nonprofit Cloud covers most requirements but might need Experience Cloud to fully handle marketing and engagement aspects. Choosing just one, C fits best overall, but realistically, a combo probably works better.

C/D? Nonprofit Cloud definitely covers fundraising and grantmaking, but marketing and engagement might lean more towards Experience Cloud features. Still, Nonprofit seems best overall for these combined needs.

Option A fits better since it covers both onboarding with actual data and testing safely.

It’s C because Trailhead Playgrounds are designed for learning and onboarding without touching real company data, making them perfect for new hires to practice and explore safely.

B tbh doesn’t fit with multi-tenant because that’s more about isolated environments, which is single-tenant’s thing. Multi-tenant is all about efficiency by letting tenants share the same system resources rather than each having a chunk set aside just for them. That sharing aspect is what makes C the better pick here.

C imo. Multi-tenant means several tenants access the same system and share its resources, instead of each having their own dedicated setup. B’s off because reserving resources per tenant sounds more like single-tenant or isolated environments. A is also incorrect since multi-tenant usually aims to reduce costs, not increase them.

It’s A because picklists prevent future errors without blocking saves like validation rules could.

It’s A for sure. Picklists stop users from entering anything that’s not on the list, which solves the typo and blank problem going forward. Validation rules (B) might prevent wrong entries, but they don’t help if the field is blank or if users don’t know the exact spelling to satisfy the rule. Emailing users (C) is just a passive approach and doesn’t actually stop errors from happening. So, switching to a picklist is the only action that enforces correct data entry reliably after the change.

Pretty sure it’s A too, since Contacts can exist even without an Account linked, which rules out master-detail. Lookup fits best here. So, I’d go with A.

It’s A because Contacts have a standard lookup to Accounts, letting them exist without one. Master-detail would force Contacts to be deleted if the Account’s deleted, which isn't the case here.

Maybe D, but since there’s no D here, probably A still. The platform’s cloud nature means Salesforce does all the updates on their servers. If you had to download or buy something every time, that’d kill the whole point of SaaS. I also don’t see how B could be right because licenses are usually subscription-based, not tied to every single update. So yeah, A really lines up as the only practical choice here.

A – Salesforce is cloud-based and updates roll out automatically, so users don’t have to do anything manually like downloading or buying new licenses.

Maybe B, permission sets can grant field edit rights without profile changes.

C imo, public groups can be used in sharing rules that grant access to records, but that alone won’t change field-level edit permissions. Since the question focuses on field edits, permission sets (B) are usually the go-to, but updating a public group could be part of the sharing setup. A queue (A) is mostly for leads or cases, not opportunities. So between B and C, B is still stronger for field edits, but C might help if sharing rules need adjusting as well.

Maybe A could work here since role hierarchy helps with data visibility based on department structure. If departments line up with roles, users get access to info their department needs without extra setup. Profiles and permission sets control permissions, but role hierarchy handles access to records naturally. So, if data sharing is the main concern per department, role hierarchy might be the simplest way to manage access.

Not B, since creating individual profiles for each department can get messy and hard to maintain. Permission sets (C) are better for tweaking access without making a bunch of profiles.

D imo, Setup is definitely out since it’s for admin settings. Between Accounts and Reports, the Reports tab is built for customized reporting, so that’s where you’d make a detailed report with specific filters.

C. The Reports tab is definitely where you'd create a proper report with filters like territory and active status. The Accounts tab just shows data and lets you create list views, but those aren’t full reports. Setup is for admin stuff, so that’s out. For this kind of request, the Reports tab gives you the most flexibility to customize exactly what the sales rep needs.

D imo, text area fields are open-ended for typing, so that can be cut. Formula fields auto-calc, not user-selected. So picklist fits perfectly with the predefined selectable options here.

Makes sense to rule out formula and text area since they don’t allow users to pick from options. Definitely sounds like A.

It’s A because the Activity Timeline tracks calls, emails, and meetings with the contact, giving a full interaction overview. The Details Tab just holds static info, so it’s less relevant here.

A for sure, it shows actual communications, not just record changes.

D imo, Sales Cloud focuses more on managing the sales process and customer records but doesn’t have native tools for orchestrated email sequences or detailed tracking of message engagement like open or response rates. Service Cloud is more about customer support. Marketing Cloud (B) is built specifically for automating marketing campaigns, tracking engagement, and personalizing outreach, which fits all the needs mentioned. So even if they use Sales Cloud for leads, the actual messaging and analytics described fit Marketing Cloud better.

Maybe B. Marketing Cloud is designed to handle automated message sequences and track engagement, which fits the scheduled outreach part. Plus, it’s built for personalized campaigns to existing customers, so it should cover the customized messages about new products and discounts. Sales Cloud mostly focuses on managing leads and opportunities rather than detailed messaging. Service Cloud is more about customer support, so it doesn’t really match the marketing and messaging needs here. Overall, Marketing Cloud seems like the right fit for all these requirements in one solution.