Section 5 · User Interface · 17% of exam
5.1 Customize Salesforce Pages and Navigation
Exam objective
Describe user-interface customization options and how they shape the application experience. Salesforce user-interface customization is layered. Apps organize navigation and branding; Lightning App Builder places components on record, app, and home pages; page layouts control many record-detail fields, related lists, buttons, and actions; compact layouts determine highlights; record types and business processes can tailor picklist values and processes; dynamic forms and actions can expose fields and actions based on conditions where supported. The exam expects candidates to choose the right layer for a requirement rather than treating all UI controls as interchangeable. Start with user tasks. Identify which records users work on, what information they need first, and which actions should be prominent. Use app navigation to make frequent work accessible. Use Lightning pages for component composition and page-level audience or activation choices. Use page layouts to organize record details and related lists and to control the placement of actions in contexts where the layout applies. Use record types when users need distinct processes, picklist values, or layouts for the same object, not merely to create a different visual appearance. Dynamic forms and conditional visibility can simplify a record page by showing relevant fields and sections in context. They do not replace field-level security. Page activation and assignments can differ by app, profile, or record type depending on the page type. When users report seeing different pages, inspect activation assignments, app context, record type, profile, and mobile form factor. Validate changes for all audiences and not just the builder’s own app. A strong UI supports accessibility, consistency, and data quality. Use clear labels, logical grouping, concise help text, and actions that match the user’s workflow. Avoid loading a page with every possible field or component. Think about screen size, network conditions, and users who rely on keyboard or assistive technology. UI changes should be tested alongside security settings because visibility and access are related but not equivalent.
Applied scenario: A support team handles both warranty cases and installation requests on the same Case object. If the processes require different picklist values and layout emphasis, use record types with appropriate business processes and page layouts. Use a Lightning record page to place a contextual knowledge component and a prominent escalation action. Add conditional visibility so installation-only fields appear for installation cases, while field-level security still controls whether a user is permitted to see sensitive values. Test the cases in the correct app, with the intended profiles and on desktop and mobile.
Design and risk review: Do not use a page layout to secure data or create a record type for every small presentation difference. Too many app-specific pages create maintenance overhead and can confuse users. A component hidden by a visibility filter may still expose information through another route if permissions allow it. Page assignments can be the cause when a user says a change is missing. Verify activation and audience context before rebuilding the page. Salesforce Certified Platform App Builder | SU ·26 guide alignment 20 Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.
Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.
Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result.
Key takeaways
- Describe user-interface customization options and how they shape the application experience
- Choose the platform feature that fits the requirement, data, access, and operating context.
- Test realistic users, exceptions, dependencies, and lifecycle effects before release.
- Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://trailhead.salesforce.com/content/learn/modules/lightning_app_builder
