Salesforce Administrator Practice Exam.
Free practice test — 36 verified questions, instant feedback.

Answer: A
With a Private org-wide default, records are only visible to the owner and users above the owner in the role hierarchy, so placing VPs above reps automatically grants visibility without extra rules. Public Read/Write would let all reps see each other's accounts, which violates the requirement. 'View All Data' is an object-level permission that grants access to everything in the org, which is a much broader and less appropriate grant than using the hierarchy for this scoped need. Per-user sharing rules would work but require ongoing manual maintenance every time a VP or rep is added, unlike the role hierarchy which scales automatically.

Answer: A
Field-level security (set via profiles or permission sets) is the true security layer that determines whether a user can see or edit a field regardless of which page layout is assigned, while page layouts merely control the visual organization of fields, related lists, and buttons on a record page. Layouts cannot expose a field that field-level security hides, so security always wins over layout when the two conflict, making the reverse statement false. Both features apply equally to standard and custom objects, so restricting the comparison to only custom objects is incorrect.

Answer: A
Permission sets are designed to grant additional, granular permissions on top of a user's profile without requiring separate profiles, which keeps administration simple as team-specific needs change over time. Duplicating a profile creates maintenance overhead because any future change to the base profile now must be replicated across multiple profiles. Sharing rules control record-level access, not object or system permissions, so they cannot grant an extra permission like this. Modifying the base profile would incorrectly give the extra permission to every user, not just the collections team.

Answer: A
Object permissions (like Read) and tab visibility settings are independent in Salesforce; a profile can grant Read access to an object while still hiding its tab, which controls whether the tab shows up in the navigation, not whether the underlying records are accessible via search, related lists, or reports. A Public Read/Write org-wide default would make records more visible, not less, so it would not cause this symptom. Role hierarchy position affects record-level visibility, not whether a tab appears in the UI. Validation rules govern what data can be saved, and have no bearing on tab visibility.

Answer: A
The object must exist before fields can be added to it, fields must exist before they can be placed on a page layout, and field-level security is normally addressed after fields are created so profiles or permission sets can reference them correctly. Setting field-level security before the object or fields exist is not possible since there is nothing yet to secure. Similarly, a page layout cannot be built for an object that has not been created, and a validation rule cannot reference fields that do not yet exist.

Answer: A
Lightning App Builder allows multiple record pages to be created for the same object, and each page's activation settings support assignment by app, record type, and profile, letting different user populations see a tailored layout of components natively. Apex triggers operate on data changes in the backend and are not the mechanism for controlling which UI components render on a page. It is false that Lightning pages cannot vary by audience, since that assignment flexibility is a core feature. Building custom Visualforce overrides for this purpose is unnecessarily complex compared to the native declarative activation options.

Answer: A
Object Manager is the primary interface for creating and editing the detailed configuration of a specific object, including its fields, relationships, page layouts, and validation rules, whereas Schema Builder provides a diagrammatic, big-picture visualization of multiple objects and their relationships at once, which is useful for understanding data model structure. Schema Builder is a visualization and creation aid but is not a mandatory prerequisite step before objects can be created in Object Manager. Both tools work across standard and custom objects, so restricting either tool to only one object type is incorrect, and the two tools clearly serve different purposes rather than being identical.

Answer: A
Formula fields support conditional logic through functions like IF, letting administrators declaratively construct dynamic text or apply visual styling in supported contexts without any code, which fits the stated need. A required field only forces data entry and has no bearing on conditional display logic. Roll-up summary fields aggregate values from child records up to a parent and are unrelated to per-record conditional text on the Opportunity itself. Using an Apex trigger to accomplish simple conditional display logic ignores the declarative, no-code tools purpose-built for this exact requirement.

Answer: A
Record Types let administrators associate a subset of picklist values with a business process and pair that with a specific page layout, so the Government division can see only relevant Stage values while other divisions retain full access to the standard list. Workflow rules automate field updates, tasks, and notifications, and cannot delete or restrict picklist values org-wide. Cloning Opportunity into an entirely new custom object is unnecessary complexity when Record Types solve the exact use case natively. A validation rule enforcing that every picklist value must be used would actively break normal data entry rather than scope which values are available.

Answer: A
Salesforce list views natively support a Kanban display mode that groups records by a picklist field like Stage, which can be dropped onto a Lightning page as a component with no code required. A rich text component only displays static formatted text and cannot show live, grouped record data. Building a Visualforce page with a custom controller would require development effort that is unnecessary given the native Kanban capability. Approval processes route records for sign-off and have nothing to do with visualizing pipeline stages.

