Salesforce Platform Foundations Practice Exam

Correct: A — Customer Relationship Management. CRM is technology for managing a company's relationships and interactions with customers and prospects, tracking the data tied to those interactions. Salesforce is built on this foundation, then extends well beyond it as a platform.

Why not the others: "Cloud Resource Manager" (B) describes infrastructure provisioning, not customer management; "Customer Reporting Module" (C) is invented — reporting is one feature, not what CRM stands for.

Correct: A — Trailhead. Trailhead is Salesforce's free, self-paced learning platform with hands-on modules, projects, and playground orgs. Knowing the ecosystem's learning and community resources is a core part of the Ecosystem section.

Why not the others: the AppExchange (B) is the marketplace for installing third-party apps, not a learning platform; the Setup Audit Trail (C) is an admin log of configuration changes, unrelated to learning.

Correct: A — Multitenant. Salesforce runs a multitenant cloud model: many customers ("tenants") share the same infrastructure and platform while their data and configurations remain isolated. This lets Salesforce deliver upgrades to everyone simultaneously.

Why not the others: on-premise (B) means software you host in your own data center — the opposite of Salesforce's cloud model; single-tenant dedicated hosting (C) gives each customer its own isolated stack, which is not how the core platform works.

Correct: A — The App Launcher. The App Launcher (the grid icon) lets users search for and open any app or item by name, even when it isn't on the navigation bar. It's the central way to move between apps in Lightning Experience.

Why not the others: the recycle bin (B) recovers deleted records, not apps; the report builder (C) is for creating reports, not launching apps.

Correct: A — A record. Using the spreadsheet analogy: an object is the table, a field is a column, and a record is a single row — one specific instance, like the "Acme Corp" account. This vocabulary is foundational to the Data Model section.

Why not the others: an object (B) is the table/type itself (Account), not a single entry; a field (C) is a single column of data (like Phone or Industry), not a whole row.

Correct: A — Standard objects. Standard objects like Account, Contact, Lead, and Opportunity ship with Salesforce out of the box. The exam expects you to distinguish these from custom objects you build yourself.

Why not the others: custom objects (B) are ones you create for company-specific data (identified by a "__c" suffix); external objects (C) map to data stored outside Salesforce and aren't the standard CRM objects.

Correct: A — An account, a contact, and an opportunity. Lead conversion turns a qualified lead into an account (the company), a contact (the person), and — when there's a sales deal — an opportunity. This flow is a favorite Data Model exam scenario.

Why not the others: reports, dashboards, and folders (B) are analytics artifacts, not the output of lead conversion; profiles, permission sets, and roles (C) are security/access constructs, unrelated to converting a lead.

Correct: A — Share the report folder. Access to reports and dashboards is controlled at the folder level. Sharing the folder (with the appropriate access level) gives the manager access to the reports inside it — the standard, maintainable approach.

Why not the others: exporting to a spreadsheet (B) hands over a static copy, not live access to view and modify in Salesforce; deleting and recreating (C) is destructive and unnecessary.

Correct: A — A report returns records meeting criteria; a dashboard summarizes reports visually. A report is a filtered, grouped list of records; a dashboard presents one or more source reports as charts, gauges, and tables on a single page for at-a-glance insight.

Why not the others: reports aren't always charts and dashboards aren't always tables (B) — both support many formats; visibility (C) is governed by folder sharing and the dashboard's running user, not a blanket admin-only vs. public rule.

Correct: A — Global search. The global search box at the top of Lightning Experience searches across objects and records, letting a user jump straight to a record like a specific account from anywhere in the app.

Why not the others: the dashboard refresh button (B) reloads dashboard data; the data import wizard (C) loads records into Salesforce — neither is a way to find an existing record.