Salesforce Platform Administrator II Free Practice Test | 200+ Questions 2026

Salesforce Platform Administrator II Practice Test

The Salesforce Platform Administrator II certification is designed for experienced administrators who are ready to solve more complex security, automation, data, application, and deployment problems. It goes beyond basic feature recognition and asks whether you can select a maintainable solution for a detailed business requirement. A Salesforce Platform Administrator II practice test helps you measure that advanced decision-making ability before relying on a score alone. You can also Discover practice tests by exam and vendor while organizing your wider certification learning plan.

Salesforce describes Platform Administrator II holders as seasoned administrators who can use advanced platform features to solve a range of business problems. Students should already understand the everyday responsibilities covered by the Salesforce Platform Administrator credential. Platform Administrator is the official prerequisite for Platform Administrator II.

This guide explains all seven current topic areas in clear language. It also shows you how to combine practice testing with hands-on administration, how to recognize common mistakes, and how to develop the reasoning expected from an advanced administrator. Certification facts and domain percentages were checked against official Salesforce and Trailhead sources in August 2026.

Is Platform Administrator II the Same as Advanced Administrator?

Salesforce Certified Platform Administrator II is the current name for the credential previously known as Salesforce Certified Advanced Administrator. Students may still find older Trailhead URLs, course references, bookmarks, and community discussions using the Advanced Administrator wording.

The knowledge remains focused on advanced administration, but students should use the current credential page and official outline when choosing resources. A page that uses the old name may still be helpful if its topics match the seven current domains. It should not be treated as current simply because it ranks well in search.

Salesforce’s current credential page describes certified professionals as seasoned administrators who can use advanced features and functionality to solve varied business problems.

Who Should Prepare for Platform Administrator II?

This certification suits administrators who have moved beyond simple setup tasks and regularly make decisions that affect multiple teams, large datasets, complex automation, security, reporting, and deployment.

The official prerequisite is Salesforce Certified Platform Administrator. In practical terms, students should already be comfortable with:

• Users, profiles, permission sets, roles, and record sharing.
• Standard and custom objects, fields, relationships, and record types.
• Sales and service processes.
• Reports and dashboards.
• Data import, export, validation, and duplicate management.
• Flow and approval fundamentals.
• Sandboxes and basic change-management concepts.

Platform Administrator II is not a repetition of the first administrator credential. It expects deeper judgment. You may need to compare several possible designs, predict downstream effects, troubleshoot a failed process, or recommend a solution that balances security, user experience, scalability, and maintenance.

Why Use a Platform Administrator II Practice Test?

Advanced administration is difficult to learn through memorization because Salesforce features interact. A sharing choice can change report results. A relationship type can affect ownership and roll-up options. A flow can conflict with validation, assignment, or another automation. A change that works in a sandbox can still fail during deployment because a dependency is missing.

A useful practice-test routine can help you:

• Identify advanced topics that are still understood only at a basic level.
• Compare multiple valid-looking solutions against the complete requirement.
• Practice reasoning across security, data, automation, and application boundaries.
• Recognize the effect of order of execution.
• Improve troubleshooting instead of relying on trial and error.
• Review mistakes by official domain.
• Learn why a simpler or purpose-built solution is often preferable.

Treat a practice score as evidence from one session, not a certification guarantee. Review every incorrect answer, uncertain answer, and correct guess. The important question is whether you can explain the solution without seeing the options.

Salesforce Platform Administrator II Topics Explained

1. Security and Access — 20%

Security and Access is one of the two largest domains. It tests advanced control of record access, field access, authentication, profiles, permission sets, delegated administration, territories, and complex account models.

Record and field access

Advanced security scenarios require you to evaluate the complete sharing model. Start with organization-wide defaults, then consider role hierarchy, sharing rules, teams, territories, manual sharing, and controlled-by-parent behavior. Object permissions and field-level security must also be checked because record sharing cannot grant access to an object or field that the user is not permitted to use.

Folder access matters for reports, dashboards, and email templates. A user may have access to business records but still be unable to open a report because its folder is not shared appropriately. The reverse is also important: access to a report folder does not automatically grant access to every underlying record.

Use this sequence when troubleshooting:

1. Can the user authenticate?
2. Can the user access the application and object?
3. Can the user access the required field?
4. Can the user access the record?
5. Can the user access the folder or feature involved?

Profiles, permission sets, and delegated administration

Custom profiles provide baseline settings and permissions. Permission sets and permission-set groups add access without creating many profile variations. Session-based permission sets can provide sensitive access only during an approved or elevated session.