Answer: A
Lead assignment rules are purpose-built to evaluate criteria such as state or lead source and automatically assign ownership to the correct queue or user, which is exactly the routing behavior described. A picklist field alone stores a value but performs no automated action. Duplicate rules are designed to detect and manage duplicate records, not to route ownership. A daily report emailed to all reps does not perform automatic assignment and depends on manual follow-up, which does not meet the automation requirement.

Answer: A
Web-to-Lead is the native mechanism for capturing website form submissions directly into Salesforce as Lead records, and marketing automation platforms are designed to layer on lead scoring and automated nurture sequences that native core Salesforce does not provide out of the box. A validation rule only enforces data entry requirements and does not capture or nurture leads. Roll-up summary fields aggregate child record data onto a parent and have no role in lead capture or scoring. Editing the Contact page layout does nothing to address lead capture, scoring, or nurturing, and Contacts are a separate object from Leads until conversion.

Answer: A
The standard lead conversion process is built to simultaneously create or match an Account and Contact and optionally create an Opportunity, reflecting the business reality that a qualified lead becomes a tracked account relationship with associated people and potential deals. It is incorrect that conversion only touches the Contact, since Account creation/matching is a core part of the process. Lead conversion is a native, out-of-the-box Salesforce feature and does not require custom Apex to function. The original Lead record is not deleted; it is marked as converted and retained with a reference to the resulting records for historical traceability.

Answer: A
A summary report grouped by two fields with a numeric summary on Amount is exactly the report format needed to feed a chart and subsequently a dashboard component, matching the described requirement precisely. A workflow rule can send emails but does not produce grouped analytics or a visual chart on a dashboard. A validation rule only enforces data entry and does not aggregate or visualize data. A basic list view without grouping cannot show subtotals by Stage and Region and cannot be charted the way a summary report can.

Answer: A
Dynamic dashboards can be configured to run as the logged-in user, so when combined with record-level sharing rules or role hierarchy scoping on the underlying reports, each manager automatically sees only the data relevant to their own visibility, which is precisely the described requirement. Running a dashboard as one fixed user would show identical data to everyone regardless of who is viewing it, which is the opposite of the goal. Sharing dashboard data via an unauthenticated public link would expose data outside Salesforce's security model entirely, which is inappropriate for internal role-scoped reporting. Dashboards are not standard Salesforce objects with page layouts in the way custom or standard sObjects are, so this option does not apply.

Answer: A
Salesforce's native duplicate management framework (matching rules paired with duplicate rules) is designed to detect and optionally block or flag likely duplicate records during import tools like Data Import Wizard or Data Loader, which directly addresses the stated concern. Disabling validation rules affects data quality enforcement unrelated to duplicate detection and could actually let bad data in. Importing into an unrelated custom object would not create the needed Contact records at all and defeats the purpose. Manually reviewing 5,000 rows after the fact is inefficient and error-prone compared to using native duplicate prevention during the import itself.

Answer: A
Deleted records land in the Recycle Bin for a limited retention period, giving administrators a native safety net to restore records if a mass deletion turns out to be a mistake, which matches the requirement of temporary recoverability. Exporting to a spreadsheet before a hard delete with no Salesforce-side recovery path does not provide the requested short-window restore capability inside the system. Simply changing the Owner field does not remove the records or free up storage, since the records still exist and consume space. A validation rule controls what data can be saved and has no ability to block querying or serve as an archival mechanism.

Answer: A
Record-triggered Flow is the current recommended declarative automation tool for this kind of conditional, event-driven record creation, and it is inherently easier for future administrators to inspect and maintain visually compared to code. Writing an Apex trigger for a need that is fully achievable declaratively adds unnecessary technical debt and reduces maintainability for non-developer administrators. A page layout change only affects the visual arrangement of fields and cannot create related records automatically. A sharing rule affects record visibility, not automated task creation, so it does not address the stated need at all.

Answer: A
Salesforce has communicated that Flow is the go-forward strategic automation platform and provides migration tooling to help consolidate Workflow Rules and Process Builder logic into Flow, reducing long-term complexity of managing multiple overlapping automation tools on the same object. It is inaccurate to call Workflow Rules the newest tool, since they predate both Process Builder and Flow chronologically. Rebuilding everything in Apex ignores the declarative-first guidance and would abandon the low-code approach without a demonstrated need for code. It is also false that automation cannot be migrated or consolidated, since Salesforce explicitly provides tooling to assist with exactly that migration.

