ADX-201 Essentials for New Lightning Experience Administrators Exam Topics and Questions
These Salesforce Essentials for New Lightning Experience Administrators (ADX-201) 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 ADX-201 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 Essentials for New Lightning Experience Administrators certification exam.
Let's Practice Free Salesforce ADX-201 Questions Aligned with Official Exam Topics
This opening topic establishes the platform's architecture and navigation logic. You need to understand how Salesforce organizes data, where different objects sit in the stack, and how the multi-tenant model affects what you can and cannot do as an administrator. The cost comes when items present a scenario that requires you to know whether a solution lives in setup, configuration, or code. How Salesforce Fundamentals is tested Items present administrative tasks and reward recognition of where in the platform that...
This opening topic establishes the platform's architecture and navigation logic. You need to understand how Salesforce organizes data, where different objects sit in the stack, and how the multi-tenant model affects what you can and cannot do as an administrator. The cost comes when items present a scenario that requires you to know whether a solution lives in setup, configuration, or code.
How Salesforce Fundamentals is tested
Items present administrative tasks and reward recognition of where in the platform that task belongs. You might see a requirement to extend functionality and need to distinguish declarative options from those requiring development. Another common pattern asks you to identify which layer of the architecture controls a given behaviour. Marks are lost when candidates confuse similar-sounding features or assume a capability exists at the wrong level of the stack. Pay attention to what the platform provides out of the box versus what requires customization. The distinction between metadata and data also appears, usually in scenarios involving deployment or backup. Know the boundaries of the Lightning Experience interface and where Classic-only features still apply.
The practice test lets you see how architectural concepts are framed in item stems before you pay for the full bank. The PDF gives you every question on fundamentals in one place, which helps when you need to verify coverage of both exploration and architecture sub-topics without switching contexts.
The question below checks whether you can map a business need to the right part of the Salesforce stack.
Cloud Kicks has a team of product owners that need a space to share feedback and ideas with
just the product team.
How should the administrator leverage Salesforce to help the team collaborate?
Once the platform is understood, you move to the organisation-wide settings that affect every user. This topic covers company information, licensing, fiscal configuration, collaboration tools, user management, and login security. These are the decisions you make once and live with across the entire org. Mistakes here propagate to every record and every profile, so the exam tests whether you can sequence setup tasks correctly and choose settings that do not lock you into unintended constraints later. β Org-level configuration and...
Once the platform is understood, you move to the organisation-wide settings that affect every user. This topic covers company information, licensing, fiscal configuration, collaboration tools, user management, and login security. These are the decisions you make once and live with across the entire org. Mistakes here propagate to every record and every profile, so the exam tests whether you can sequence setup tasks correctly and choose settings that do not lock you into unintended constraints later.
β Org-level configuration and licensing
Company information and licensing decisions set the foundation for everything else. You need to know which licence type grants which capabilities, and how user limits interact with feature access. Fiscal year settings determine how reports aggregate data over time, and currency choices affect both display and conversion logic. Items test whether you recognise the consequences of a fiscal year change on historical data, or whether adding a currency requires additional steps to maintain accurate reporting. The exam also checks your understanding of when a licence type blocks access to a feature entirely versus when it simply hides the feature from the UI.
β User provisioning, collaboration, and login controls
User management spans creation, deactivation, password policies, and session settings. Collaboration tools include Chatter, groups, and file sharing, and the exam tests whether you can configure these to balance openness with data security. Login security controls cover IP restrictions, login hours, session timeouts, and multi-factor authentication. Items reward knowing which control applies at the profile level versus the org level, and what happens when multiple restrictions overlap. Candidates lose marks when they assume a login policy applied to one profile automatically extends to another, or when they overlook the interaction between login hours and time zones. The practical cost is a user locked out unintentionally or a security gap left open.
How The Big Picture: All Users is tested
Items present a scenario where a setting affects the entire user base and ask you to identify the consequence or the correct configuration sequence. You might see a company changing its fiscal year mid-cycle and need to recognise what happens to existing reports. Another pattern describes a licensing shortfall and asks which user type solves the need without exceeding budget. Login security items often combine multiple controls, such as IP ranges and login hours, then ask what happens when a user attempts access from a new location during restricted hours. Marks are lost when candidates choose the control that sounds most secure without checking whether it actually applies to the scenario. The exam rewards precision about where each setting lives and what it overrides.
A full question bank helps you spot patterns in how org-wide settings interact across items. One question might test fiscal year in isolation, another might combine it with currency and reporting, and seeing both types in volume shows you where your understanding has gaps.
The scenario below turns on the interaction between licensing and feature access across the organisation.
Universal Container wants to prevent its service team from accessing deal records. While
service users are unable to access deal list views, they are able to find the deal records via a search.
What options should the administrator adjust to fully restrict access?
After org-wide settings, the exam shifts to controlling what users can see and do. This topic covers profiles, permission sets, and field-level security. These three mechanisms layer on top of each other, and items test whether you know which one to adjust for a given requirement. The trap is choosing a tool that works but creates unintended side effects elsewhere in the org. How Feature and Object Access is tested Items describe a user who needs access to a feature...
After org-wide settings, the exam shifts to controlling what users can see and do. This topic covers profiles, permission sets, and field-level security. These three mechanisms layer on top of each other, and items test whether you know which one to adjust for a given requirement. The trap is choosing a tool that works but creates unintended side effects elsewhere in the org.
How Feature and Object Access is tested
Items describe a user who needs access to a feature or object and ask you to grant it without over-permissioning. You might see a scenario where a single user needs temporary access to an object that their profile does not include. Another pattern presents a field that should be visible to one role but hidden from another, then asks where to enforce that rule. The exam rewards knowing when to use a permission set instead of cloning a profile, and when field-level security is the only control that works. Marks are lost when candidates apply a profile change that affects dozens of users to solve a problem for one, or when they assume object permissions automatically grant field access. Pay attention to the cumulative effect of profiles and permission sets, because items often hinge on what happens when both are in play.
The practice test shows you how permission scenarios are worded under timed conditions, which matters because distinguishing profile from permission set language is half the battle. The PDF lets you review every feature-access item in sequence, making it easier to see where your instinct defaults to the wrong control.
The item below tests whether you can choose the right access control without creating unintended permissions elsewhere.
Feature access controls what users can do with an object. Record access controls which rows they see. This topic covers ownership, organisation-wide defaults, role hierarchy, sharing rules, teams, manual sharing, and restriction rules. These six mechanisms stack in a defined order, and the exam tests whether you can predict the outcome when multiple rules apply to the same record. The cost is highest here because one misconfigured default or sharing rule can expose thousands of records or hide them from...
Feature access controls what users can do with an object. Record access controls which rows they see. This topic covers ownership, organisation-wide defaults, role hierarchy, sharing rules, teams, manual sharing, and restriction rules. These six mechanisms stack in a defined order, and the exam tests whether you can predict the outcome when multiple rules apply to the same record. The cost is highest here because one misconfigured default or sharing rule can expose thousands of records or hide them from users who need them.
β Ownership, org-wide defaults, and role hierarchy
Record ownership determines the baseline: the owner always has full access unless restriction rules intervene. Organisation-wide defaults set the floor for everyone else, and the exam tests whether you know when to choose Private, Public Read Only, or Public Read/Write. Role hierarchy grants access upward, so a manager sees records owned by reports. Items reward understanding the interaction between these three layers. A common trap is setting an org-wide default too open because you forgot that hierarchy already grants upward visibility, or setting it too restrictive and then needing a dozen sharing rules to open it back up. The exam also checks whether you recognise that changing an org-wide default is not instant and can take hours to recalculate in a large org.
β Sharing rules, teams, manual sharing, and restriction rules
Sharing rules open access based on criteria or ownership, and the exam tests whether you can write a rule that grants access to the right group without over-sharing. Teams allow record-by-record sharing for specific objects like Opportunities and Cases, and items ask when a team is the right tool versus a sharing rule. Manual sharing lets an owner grant access to individuals, but it does not scale, and the exam checks whether you recognise when it is the only option. Restriction rules are the newest addition and work in reverse: they block access even when other rules would grant it. Items reward knowing that restriction rules can override role hierarchy and sharing rules, which breaks the usual additive model. Candidates lose marks when they assume all sharing is cumulative and miss the scenario where a restriction rule applies.
How Record Access is tested
Items present a record and a user, then ask whether the user can see or edit it. You need to trace through ownership, org-wide defaults, hierarchy, sharing rules, and restriction rules in order. A typical scenario gives you a Private default, a role hierarchy, and two sharing rules, then asks what happens when a user in a specific role tries to access a record owned by someone in another branch. Another pattern introduces a restriction rule and asks which users lose access. The exam rewards methodical evaluation of each layer and punishes guessing. Marks are lost when candidates stop at the first rule that grants access and ignore a restriction rule further down the chain, or when they assume hierarchy always wins. The practical cost is a security audit failure or a user unable to do their job because a sharing rule was scoped too narrowly.
Record access is where volume matters most. One question might test org-wide defaults in isolation, another combines hierarchy and sharing rules, and a third adds restriction rules into the mix. Seeing all three types in the full bank shows you which combinations you handle confidently and which ones still trip you up.
The scenario below asks you to evaluate multiple sharing mechanisms in sequence to determine final access.
With access controls in place, the exam moves to customizing the data model. This topic covers objects, standard and custom fields, relationship fields, and formula fields. These are the building blocks of every Salesforce implementation, and items test whether you can choose the right field type for a requirement and understand the limits each type imposes. The cost comes when you pick a field type that works today but cannot scale or cannot be used in the feature you need...
With access controls in place, the exam moves to customizing the data model. This topic covers objects, standard and custom fields, relationship fields, and formula fields. These are the building blocks of every Salesforce implementation, and items test whether you can choose the right field type for a requirement and understand the limits each type imposes. The cost comes when you pick a field type that works today but cannot scale or cannot be used in the feature you need later.
β Objects and field types
An object is a table, and a field is a column. Standard objects like Account and Contact come with the platform; custom objects are yours to define. The exam tests whether you know when to extend a standard object with custom fields versus when to build a custom object and relate it. Field types include text, number, picklist, date, checkbox, and more, and each has validation and reporting behaviour that matters. Items reward knowing that a text field holding numbers cannot be summed in a report, or that a picklist is easier to maintain than a text field when values are controlled. Candidates lose marks when they choose a long text area for data that needs to appear in a formula, or when they assume a custom object can do everything a standard object does without checking platform limits.
β Relationships and formulas
Relationship fields connect objects. Lookup and master-detail are the two types, and the exam tests the differences relentlessly. Master-detail enforces cascade delete and rolls up summary fields; lookup does neither but allows the child to exist without a parent. Formula fields calculate values from other fields on the same record or across a relationship. Items ask you to identify when a formula can span a relationship and when it cannot, or what happens when a formula references a field that the user cannot see. The exam rewards knowing that formulas are read-only, recalculate when source fields change, and have a compile size limit. Marks are lost when candidates try to write a formula that references a field across a lookup in the wrong direction, or when they assume a roll-up summary can work on a lookup relationship.
How Standard Functionality Customizations is tested
Items describe a business requirement and ask you to choose the field type or relationship that meets it. You might see a need to track a value that depends on two other fields and need to recognise that a formula field is the solution. Another pattern presents a requirement to delete a parent record and have all children delete automatically, which rewards knowing that only master-detail supports cascade delete. Formula items often give you a requirement and ask whether the formula can be built, or they describe a formula behaviour and ask what happens when a source field is hidden by field-level security. The exam punishes assuming that all field types work in all features; for example, long text area fields cannot be used in filters or external IDs. Candidates also lose marks when they confuse lookup with master-detail or forget that changing a lookup to master-detail requires existing records to have a parent.
Customization questions appear across every topic, but this section concentrates them. The demo gives you a few for free so you can check whether formula and relationship wording makes sense before committing. The full bank lets you work through field-type scenarios in volume, which is the only way to internalize which types have which restrictions.
The question below asks you to match a business requirement to the field or relationship type that supports it.
The final topic covers how users interact with the data model you have built. This includes applications, home pages, tabs, list views, page layouts, dynamic forms, buttons, links, actions, record types, business processes, and Path. These are the tools that make the org usable, and items test whether you can configure the UI to guide users without restricting flexibility. The trap is over-customizing to the point where maintenance becomes unsustainable or under-customizing so users see irrelevant fields and waste time....
The final topic covers how users interact with the data model you have built. This includes applications, home pages, tabs, list views, page layouts, dynamic forms, buttons, links, actions, record types, business processes, and Path. These are the tools that make the org usable, and items test whether you can configure the UI to guide users without restricting flexibility. The trap is over-customizing to the point where maintenance becomes unsustainable or under-customizing so users see irrelevant fields and waste time.
β Applications, home pages, tabs, and list views
Applications are containers for tabs, and tabs surface objects, Visualforce pages, or external URLs. The exam tests whether you know that tab visibility is controlled by profile and app assignment, and that hiding a tab does not remove access to the underlying object. Home pages can be customized with components in Lightning, and items ask you to identify which component meets a requirement or what happens when a component references data the user cannot see. List views filter records on an object, and the exam checks whether you understand the difference between a personal list view and a public one, and what happens when a list view filter references a field that gets deleted. Marks are lost when candidates assume that removing a tab prevents users from searching for or accessing records via links.
β Page layouts, dynamic forms, and actions
Page layouts control which fields appear when viewing or editing a record, and the exam tests whether you know that field-level security overrides page layout visibility. Dynamic forms let you place fields as components on a Lightning page, offering finer control than a page layout alone. Buttons, links, and actions let users trigger behaviour: a button might open a URL, a link might run a report, and an action might create a record. Items reward knowing when to use a standard action versus a custom one, and what happens when a button references a field or object the user cannot access. Candidates lose marks when they confuse page layout assignment with record type assignment, or when they assume a button will work for all users without testing permissions.
β Record types, business processes, and Path
Record types segment records on the same object and assign different page layouts and picklist values to each type. Business processes control which picklist values are available for a given record type, most commonly on Lead and Opportunity. Path is a visual guide that surfaces key fields and guidance text as a record moves through stages. The exam tests whether you can configure record types without creating redundant page layouts, and whether you understand that record type controls picklist values only when a business process is also assigned. Items ask what happens when a user creates a record and has access to multiple record types, or when a process automation changes a record to a type the user cannot normally create. Marks are lost when candidates assume record types restrict access to records, which they do not, or when they forget that Path is optional and requires a picklist field to drive it.
How The Existing User Interface (UI) is tested
Items present a UI requirement and ask you to choose the configuration that meets it. You might see a need to show different fields to different user groups and need to decide between page layouts, dynamic forms, and field-level security. Another pattern describes a button that works for some users but not others, and asks you to identify the missing permission or the field reference that fails. Record type items often combine page layout assignment, picklist value filtering, and business process logic in one scenario, then ask what a user sees when creating a record. The exam rewards knowing the order of evaluation: field-level security always wins, then page layout or dynamic form visibility, then record type and business process. Candidates lose marks when they configure the UI without considering permissions, or when they assume a change to a page layout applies to all users immediately without checking profile assignment. Path items test whether you know it requires a picklist and that guidance text is optional.
UI customization spans seven sub-topics, and the question bank shows you which ones you handle instinctively and which ones need more work. Timed practice helps because UI items often include screenshots or long requirement descriptions, and you need to parse them quickly under exam conditions.
The item below combines page layout, record type, and permission logic to test whether you can predict what a user sees.
UI configuration determines what users see; data management determines what they work with. This topic covers backup, import, export, update, mass delete, mass transfer, and data quality tools. These operations touch every record in the org, and errors compound quickly. A bad import can create thousands of duplicate accounts. A mass delete without a backup can lose years of history. Items test whether you know which tool to use for a given data operation and what happens when the data...
UI configuration determines what users see; data management determines what they work with. This topic covers backup, import, export, update, mass delete, mass transfer, and data quality tools. These operations touch every record in the org, and errors compound quickly. A bad import can create thousands of duplicate accounts. A mass delete without a backup can lose years of history. Items test whether you know which tool to use for a given data operation and what happens when the data violates validation rules or lacks required relationships.
β Backup, import, and export
Salesforce offers weekly or monthly export schedules, and the exam tests whether you know that exports include attachments only if you select that option, and that large orgs may need to request files in multiple parts. Backup is not automatic; you must schedule it. Import tools include Data Import Wizard and Data Loader. The wizard handles up to 50,000 records and works in the browser; Data Loader is a desktop client with no record limit. Items reward knowing which tool supports which objects, and that the wizard cannot update certain standard objects that Data Loader can. Candidates lose marks when they assume all objects can be imported via the wizard, or when they forget that an import updates existing records only if you map a unique identifier like Record ID or an external ID field.
β Mass operations and data quality
Mass delete removes records in bulk and sends them to the recycle bin for 15 days. Mass transfer changes ownership of many records at once, and the exam tests whether you know that transfer triggers sharing recalculation and can take time in large orgs. Data quality tools include duplicate management, which identifies potential duplicates using matching rules and blocks or alerts on creation, and data cleansing tools like Data.com Clean or third-party integrations. Items ask when to use a matching rule versus a duplicate rule, and what happens when a duplicate rule is set to block instead of alert. Marks are lost when candidates assume mass delete is permanent, or when they configure a duplicate rule without testing its impact on existing records and integrations that create data programmatically.
How Data Management is tested
Items describe a data operation and ask you to choose the tool that completes it correctly. You might see a requirement to import 100,000 records with relationships to multiple objects and need to recognize that Data Loader is the only option. Another pattern presents a scenario where records must be deleted but might need to be restored later, which rewards knowing that mass delete uses the recycle bin and that the bin empties after 15 days. Duplicate management items often describe a rule configuration and ask what happens when a user tries to save a record that matches an existing one. The exam also tests whether you understand that importing data does not bypass validation rules, so an import can fail partway through if rows violate a rule. Candidates lose marks when they choose the import wizard for objects it does not support, or when they assume that exporting data includes all fields without checking the export file definition.
Data management items often hinge on knowing which tool supports which operation, and a full question bank gives you enough volume to see every combination. The free demo shows you whether the item style matches your expectation before you invest in the complete set.
The scenario below asks you to select the data operation tool that meets the requirement without violating platform limits.
Data exists; now you automate what happens to it. This topic covers automation fundamentals, validation rules, lead and case management, workflows, processes, and approval processes. These are the declarative tools that enforce business logic without code. The exam tests whether you can sequence automations correctly, predict what fires when, and avoid conflicts between overlapping rules. A misconfigured validation rule can block legitimate updates. An approval process without the right entry criteria can lock records unintentionally. β Validation rules and automation...
Data exists; now you automate what happens to it. This topic covers automation fundamentals, validation rules, lead and case management, workflows, processes, and approval processes. These are the declarative tools that enforce business logic without code. The exam tests whether you can sequence automations correctly, predict what fires when, and avoid conflicts between overlapping rules. A misconfigured validation rule can block legitimate updates. An approval process without the right entry criteria can lock records unintentionally.
β Validation rules and automation fundamentals
Validation rules prevent a record from saving if a formula evaluates to true. They fire before the record is committed, which means they can block workflows and processes from running. The exam tests whether you can write a validation formula that enforces a requirement without creating unintended side effects, and whether you understand that validation rules apply to all users unless you add a profile or permission check to the formula. Automation fundamentals include knowing that Salesforce evaluates rules in a specific order: validation rules, assignment rules, auto-response rules, workflow rules, processes, and flows. Items reward recognizing that a validation rule will prevent a process from updating a field, or that a workflow field update can trigger another workflow if re-evaluation is enabled. Candidates lose marks when they assume automation tools fire simultaneously or when they forget that validation errors surface to the user as a message, not a silent failure.
β Lead and case automation, workflows, and processes
Lead assignment rules route incoming leads to queues or users based on criteria. Case assignment and auto-response rules do the same for cases, and escalation rules move cases up the chain when SLA thresholds are breached. The exam tests whether you know that only one assignment rule can be active per object at a time, and that auto-response rules send one email per case creation. Workflow rules trigger field updates, email alerts, tasks, or outbound messages when criteria are met. Process Builder replaced workflow for most use cases and allows more complex logic, including updating related records. Items ask when to use workflow versus process, and what happens when both are active on the same object. Marks are lost when candidates configure a workflow to update a related record, which it cannot do, or when they assume a process can send an outbound message, which requires workflow or code.
β Approval processes
Approval processes lock a record and route it through one or more approval steps. The exam tests entry criteria, approver assignment, actions on submission, approval, rejection, and recall. You need to know that a locked record cannot be edited unless the approval process allows it or the user has the Modify All Data permission. Items reward understanding that initial submission actions fire immediately, while final approval or rejection actions fire only after all steps complete. A common trap is configuring an approval process without setting criteria, which means every record that enters the process gets locked. Another is forgetting that email notifications to approvers are not automatic; you must add an email alert action. Candidates lose marks when they assume approval processes can run in parallel, which they cannot, or when they overlook that a recalled submission does not unlock the record automatically unless the process is configured to allow it.
How Declarative Automation is tested
Items present a business requirement and ask you to choose the automation tool that meets it. You might see a need to prevent a record from saving unless two fields are populated, which rewards knowing that a validation rule is the solution. Another pattern describes a requirement to update a field on a related record when a workflow fires, which is impossible with workflow alone and requires Process Builder or Flow. Approval process items often combine entry criteria, step criteria, and actions, then ask what happens when a record is submitted or rejected. The exam also tests order of execution: a validation rule that fires before a workflow might block the workflow from running, or a process that updates a field might cause a validation rule to fail on re-evaluation. Candidates lose marks when they configure automation without considering what other automation is already active, or when they assume that all automation tools can perform the same actions.
Automation scenarios can combine validation, workflow, process, and approval logic in a single item, and working through the full bank in timed conditions shows you which combinations you evaluate correctly under pressure and which ones need another pass.
The item below tests whether you can choose the right automation tool and predict its interaction with other active rules.
Workflow and Process Builder are legacy. Flow is the unified automation tool going forward, and this topic tests whether you can build, combine, and deploy flows. The sub-topics cover flow definition, field updates, building and combining multiple flows, deploying flows via Lightning components, and order of execution. Flow is more powerful than the tools it replaces, but that power comes with complexity. Items test whether you know when a flow should run before save versus after save, and what happens...
Workflow and Process Builder are legacy. Flow is the unified automation tool going forward, and this topic tests whether you can build, combine, and deploy flows. The sub-topics cover flow definition, field updates, building and combining multiple flows, deploying flows via Lightning components, and order of execution. Flow is more powerful than the tools it replaces, but that power comes with complexity. Items test whether you know when a flow should run before save versus after save, and what happens when a flow fails partway through.
β Flow types and field updates
Flow comes in several types: screen flows that guide users through a wizard, record-triggered flows that fire on create or update, scheduled flows that run at a set time, and autolaunched flows that other automation calls. The exam tests whether you can choose the right type for a requirement. A screen flow requires user interaction; a record-triggered flow does not. Building a flow to update a field requires knowing that before-save flows run in the same transaction and cannot send emails or create child records, while after-save flows can do both but cannot update the triggering record without a separate update element. Items reward understanding that a flow can loop through a collection of records and perform actions on each, and that loops can hit governor limits if the collection is large. Candidates lose marks when they build an after-save flow to update the triggering record and forget to query it first, or when they assume a before-save flow can call an external API.
β Combining flows, deployment, and execution order
Flows can call other flows using subflows, which allows modular design and reuse. The exam tests whether you know that a subflow inherits the transaction of the parent flow, and that errors in a subflow roll back the entire transaction unless fault handling is configured. Deploying a flow with a Lightning component means embedding it on a page or exposing it as an action, and items ask when to use a component versus a quick action. Order of execution determines when flows fire relative to validation rules, workflows, and processes. Record-triggered flows run after workflows but before processes if they are set to run before save, and after processes if they run after save. Items reward knowing that a before-save flow can prevent a record from being created if it includes a fault path that stops the transaction. Marks are lost when candidates assume all flows fire at the same point in the save operation, or when they deploy a flow without activating it and wonder why nothing happens.
How The Future of Automation: Flow is tested
Items describe an automation requirement and ask you to build or configure a flow that meets it. You might see a need to update a related record when a field changes, which rewards knowing that an after-save record-triggered flow is the correct type. Another pattern presents a requirement to guide a user through multi-step data entry, which requires a screen flow. The exam also tests flow execution order: a scenario might describe a record update that triggers a validation rule, a workflow, and a flow, then ask which one fires first or what happens if one fails. Candidates lose marks when they choose a before-save flow for a requirement that needs to send an email, or when they build a flow that queries and updates records in a loop without bulkifying the logic, which causes the flow to hit governor limits in production. Fault handling items test whether you know that an unhandled error stops the flow and rolls back all changes.
Flow items test both configuration and conceptual understanding, and the practice test lets you see how flow scenarios are worded before you commit to the full set. The PDF groups all flow questions together, which helps when you need to compare before-save and after-save logic side by side.
The question below checks whether you can select the correct flow type and predict its behavior in the order of execution.
Automation acts on data. Sometimes you need a new object to hold that data. This topic covers creating custom objects, building tabs, deploying change sets, and generating mobile layouts. These are the tasks you perform when extending the data model beyond what standard objects provide. Items test whether you know the steps in the correct order and what happens when a dependency is missing. Deploy a tab before the object exists and the deployment fails. Forget to include a field...
Automation acts on data. Sometimes you need a new object to hold that data. This topic covers creating custom objects, building tabs, deploying change sets, and generating mobile layouts. These are the tasks you perform when extending the data model beyond what standard objects provide. Items test whether you know the steps in the correct order and what happens when a dependency is missing. Deploy a tab before the object exists and the deployment fails. Forget to include a field in a change set and the page layout that references it breaks in the target org.
β Custom objects and tabs
Creating a custom object requires defining its label, plural label, and API name, then choosing whether to allow reports, activities, and tracking. The exam tests whether you know that the API name must be unique and ends with __c, and that once an object is created its API name cannot be changed. Tabs make the object accessible in the UI, and you assign the tab to apps and set its visibility per profile. Items reward knowing that a tab is not required for an object to function; users can still access records via search, related lists, or links. Candidates lose marks when they assume that creating an object automatically creates a tab, or when they delete an object without checking whether other objects have lookup or master-detail relationships pointing to it, which would block the deletion.
β Change sets and mobile layouts
Change sets move metadata from one org to another, typically from sandbox to production. The exam tests whether you know that a deployment connection must exist between the orgs before a change set can be sent, and that the receiving org must accept and deploy the inbound change set. You need to add all dependencies to the change set: if you send a page layout, you must also send any custom fields it references. Mobile layouts control which fields appear in the Salesforce mobile app, and items ask when to configure a mobile layout versus relying on the default compact layout. Marks are lost when candidates send a change set without including dependent components, or when they assume a change set can move data as well as metadata, which it cannot. Another trap is forgetting that deploying a change set does not activate everything automatically; flows and validation rules may need manual activation in the target org.
How New Objects is tested
Items present a scenario where you need to extend the data model and ask you to complete the task in the correct sequence. You might see a requirement to create an object, add fields, build a tab, and deploy everything to production, then need to identify which step must happen first or which dependency is missing from the change set. Another pattern describes a deployment that fails and asks you to identify the cause, which rewards knowing that missing fields, profile assignments, or page layout references are common culprits. Mobile layout items test whether you know that compact layouts control what appears at the top of a record in mobile, and that you can assign different compact layouts to different record types. Candidates lose marks when they assume all metadata can be deployed via change sets, which is not true for certain settings like org-wide defaults or fiscal year configuration, or when they deploy a change set to production during business hours without testing it in a sandbox first.
Change set questions often describe multi-step deployments with missing dependencies, and seeing enough of them in the question bank helps you recognize the pattern quickly. Timed practice matters because deployment items can include long requirement lists that you need to parse under exam conditions.
The scenario below asks you to identify the correct deployment sequence and the dependencies required for a successful change set.
Objects hold data. Reports surface it. This final topic covers report components, filters, formulas, conditional formatting, charts, exports, subscriptions, and dashboards. These are the tools that turn raw data into decisions, and items test whether you can build a report that answers the question without including irrelevant rows or columns. The trap is choosing the wrong report type or applying a filter that excludes the records you need. β Report types, filters, and formulas A report type determines which objects...
Objects hold data. Reports surface it. This final topic covers report components, filters, formulas, conditional formatting, charts, exports, subscriptions, and dashboards. These are the tools that turn raw data into decisions, and items test whether you can build a report that answers the question without including irrelevant rows or columns. The trap is choosing the wrong report type or applying a filter that excludes the records you need.
β Report types, filters, and formulas
A report type determines which objects and fields are available. Standard report types cover common use cases like Accounts with Opportunities; custom report types let you define your own object relationships. The exam tests whether you know that a report can include up to four related objects and that the primary object determines the row count. Filters limit which records appear, and you can apply standard filters like date ranges or custom filters on any field. Cross filters let you include or exclude records based on related object criteria without adding the related object to the report. Report formulas calculate values within the report itself, and items reward knowing that a formula can reference summary fields but cannot update data. Marks are lost when candidates choose a report type that does not include the relationship they need, or when they apply a filter that excludes records unintentionally.
β Formatting, charts, and dashboards
Conditional formatting highlights rows or cells based on criteria, such as coloring overdue tasks red. Charts visualize report data, and the exam tests whether you can choose the right chart type for the data: bar charts for comparisons, line charts for trends, pie charts for proportions. Exporting a report generates a file in Excel or CSV format, and subscriptions send the report to users on a schedule. Dashboards combine multiple reports into a single view, and each dashboard component sources data from one report. Items ask when to use a dashboard filter versus a report filter, and what happens when a user views a dashboard but lacks access to the underlying report data. Candidates lose marks when they assume a dashboard runs in real time, which it does not unless set to refresh on load, or when they configure a dashboard component to display data the viewer cannot see, which results in an error or blank component.
How Analytics is tested
Items describe a reporting requirement and ask you to build or configure the report correctly. You might see a need to show all accounts that have no opportunities, which rewards knowing that a cross filter with a without condition is the solution. Another pattern presents a dashboard requirement and asks whether the viewer will see data, which depends on the dashboard running user setting and the viewer's sharing access. Formula items test whether you can write a formula that calculates a percentage or a date difference, and whether you understand that formulas in reports cannot reference fields from unrelated objects. The exam also tests report limits: you can schedule up to five reports to run at the same time, and a report can return a maximum of 2,000 rows in the UI or 50,000 in an export. Candidates lose marks when they build a report that times out because it queries too many records, or when they assume a dashboard will update instantly without configuring the refresh setting.
Analytics items span five sub-topics, and the full bank shows you which areas you handle confidently and which ones still need work. The demo includes a few reporting questions so you can verify that the item wording matches your understanding before purchasing.
The item below tests whether you can configure a report to answer the requirement without including unnecessary data or violating platform limits.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full ADX-201 Exam Questions π