Lesson 6 of 23 · All lessons
Salesforce Platform Administrator II
0 of 23 complete
1Exam Overview
  1. 1.1Platform Administrator II Complete Exam Overview
2Security and Access20%
  1. 2.1Sharing architecture: records, fields, and inherited access
  2. 2.2Profiles, permission sets, delegated administration, and
  3. 2.3Person accounts and complex account-contact models
3Objects and Applications19%
  1. 3.1Object relationships, record types, and schema design
  2. 3.2Applications, Lightning App Builder, Dynamic Forms, and
  3. 3.3Record types, page layouts, and related-list experience
4Auditing and Monitoring10%
  1. 4.1Debug logs and Setup Audit Trail
  2. 4.2Sensitive data, sandbox controls, and security review
  3. 4.3Reviewing security changes and pending access updates
5Cloud Applications11%
  1. 5.1Sales lifecycle: products, price books, schedules, orders, and
  2. 5.2Forecasting and Enterprise Territory Management
  3. 5.3Knowledge, entitlements, and service channels
  4. 5.4Salesforce product suite and platform extension choices
6Data and Analytics Management13%
  1. 6.1Data quality, validation, duplicates, enrichment, and archiving
  2. 6.2Complex reports, dashboards, and analytic design
  3. 6.3External data, backup and restore, and import methods
7Environment Management and Deployment
  1. 7.1Sandboxes, packages, and metadata movement options
  2. 7.2Change set composition, validation, and deployment practice
  3. 7.3Sandbox selection, refresh, and data protection
8Process Automation20%
  1. 8.1Choosing Flow, approvals, formulas, and legacy automation
  2. 8.2Order of execution, recursion, and automation interaction
  3. 8.3Automation troubleshooting, testing, and fault handling

Section 3 · Objects and Applications · 19% of exam

3.2 Applications, Lightning App Builder, Dynamic Forms, and

4 min read Updated Nov 17, 2026

Exam objective

Given a scenario, determine the appropriate solution to extend UI/UX with App Manager, Lightning App Builder, Dynamic Forms, standard components, Console, and Lightning page analysis.

A Lightning app packages navigation and utility options for a role or workflow. App Manager is used to create and manage Lightning apps, assign branding, choose navigation items, and configure supported utility features. An app helps users reach the right work areas; it does not grant object, field, or record permissions. If a user can open an app but cannot see a record, inspect data access. If a user has access to records but cannot find the work area, inspect app visibility and navigation configuration.

Lightning App Builder composes supported pages from components and assigns them to applicable apps, record types, or profiles depending on page type and activation. A home page can present role-specific information; a record page can bring related components and actions into context. Assignment and activation determine who receives a page. Build a page around the user's task and avoid loading it with redundant components. Component visibility filters control when a component appears, but they do not secure the underlying data. All sensitive information still requires object, field, and record access controls.

Dynamic Forms can place fields and sections directly on supported Lightning record pages and apply visibility rules at a more granular level than a traditional page layout. This can simplify layouts for users who need different fields based on record attributes or permissions. Page layouts remain important for other interfaces and functions, and not every object or feature has identical support. Use field-level security for data protection; use Dynamic Forms for presentation. If a field is hidden by a visibility rule, the user might still access it elsewhere if security permits.

Standard Lightning components provide common functionality such as record details, related lists, highlights, activity, and path guidance. They are often preferable to custom development because Salesforce maintains their behavior and compatibility. Choose components based on user tasks and understand each component's data and configuration dependencies. A related list component can only show relationships that exist and that the user can access. A component's visibility, record page assignment, app navigation, and underlying security all interact but solve distinct problems.

A Console app supports high-volume service or sales workflows with workspace tabs, subtabs, split views, and productivity tools. It helps users move between related records while retaining context. Console configuration is appropriate when agents handle many cases or records in sequence; it may be unnecessary for occasional users who need a simple navigation bar. Verify utility items, navigation, record opening behavior, and supported components for the intended user. Console usability should be tested with realistic workloads, not only a short demonstration. The Lightning page analyzer helps identify page performance concerns such as component load impact and page complexity. Treat its findings as diagnostic clues: determine which components are expensive, redundant, or unnecessary for a given audience, then simplify and retest. Page performance can also depend on data volume, network, formulas, integrations, and browser behavior. Avoid assuming that reducing visible components fixes an underlying query or data issue. Establish a baseline and compare the same representative page under similar conditions after changes. Scenario method: identify whether the requirement concerns navigation, record-page composition, field presentation, console workflow, or performance. Select the corresponding tool, then verify activation, audience, and access. Test as a representative profile and device. Confirm the user can navigate to the page, the required records and fields remain authorized, and page behavior meets task needs. When the requirement applies to one group only, use supported page assignment or visibility conditions rather than cloning an entire app unnecessarily.

Exam focus: separate App Manager's app navigation from Lightning App Builder's page composition. Use Dynamic Forms to tailor field presentation where supported, not to secure sensitive data. Recognize Console for multi-record productivity. Use the page analyzer when investigating page performance. Look for the least complex native feature that serves the workflow, and test activation and security independently.

Availability of Dynamic Forms and analyzer features is object- and release-dependent. Confirm support in the current Salesforce Help documentation before basing a design on them.

Practical scenario:

Support agents process several cases per call and need a compact record workspace with related knowledge and recent activity. Configure a Service Console app with only relevant navigation and utility items, then tailor the case record page with supported standard components. Use component visibility to reduce clutter by case type, but rely on record, object, and field permissions to protect customer data. Review analyzer findings and remove components that do not support the workflow.

Extra concept:

Page assignments can be affected by app, record type, profile, and org defaults. If a user reports that a page change did not appear, verify activation assignments and the app in use before rebuilding the page. Page visibility and page activation are separate from permission assignment.

Key takeaways

  • App Manager configures navigation; Lightning App Builder composes pages.
  • Dynamic Forms and component visibility tailor presentation but do not secure fields.
  • Use Console for high-volume multi-record work and test the actual user workflow.
  • Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.lightning_app_builder_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.dynamic_forms.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.console_app_overview.htm&type=5

Check your knowledge

Answer exam-style Objects and Applications questions with answers and explanations.

Practice Objects and Applications
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Administrator II simulator: same number of questions, same time limit.

Get Complete Access