Answer: A
A record-triggered Flow that fires on the Account update can query related Contacts filtered to the primary flag via Get Records and then update the matching records, which precisely matches the described conditional, cross-object automation requirement. A screen flow requires manual user launch and would not automatically respond to an Account edit, failing the 'whenever the parent Account's Billing Address changes' requirement. A purely scheduled Flow with no trigger tied to the Account edit would run on a fixed cadence rather than immediately in response to the specific change, introducing unwanted latency and complexity. A formula field cannot write values into a different record's editable field, since formulas are read-only calculated fields on their own object.

Answer: A
Validation rules are purpose-built to block a save and present an inline error message when a specified logical condition, such as Close Date being earlier than today's date, evaluates to true, which is the simplest declarative fit for this exact requirement. A Flow that only sends an email alert would not stop the invalid save from completing, failing the core requirement to prevent bad data. Restricting edit access to the field entirely would stop legitimate future-dated updates too, which is overly broad and not what was requested. Filtering a report to hide past-dated records does nothing to prevent the invalid data from being saved in the first place; it only affects visibility in that specific report.

Answer: A
Salesforce provides case escalation rules (and more broadly, entitlement processes with milestones) that are explicitly designed to track time-based service commitments against configured business hours, including holiday exclusions, and to automatically reassign or escalate cases when a threshold is exceeded, which matches the requirement precisely. A validation rule can only block saves based on a condition; it has no concept of elapsed time-based escalation. A weekly scheduled report is a passive analytics tool that does not take automated action to reassign a case at all. A public group is merely a collection of users for sharing or assignment purposes and has no built-in time-tracking or escalation logic on its own.

Answer: A
Screen flows in the Flow tool are specifically designed to guide users through a structured, step-by-step interactive process with conditional branching based on prior answers, and can be embedded directly onto the Case record page for agents to launch during a call, which is exactly the described requirement. A static Knowledge article can provide reference information but cannot dynamically branch based on live agent input during the interaction. A page layout only arranges existing fields visually and has no capacity for interactive, conditional step-by-step guidance. A public group is purely a list of users for assignment or sharing purposes and provides no guided process functionality whatsoever.

Answer: A
Experience Cloud provides branded, externally-facing digital experiences (communities/sites) where authenticated external users like customers can log cases, track case status, and browse Knowledge articles, which directly matches every element of the described self-service requirement. A validation rule only enforces data entry conditions on save and provides no external-facing portal capability. A private internal list view is restricted to internal users by definition and cannot serve as a customer-facing self-service destination. Adjusting the internal role hierarchy changes internal visibility of records among employees and does nothing to expose functionality to external customers.

Answer: A
Entitlement processes support milestones (like first response and resolution time) that track elapsed time against a target, and these can be paired with time-dependent automation to trigger reminders or escalations as a milestone nears violation, matching the described measurement-and-reaction requirement precisely. A dashboard with no underlying report has no data source to display and cannot perform any automated reaction on its own. A bare priority picklist field alone stores a categorical value but has no time-tracking or automated milestone logic attached to it by itself. Deleting cases that take too long would destroy valuable service data and does not measure or address the underlying resolution-time problem at all.

Answer: A
Salesforce Knowledge's suggested articles capability, surfaced via the Knowledge component on the Lightning Case record page, automatically searches for and displays articles relevant to fields like Subject and Description as the agent works the case, which is exactly the described capability. A workflow rule automates field updates, tasks, or emails and has no mechanism to delete or curate Knowledge articles by relevance. A static Chatter post with hard-coded links does not dynamically adjust as new cases with different subjects come in, unlike the dynamic suggested-articles feature. A permission set governs access rights and, absent any Knowledge-related configuration, does nothing to surface or suggest articles at all.

Answer: A
Chatter provides an in-record collaboration feed where users can post updates, @mention colleagues to notify them, and attach files, all visible to anyone with access to that record, which matches the described collaboration requirement exactly. A validation rule can force data entry conditions but has no concept of a social feed, mentions, or file sharing. Emailing a spreadsheet around the team happens outside Salesforce entirely and does not tie collaboration history to the actual record for future reference. A sharing rule only affects record-level visibility and has no posting, tagging, or file-sharing functionality of its own.