Delegated administration allows selected users to complete limited administrative work without receiving full system-administrator access. Study what can be delegated and how to avoid granting unnecessary control.

Authentication and sensitive access

Understand multi-factor authentication, single sign-on, login policies, session security, trusted locations, connected-app access, and the implications of authentication changes. Security decisions should protect the organization without creating unmanaged workarounds.

Enhanced Transaction Security and Event Monitoring can support policies and detection for sensitive activity. Learn the difference between controlling access before an action and monitoring or responding to activity after it occurs.

Complex account and territory models

Review person accounts, business accounts, contacts, contacts related to multiple accounts, account teams, and Enterprise Territory Management. These models solve different business needs and can affect sharing, reporting, and sales responsibilities.

For hands-on preparation, create users with different permission sets and roles, then test object, field, record, and folder access separately. Document why each user can or cannot complete a task.

2. Process Automation — 20%

Process Automation is the other 20% domain. It focuses on selecting the right automation approach for a complex requirement, understanding tool capabilities and limits, troubleshooting declarative automation, and reasoning about order of execution.

Selecting an automation approach

Flow Builder is the central declarative automation tool. You should understand record-triggered flows, screen flows, autolaunched flows, scheduled flows, subflows, asynchronous paths, scheduled paths, decisions, loops, record operations, and fault handling.

The best design is not always the flow with the most elements. Prefer clear entry criteria, reusable logic, efficient record operations, and useful fault paths. Avoid database actions inside loops where possible because they can create performance and limit problems.

The official outline also expects awareness of approval processes, workflow rules, formulas, and situations that may require code. Workflow rules may still appear in older orgs, while Flow is the strategic declarative tool for current development. An administrator should know how legacy automation behaves during migration or troubleshooting.

Order of execution

Order of execution describes the sequence in which Salesforce validation, before-save logic, after-save logic, assignment, workflow, other automation, and database actions occur. You do not need to turn the entire sequence into an isolated memory list. Learn how to trace why a field changed, why automation ran twice, or why a validation blocked a later action.

A strong troubleshooting method is:

• Identify the transaction that starts the process.
• List every automation that can respond.
• Confirm the entry criteria for each item.
• Determine when each item runs.
• Review field changes that could trigger reevaluation.
• Use debug information and flow error details.
• Test with one controlled record before wider execution.

Approvals and complex processes

Approval processes include entry criteria, initial submission actions, approver routing, record locking, approval actions, rejection actions, recall, and delegated approvers. Practice scenarios where approvers depend on record values, managers, queues, or related data.

Some requirements need more than one tool. For example, Flow may prepare a record, an approval process may route it for review, and a post-approval action may update related records. The administrator must make each responsibility clear and avoid circular behavior.

3. Objects and Applications — 19%

Objects and Applications covers advanced data modeling and user-experience design. You need to choose object relationships and interface tools based on business requirements.

Advanced relationship design

Review lookup, master-detail, self, hierarchical, and many-to-many relationships. A junction object commonly uses two master-detail relationships to connect records in a many-to-many model.

Relationship choice affects record ownership, required parent connections, cascade deletion, sharing, and roll-up summary support. Do not choose master-detail only because a roll-up is convenient. Confirm that the ownership and deletion behavior also fit the business requirement.

Schema Builder helps visualize and modify a data model. Standard and custom related lists help users see connected information. Record types and business processes can support different workflows without creating unnecessary duplicate objects.

Advanced application and page design

App Manager controls Lightning apps and their navigation. Lightning App Builder creates record, app, and home pages. Dynamic Forms can place fields and sections as individual components and apply visibility rules. Standard components, custom components, the Lightning console, and page activation assignments support different user experiences.

The Lightning page analysis capability helps identify performance concerns. A visually complex page is not automatically effective. Administrators should balance useful information, component visibility, performance, and mobile behavior.

When practicing, take one object and create different experiences for sales and service users. Use record types only when the processes or picklist values genuinely differ. Use component visibility when the underlying process is shared but the interface needs contextual guidance.

4. Data and Analytics Management — 13%

This domain combines data quality, imports, external access, archiving, advanced reports, and dashboards.

Data quality and lifecycle

Study validation rules, duplicate rules, matching rules, formulas, lookup filters, required fields, external IDs, and enrichment approaches. Data quality also includes retention and archiving. Records should remain accurate and useful without allowing the production org to become an unmanaged archive.

