Plat-101 Salesforce Certified Platform Foundations Exam Topics and Questions
These Salesforce Certified Platform Foundations (Plat-101) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise Plat-101 sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Certified Platform Foundations certification exam.
Let's Practice Free Salesforce Plat-101 Questions Aligned with Official Exam Topics
This topic carries the heaviest weight on the exam and tests whether you understand the landscape around Salesforce as a platform and a career path. Expect questions that ask you to match a business need to the right product, identify where someone would go to learn a specific skill, or distinguish between the work a developer does and the work an administrator handles. The cost shows up when you confuse product lines or assume all roles require code. β Learning...
This topic carries the heaviest weight on the exam and tests whether you understand the landscape around Salesforce as a platform and a career path. Expect questions that ask you to match a business need to the right product, identify where someone would go to learn a specific skill, or distinguish between the work a developer does and the work an administrator handles. The cost shows up when you confuse product lines or assume all roles require code.
β Learning resources and skill application
The exam wants you to know where someone would go to learn declarative automation versus Apex, or where a company would find pre-built solutions rather than building from scratch. Trailhead is the obvious answer for guided learning, but the scenario may point you toward community groups, documentation, or AppExchange depending on the need. Pay attention to whether the question describes a learner trying to close a knowledge gap, a team looking for a ready-made component, or a developer hunting for API reference material. Each need maps to a different resource, and picking the wrong one costs marks even when all the options sound plausible. The key is matching the scenario's intent to the resource's purpose, not listing every place Salesforce content lives.
β Product lines and Customer 360
Customer 360 is the umbrella term for Salesforce's suite of cloud products, and the exam tests whether you can pick the right one when given a use case. Sales Cloud handles opportunity and lead management. Service Cloud is for case handling and support workflows. Marketing Cloud manages campaigns and customer journeys. Commerce Cloud runs storefronts. The trap is assuming one product does everything or picking based on a keyword match rather than the actual workflow described. A scenario about tracking customer issues points to Service Cloud, even if the word "sales" appears elsewhere in the stem. Read for the process being automated, not the industry or the job title mentioned in passing.
β How companies use Salesforce and career roles
This section covers the operational side: how organisations deploy Salesforce to manage customer relationships, automate processes, and centralise data. The exam may describe a company's workflow and ask what Salesforce enables, or present a business problem and ask which capability applies. On the career side, you need to distinguish administrators from developers, architects from consultants, and business analysts from technical leads. Administrators configure the platform declaratively. Developers write code. Architects design solutions across multiple systems. The exam will describe a task and ask which role owns it, or present a career goal and ask which path fits. Mixing up declarative and programmatic responsibilities is the most common error here.
How Salesforce Ecosystem is tested
At thirty-two percent, this topic dominates the question count. Items present a scenario and ask you to choose the correct product, resource, or role. The scenarios are short but packed with detail, and the wrong answers are plausible if you skim. A question might describe a user trying to learn how to build a flow and offer Trailhead, AppExchange, Salesforce Help, and a developer forum as options. Three of those could work in some context, but only one fits the specific need described. Another item might outline a support workflow and ask which product handles it, with Sales Cloud and Service Cloud both appearing as options. The weight means you cannot afford to guess across this topic. If you miss half the ecosystem questions, you are already close to failing before the other topics begin. The trap is pattern-matching on a single word rather than reading the whole scenario. The demand is recognising intent and mapping it to the right part of the platform or the right learning path.
A practice test lets you see how Salesforce writes ecosystem scenarios and how the options are worded. The free demo covers this topic, so you can check whether you are reading the scenarios closely enough or jumping to the first familiar term before committing to the full bank.
The question below asks you to match a business need to the correct Salesforce product, using the details in the scenario to rule out the others.
A Salesforce associate wants to quickly create an org where they can learn, practice, and develop Salesforce skills.
Which type of org should they create from within Trailhead?
Navigation tests whether you know how to move around the Salesforce interface and where to go when you need to configure something. The exam assumes you have spent time in the platform, not just read about it. Questions ask where a user would find a specific record, how to reach a setup page, or which menu exposes a particular customisation option. The cost comes when you confuse the App Launcher with the Setup menu, or assume every configuration task lives...
Navigation tests whether you know how to move around the Salesforce interface and where to go when you need to configure something. The exam assumes you have spent time in the platform, not just read about it. Questions ask where a user would find a specific record, how to reach a setup page, or which menu exposes a particular customisation option. The cost comes when you confuse the App Launcher with the Setup menu, or assume every configuration task lives in the same place.
How Navigation is tested
Items describe a task and ask where in the interface you would go to complete it. A question might say a user needs to view all open cases assigned to them and ask which navigation element gets them there fastest. Another might describe an administrator who needs to create a custom field and ask where that configuration happens. The options will include plausible but incorrect menus, so you need to know not just that something can be done, but where the platform puts it. The weight at twenty-eight percent means navigation errors add up quickly. The trap is assuming the most obvious-sounding menu is correct without checking whether the task is user-facing or admin-facing. User tasks happen in the app itself; admin tasks happen in Setup. Mixing those two contexts loses marks. The demand is knowing the interface well enough that you do not have to guess based on the name of a menu.
Timed practice exposes whether you are pausing too long on navigation questions because you are unsure where a feature lives. The full question bank gives you enough repetitions across interface locations to spot the pattern of what goes where, so you stop second-guessing yourself under exam conditions.
The scenario below describes a user trying to locate information and asks which interface element delivers it most directly.
Get Cloudy Consulting gets 90^b of its business from trade shows. Sales reps create many lead records during these events, but they often forget to change the Lead Source field toTrade Show'.
What should help the sales reps when they create these lead records?
Data Model shifts focus to how Salesforce organises information and controls access to it. You need to understand the relationships between Accounts, Contacts, Leads, Opportunities, and Cases, and you need to know which tools enforce visibility rules and which ones protect data quality. The exam tests this through scenarios that describe a business requirement and ask which feature or configuration applies. Miss the distinction between a lookup and a master-detail relationship, or confuse sharing rules with validation rules, and you...
Data Model shifts focus to how Salesforce organises information and controls access to it. You need to understand the relationships between Accounts, Contacts, Leads, Opportunities, and Cases, and you need to know which tools enforce visibility rules and which ones protect data quality. The exam tests this through scenarios that describe a business requirement and ask which feature or configuration applies. Miss the distinction between a lookup and a master-detail relationship, or confuse sharing rules with validation rules, and you lose marks.
β Relationships between core objects
Accounts represent companies or organisations. Contacts are people, usually linked to an Account. Leads are unqualified prospects; when qualified, a Lead converts into an Account, a Contact, and optionally an Opportunity. Opportunities track deals in progress and relate to Accounts. Cases represent customer issues and can relate to Accounts or Contacts. The exam asks you to identify which object a piece of information belongs to, or how two objects connect. A question might describe a sales process and ask where the deal stage is tracked, or present a support workflow and ask which object holds the customer complaint. The trap is assuming all customer data lives on the Contact, or that Leads and Contacts are interchangeable. They are not. Leads exist before qualification; Contacts exist after. Mixing them up changes the answer.
β Data visibility and data integrity
Visibility controls who sees which records. Sharing rules, role hierarchies, and manual sharing all play a part, and the exam expects you to know which tool applies when. Organisation-wide defaults set the baseline. Sharing rules open access beyond that baseline. Role hierarchy grants access upward. The scenario will describe who needs to see what, and you pick the mechanism that delivers it. Data integrity is about keeping information accurate and consistent. Validation rules enforce field-level constraints. Duplicate rules flag or block duplicate records. The exam describes a requirement and asks which tool prevents bad data from entering the system. The trap is picking a visibility tool when the question asks about data quality, or vice versa. Read for whether the problem is access or accuracy.
How Data Model is tested
At twenty-five percent, this topic appears in roughly a quarter of the exam. Items describe a business process and ask which object relationship applies, or they outline a security requirement and ask which visibility feature solves it. The scenarios are specific enough that you cannot rely on general knowledge; you need to know what a master-detail relationship does that a lookup does not, or when a sharing rule is the right answer versus adjusting organisation-wide defaults. Another common pattern presents a data quality problem and asks which tool prevents it. Validation rules, duplicate rules, and required fields all appear as options, and the wrong ones sound reasonable if you are guessing. The demand is knowing the mechanics of each feature well enough to match it to the scenario. The trap is choosing based on a keyword in the option text rather than working through what the scenario actually requires.
Data model questions often hinge on distinctions between similar-sounding features. Working through a full question bank helps you see those distinctions repeatedly, so you stop confusing sharing rules with validation rules or master-detail with lookup when the scenario describes a relationship.
The item that follows presents a data visibility requirement and asks which Salesforce feature satisfies it without over-provisioning access.
Reports and dashboards cover how Salesforce surfaces data for analysis and decision-making. Reports pull records based on filters and display them in rows or summaries. Dashboards assemble multiple report components into a single view. The exam expects you to know what each can do, where you would build one, and what limits apply. With only two sub-topics and fifteen per cent of the weight, this section is narrower than the others, but it still punishes candidates who assume reports and...
Reports and dashboards cover how Salesforce surfaces data for analysis and decision-making. Reports pull records based on filters and display them in rows or summaries. Dashboards assemble multiple report components into a single view. The exam expects you to know what each can do, where you would build one, and what limits apply. With only two sub-topics and fifteen percent of the weight, this section is narrower than the others, but it still punishes candidates who assume reports and dashboards are interchangeable or who have never built one.
How Reports & Dashboards is tested
Items describe a requirement and ask whether a report or a dashboard meets it, or they present a use case and ask which report type applies. A question might say a manager needs to see a count of open cases by priority and ask whether that is a report, a dashboard component, or both. Another might describe a need to track opportunity pipeline over time and ask which visualisation fits. The options include report formats that sound plausible but do not match the data structure described. At fifteen percent, this topic contributes fewer questions than the others, but the pass mark is high enough that you cannot afford to drop most of them. The trap is choosing a dashboard when the requirement is a simple list, or picking a summary report when the scenario needs record-level detail. The demand is knowing what each format delivers and matching it to what the user actually needs to see.
The full question bank gives you enough reporting scenarios to recognise the pattern of when a tabular report is correct versus a summary or matrix format, and when the requirement calls for a dashboard instead. Repetition across variations builds confidence faster than re-reading static reference material.
What follows is a scenario describing an analytics requirement. The question asks which reporting feature satisfies it given the constraints outlined.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Plat-101 Exam Questions π