Answer: A
The Salesforce mobile app supports offline access, allowing designated data to be cached on the device so users can view and edit records without a live connection, with changes syncing automatically once connectivity returns, directly addressing the described field scenario. A validation rule cannot enforce or require internet connectivity, since it only evaluates data conditions at save time on the server. A static image export of a dashboard is a frozen snapshot with no editing capability and does not allow logging calls or updating records. A public group only affects sharing and visibility permissions and has no bearing on offline mobile functionality at all.

Answer: A
The Activity Timeline together with configurable Quick Actions lets reps log calls/emails, create follow-up tasks, and update fields like Stage directly from the record page in a streamlined, minimal-click experience, which is precisely the productivity goal described. A read-only report cannot perform any of these actions since it has no interactive buttons for logging or updating data. Removing the Opportunity object from the app would prevent reps from accessing Opportunities at all, which is the opposite of a productivity improvement. Hiding the Stage field would actually block the rep from updating Stage, directly working against the stated goal.

Answer: A
A record-triggered Flow can declaratively create the Task record and chain an email alert or notification action to remind the assigned user, fully satisfying the automation requirement without any code. A static text component on a layout only displays informational text and cannot create records or send reminders on its own. Granting the broad 'Modify All Data' permission is a security-relevant access grant unrelated to building automated reminders and is excessive for this purely automation-focused need. A sharing rule only controls which users can see existing Task records and has no capability to create tasks or send reminders.

Answer: A
Salesforce's AI-assisted service capabilities (part of the broader Agentforce/AI feature set) are designed to generate contextual draft replies grounded in case details and Knowledge content, which agents then review and edit before sending, matching the scenario precisely. A validation rule only blocks or allows saves based on conditions and cannot generate any content, let alone block replies entirely as described. A static email template can insert basic merge fields but does not use AI to dynamically draft content based on the specific situation. A role hierarchy change affects record visibility among internal users and has nothing to do with generating reply content.

Answer: A
Responsible deployment of an autonomous service agent requires administrators to explicitly scope what the agent is allowed to handle, ground its responses in trusted data sources, and define clear escalation paths so complex or out-of-scope issues are properly handed off to a human, which is standard practice for safe and effective agent configuration. Granting a broad, high-risk permission like 'Modify All Data' with no other guardrails is a security anti-pattern rather than a best practice for agent deployment. Disabling all existing Case automation is unnecessary and would likely break unrelated processes rather than aiding a new agent's configuration. Skipping a review of what data the agent can access is a governance and security risk, not a recommended administrative step.

Answer: A
Grounding refers to constraining an AI agent's outputs to verified, trusted data sources like Knowledge articles and CRM records so its answers are traceable and accurate rather than freely generated, which directly matches the scenario's goal of reducing inaccurate responses. Disabling logging would reduce oversight and auditability, which works against building trust in agent behavior rather than improving accuracy. Allowing the agent to invent answers when no matching record exists is the opposite of grounding and would increase the risk of inaccurate responses. Removing all permission sets from the agent's underlying user would likely break its ability to access the very data needed to ground responses, rather than improving accuracy.

Answer: A
Sound governance for autonomous agents requires that their actions remain traceable and auditable, consistent with how Salesforce tracks other automated changes, so administrators and compliance teams can review what the agent did and why, satisfying the stated audit requirement. Assuming an AI agent cannot make mistakes is a flawed premise that would undermine the need for any oversight or audit trail at all. Granting anonymous access with no identifiable user context would make it impossible to attribute actions to the agent for audit purposes, directly working against the goal. Disabling field history tracking would remove visibility into changes rather than support the requested audit and compliance review.

Answer: A
Least privilege is a foundational security principle that applies to automated agents just as it does to human users, meaning the agent's underlying user should be granted only the specific object and field access necessary for its defined billing-question task, minimizing exposure of unrelated sensitive data. Granting a full System Administrator profile for convenience is a serious security anti-pattern that would expose far more data and functionality than the agent needs. Automation does not exempt an integration or agent user from field-level security review; trust should be scoped and verified, not assumed by default. Disabling validation rules to avoid errors would compromise data integrity rather than address access scoping, and is not a recommended security practice.

Answer: A
Sharing rules are designed to extend additional access, such as Read/Write, to a defined group of users beyond what the org-wide default provides, without changing that default for the entire organization, which precisely matches the stated need. Changing the org-wide default to Public Read/Write would grant edit access to every user in the org, not just the intended group, which is broader than required and could violate other security expectations. 'View All Data' grants read visibility across the org but does not grant edit capability, so it would not satisfy the need for write access. Removing the object from the group's profile would eliminate their access entirely, the opposite of the desired outcome.