Big objects support very large datasets with specific design and query considerations. External objects can expose external data in Salesforce through supported connections. Data warehouses and data lakes serve broader analytics or storage purposes. Choose a method based on access needs, data volume, freshness, reporting, ownership, and retention.

Import and migration decisions

Compare the Data Import Wizard, Data Loader, APIs, and supported third-party tools. Consider record volume, supported objects, update or upsert needs, external IDs, relationships, ownership, validation, automation, and error handling.

Before a major import, prepare a rollback or correction plan. Test a small sample, review error files, confirm ownership, and check how automation changes the incoming data.

Advanced reporting and dashboards

Platform Administrator II expects more than basic report filters. Review custom report types, reporting snapshots, joined reports, cross filters, bucket fields, row-level formulas, summary formulas, complex charting, dashboard filters, dynamic dashboards, and embedded report charts.

Choose the simplest reporting feature that meets the requirement. A joined report is useful when multiple report blocks need to be compared, but it is unnecessary for a straightforward summary. A reporting snapshot stores summarized results over time when the organization needs historical trend analysis.

Always consider sharing. Report and dashboard results depend on the viewer, folder access, source-report access, and dashboard running-user configuration.

5. Cloud Applications — 11%

Cloud Applications covers advanced sales and service capabilities, including products, price books, schedules, orders, quotes, forecasting, territory management, Knowledge, entitlements, Omni-Channel, and customer-facing experiences.

Salesforce now uses Agentforce Sales and Agentforce Service names in current materials, while older pages may still say Sales Cloud and Service Cloud. The underlying administrator topics remain focused on configuring sustainable sales and service processes.

Sales application capabilities

Review products, price books, opportunity products, schedules, quotes, and orders. Understand how these records support the selling process and where an advanced administrator may need to control access, processes, or data quality.

Forecasting helps teams predict revenue based on opportunities and other supported data. Enterprise Territory Management assigns accounts and responsibilities according to a territory model instead of relying only on role hierarchy. Study model activation, assignment, access, and reporting implications.

Service application capabilities

Salesforce Knowledge supports articles, record types, data categories, visibility, and service-agent access. Entitlements and milestones help organizations define and measure support commitments. Case Feed, Service Console, Experience Cloud sites, messaging or chat capabilities, and Omni-Channel support interaction and work routing.

Omni-Channel distributes work according to routing configuration, capacity, presence, and supported work items. Entitlement processes track support steps and milestones. These tools solve different parts of service delivery and may be used together.

6. Auditing and Monitoring — 10%

Auditing and Monitoring tests whether you can investigate changes, system activity, security configuration, and sensitive-data concerns.

Setup Audit Trail and debug information

Setup Audit Trail records many administrative configuration changes. It helps answer who changed a setting and when. Debug logs provide detailed execution information for transactions and are useful when investigating automation, code, validation, or unexpected behavior.

Choose the tool based on the question. If the problem is a changed configuration, start with setup history. If the problem is the behavior of a transaction, review debug and flow information.

Event Monitoring and transaction security

Event Monitoring provides insight into user and application activity, such as logins, exports, API usage, or other supported events. Transaction Security policies can respond to selected events with actions such as blocking or notification where supported.

Monitoring does not replace preventive permissions. Use least privilege first, then monitoring and policies to detect or respond to risk.

Sensitive data across environments

Production data may contain personal, financial, health, or confidential information. Sandbox creation, refreshes, integrations, exports, and support processes must follow organizational security and compliance requirements. Mask or limit sensitive information where required, and avoid copying production data without an approved purpose.

Also review security health settings and pending platform updates that can change access behavior. Advanced administrators should test access-related changes before broad rollout.

7. Environment Management and Deployment — 7%

This domain has the smallest weighting, but it tests an essential administrator responsibility: moving changes safely between environments.

Sandbox strategy

Different sandbox types support different combinations of metadata, data, storage, and refresh frequency. Choose an environment based on development, testing, training, integration, or full-scale validation needs.

Keep production changes controlled. Build and test in a suitable environment, document dependencies, use representative test cases, and plan how to confirm success after deployment.

Moving metadata

Change sets move supported metadata between connected Salesforce orgs. Outbound change sets collect components, while inbound change sets are validated and deployed in the target. Dependencies, permissions, tests, and referenced components must be considered.

AppExchange packages can distribute metadata and applications. Managed and unmanaged packages have different ownership, upgrade, and modification characteristics. Even when another deployment method is used, students should understand the capabilities and limits of change sets because they appear in the official outline.

Deployment validation

Use validation where available to identify problems before the planned release. Document the deployment order, configuration steps, test results, assigned permissions, and rollback approach. After deployment, confirm both technical behavior and user access.

