CSA User Interface Development 3 — Questions and Answers
Question 1: A user reports that a field they need is missing from the Opportunity record page but it exists on the page layout. What is a likely cause in a Lightning Experience environment?
- The field-level security removes the field for that profile (Correct answer)
- The field is hidden by a visibility rule on the Lightning record page
- The field is not in the compact layout
- The field requires a custom Lightning component to display
Correct answer: The field-level security removes the field for that profile
Field-level security (FLS) controls whether a user can see a field regardless of page layout or Lightning record page configuration; FLS takes precedence.
Question 2: An administrator wants to let users edit multiple fields on a record without clicking Edit. Which Lightning Experience feature enables this?
- Quick actions
- Inline editing (Correct answer)
- Dynamic forms
- Mass update
Correct answer: Inline editing
Inline editing in Lightning Experience allows users to click on a field value directly on the record detail to edit it without entering full edit mode.
Question 3: A company wants to display a customized set of fields in the record highlights panel at the top of a Lightning record page. Which feature controls those fields?
- Page layout — top section
- Compact layout (Correct answer)
- Lightning record page header component
- Mini page layout
Correct answer: Compact layout
The compact layout defines which fields appear in the highlights panel (record header) and in other compact displays like hover cards and Kanban views.
Question 4: An administrator notices that a custom button configured for a 'URL' behavior type opens an internal Salesforce page in a new browser tab instead of navigating within the app. What is the recommended fix?
- Change the button behavior to 'Display in existing window without sidebar'
- Replace the custom button with a Lightning quick action (Correct answer)
- Use a formula to generate a relative URL
- Enable the 'Open in same tab' setting in Setup
Correct answer: Replace the custom button with a Lightning quick action
Classic-style URL custom buttons often open new tabs; replacing them with Lightning quick actions provides a native, in-app experience.
Question 5: Which statement best describes the difference between an 'object-specific action' and a 'global action' in Salesforce?
- Object-specific actions create records pre-populated with related data; global actions create blank records from anywhere (Correct answer)
- Global actions are faster than object-specific actions
- Object-specific actions appear in the global header; global actions appear on record pages
- Global actions require a custom page layout; object-specific actions do not
Correct answer: Object-specific actions create records pre-populated with related data; global actions create blank records from anywhere
Object-specific actions leverage the current record's context to pre-populate fields, while global actions are context-free and available from anywhere in the app.
Question 6: An administrator wants to add a utility item so support agents can quickly access the History tab while working in any record. Where should this be configured?
- App navigation items in App Manager
- Utility bar in the Lightning App settings (Correct answer)
- Global actions menu
- The org-wide default homepage
Correct answer: Utility bar in the Lightning App settings
The utility bar in Lightning App settings provides a persistent toolbar at the bottom of the screen where admins can add utility items like History for quick access.
Question 7: A manager wants to see a visual summary of pipeline stages for Opportunities directly on an Account record page. Which standard Lightning component is best suited for this?
- Activities Timeline
- Report Chart (Correct answer)
- Path component
- Kanban view embed
Correct answer: Report Chart
The Report Chart component on a Lightning record page can display a chart from a report filtered by the current record's related data.
A user reports that a field they need is missing from the Opportunity record page but it exists on the page layout.
What is a likely cause in a Lightning Experience environment?