Your Advanced-Admin Preparation Toolkit

Advanced certification study should help you organize complex knowledge and improve judgment. Our preparation approach follows the current seven-domain outline and turns mistakes into focused next steps.

Students can benefit from:

• Current domain alignment: Study follows Salesforce’s latest Platform Administrator II weights.
• Clear advanced explanations: Complex features are described through practical administrator decisions.
• Scenario-based reasoning: Practice emphasizes requirements, constraints, dependencies, and long-term maintenance.
• Targeted weak-area review: Security, automation, objects, analytics, or deployment gaps can be reviewed separately.
• Troubleshooting practice: You learn to trace behavior through access layers, data relationships, and automation order.
• Hands-on direction: Checklists connect reading with tasks in a Trailhead Playground or another authorized environment.
• Broader study navigation: Candidates comparing related paths can Explore Salesforce certification preparation resources alongside other professional learning options.

Quality matters more than the total number of items. A useful practice resource should align with the official outline, provide understandable explanations, avoid pass guarantees, and help you identify why an alternative does not meet the complete requirement.

How to Use Practice Tests for Advanced Administrator Study

Begin with domain-level diagnosis

Complete short topic checks after reviewing each domain. Record uncertain responses as well as incorrect ones. A correct guess should not be treated as mastery.

Use an advanced error log

For each mistake, record:

1. Domain and feature.
2. Requirement you missed.
3. Security, data, or automation dependency.
4. Correct solution and expected result.
5. Hands-on task needed to confirm it.

Rebuild the scenario safely

Use an authorized learning environment. Create a small sharing model, relationship, report, flow, approval, or change set. Change one condition at a time so you can see why the result changes.

Explain the tradeoff

Advanced scenarios often contain several workable options. Explain why the chosen solution is more secure, maintainable, scalable, or suitable for the requirement.

Return to mixed review

Once individual domains feel stable, complete mixed sessions. This checks whether you can identify the type of problem before choosing a feature.

A Six-Week Platform Administrator II Study Plan

Week 1: Advanced security and access

Review the complete sharing model, session-based access, delegated administration, authentication, account teams, territories, and complex account relationships. Test access using multiple user personas.

Week 2: Objects and application experience

Build lookup, master-detail, self, and junction relationships. Configure Dynamic Forms, component visibility, app navigation, console features, and page assignments. Review performance and mobile experience.

Week 3: Sales, service, auditing, and monitoring

Review products, price books, forecasting, territories, Knowledge, entitlements, Omni-Channel, and Experience Cloud. Then practice selecting among Setup Audit Trail, debug logs, Event Monitoring, and Transaction Security.

Week 4: Data and advanced analytics

Plan an import using external IDs and relationships. Review duplicate control, validation, external objects, big objects, and archiving. Build custom report types, cross filters, joined reports, summary formulas, snapshots, and dynamic dashboards.

Week 5: Automation

Build record-triggered, screen, and autolaunched flows. Add fault handling and reusable subflows. Review approval routing, order of execution, legacy automation, and the boundary between declarative tools and Apex.

Week 6: Deployment and mixed practice

Create a small change set with dependencies and validate it. Review sandbox selection and package concepts. Complete mixed-domain practice, rebuild weak scenarios, and explain each solution without seeing the choices.

Common Mistakes to Avoid

Treating Platform Administrator II as a basic review

The credential expects deeper scenario analysis. Review advanced capabilities and their implications, not only feature definitions.

Changing record sharing when the problem is field access

Record visibility, object permission, and field access are separate layers. Identify the failing layer before changing the model.

Choosing master-detail only for roll-up summaries

Master-detail also affects ownership, required relationships, sharing, and deletion. Evaluate all consequences.

Building one oversized flow

Large flows can be difficult to test and maintain. Use clear responsibilities, subflows where appropriate, efficient queries, and fault handling.

Ignoring order of execution

Unexpected automation behavior often comes from sequence and reevaluation. Trace every automation responding to the transaction.

Using complex reports when a simple report works

Joined reports and reporting snapshots solve specific needs. Choose the simplest tool that meets the requirement.

Moving metadata without its dependencies

A component may reference fields, record types, permissions, flows, or other metadata. Validate the package and document deployment order.

Studying only old Advanced Administrator pages

Older resources can still help, but use the current Platform Administrator II guide and Trailmix to confirm names, objectives, and weighting.

Hands-On Readiness Checklist

You are building strong readiness when you can:

• Diagnose object, field, record, folder, and authentication access separately.
• Compare profiles, permission sets, session-based permissions, and delegated administration.
• Explain account teams, person accounts, contacts to multiple accounts, and territories.
• Choose lookup, master-detail, self, or junction relationships appropriately.
• Configure Lightning pages, Dynamic Forms, components, and activation assignments.
• Select the correct monitoring or audit tool for a problem.
• Protect sensitive information across production and sandbox environments.
• Configure advanced sales and service capabilities at an administrator level.
• Plan data quality, import, external access, backup, and archiving approaches.
• Build complex reports and useful dashboards without unnecessary complexity.
• Select a suitable sandbox and deployment method.
• Identify metadata dependencies before a release.
• Design maintainable flows with error handling.
• Explain approval behavior and order of execution.
• Identify when declarative tools are insufficient and specialist development is needed.
• Explain every practice answer through requirement, constraint, dependency, and outcome.

If several items remain uncertain, return to the matching official domain and build one controlled example. Advanced readiness grows through repeated diagnosis and configuration, not through answer memorization.

Continue Developing Advanced Administrator Judgment

Platform Administrator II preparation is about connecting features across the Salesforce Platform. Security controls who can act. Object design determines how information relates. Cloud applications support sales and service teams. Monitoring reveals changes and risk. Data and analytics turn records into trustworthy insight. Deployment moves improvements safely, while automation coordinates complex work.

Use each practice result to choose one specific improvement. Review the official objective, rebuild the behavior in an authorized environment, and explain why the selected solution fits better than the alternatives. Students exploring a broader certification route can Discover practice tests for leading IT certifications while planning their next learning goal.

Keep the current terminology in view. Salesforce now uses Platform Administrator II, while older material may say Advanced Administrator. Current Salesforce pages also increasingly use Agentforce Sales and Agentforce Service names where older content says Sales Cloud and Service Cloud. The official guide and Trailmix should remain your source of truth.

Salesforce Platform Administrator II Frequently Asked Questions

What is Salesforce Platform Administrator II?

It is Salesforce’s advanced administrator certification for professionals who can use advanced platform features and administration best practices to solve complex business problems.

Is Platform Administrator II the same as Advanced Administrator?

Platform Administrator II is the current credential name. Older resources and URLs may still use Salesforce Advanced Administrator.

Is Platform Administrator II active?

Yes. Salesforce lists it as an active administrator credential as of August 2026. Always verify current status on the official credential page.

Does Platform Administrator II have a prerequisite?

Yes. Salesforce Certified Platform Administrator is the prerequisite listed by Salesforce.

Is this suitable for a Salesforce beginner?

It is intended for seasoned administrators with significant practical experience. Beginners should first build the skills covered by Platform Administrator and gain hands-on experience.

Which domains have the greatest weight?

Security and Access and Process Automation each represent 20%. Objects and Applications represents 19%. Together, these three areas account for 59% of the outline.

Do I need coding knowledge?

The focus is advanced administration and declarative configuration. However, you should understand when declarative tools reach their limits and when Apex or another development approach may be appropriate. The official Trailmix includes Apex-trigger awareness as part of the wider preparation path.

Why is security difficult in Platform Administrator II?

Scenarios can combine authentication, object permission, field access, record sharing, territories, teams, and folder access. You must identify the exact layer causing the problem.

What advanced report features should I study?

Review custom report types, joined reports, cross filters, bucket fields, row-level and summary formulas, reporting snapshots, complex charts, dynamic dashboards, and dashboard filters.

What should I know about sandboxes and deployments?

Understand sandbox purposes, change sets, metadata dependencies, validation, data migration considerations, managed and unmanaged packages, and post-deployment checks.

Should I still study workflow rules?

Yes, at least for troubleshooting and migration awareness. Existing organizations may contain legacy automation, while Flow is the primary declarative automation tool for current solutions.

How should I practice order of execution?

Create a controlled record update with validation, before-save logic, after-save logic, and other automation. Use debug information to trace the sequence and identify when values change.

Are Trailhead resources enough?

They are the official foundation. Strong preparation also includes hands-on administration, the current exam guide, relevant Superbadges, scenario-based practice, and an error log.

Are practice tests enough by themselves?

No. Use them to diagnose weak areas and confirm reasoning. They work best with official learning and hands-on configuration.

How can I tell whether I am ready?

You should be able to solve unfamiliar scenarios, explain tradeoffs, trace security and automation behavior, and reproduce core configurations safely. Consistency across different mixed-domain sessions matters more than one score.