Cloud Kicks is working on a rebrand. In which two areas of the Salesforce mobile app can a Platform Administrator customize the branding?
To align the Salesforce mobile app with a company's visual identity, a Platform Administrator can customize specific branding elements through the Salesforce Mobile App Customization settings. The two primary areas available for branding are:
Loading Page Logo: This allows the administrator to upload a company logo that appears when a user first opens the app.
Header Background Color: This allows the administrator to set the primary brand color for the top header area of the mobile interface.
These settings ensure that the user experience feels consistent with the company's internal branding from the moment they log in. Option A and B are incorrect because Salesforce does not currently allow for granular 'App header' vs 'Header background' color separation or the modification of the 'Record background color,' as the app maintains a standardized background for accessibility and readability. Customizing the loading screen and header is the standard way to implement a mobile rebrand.
Ursa Major Solar (UMS) wants a place within Salesforce to discuss sensitive records. UMS would like to be able to add new members but does not want non-members to be able to see any information about the forum. What should a Platform Administrator configure to achieve this?
To facilitate the discussion of 'sensitive records' where even the existence of the group must be hidden from non-members, a Chatter Unlisted Group is the appropriate solution. Unlike a Private Group (Option B), which can be seen in searches and lists even if the content is hidden, an Unlisted Group does not appear in search results and requires an explicit invitation to join. This ensures that only members know the forum exists, meeting the highest privacy requirement. Public Groups (Option C) are visible to everyone and are not suitable for sensitive discussions42. 'Private Chatter Channel' (Option D) is not a standard term for this type of collaboration group. Unlisted groups must be enabled in Chatter Settings before they can be created by administrators.
The Cloud Kicks sales team has asked that two of the fields that appear on the Opportunity cards in Kanban view be changed to make the cards more meaningful. Which feature should a Platform Administrator access to make this change?
In the Salesforce Lightning Experience, the fields displayed in the 'header' of a record and on the cards in the Kanban view are controlled by the Compact Layout. Each object has a System Default compact layout, but a Platform Administrator can create custom ones to prioritize the most important information, such as 'Account Name' and 'Close Date.' By editing the primary compact layout for the Opportunity object, the admin directly controls which fields the sales team sees as they drag and drop deals through the Kanban stages. While Page Layouts (Option C) control the main record detail page and Kanban Settings (Option D) control which field is used for columns and summaries, the individual 'card' content is always driven by the Compact Layout. This ensures that users can quickly gather key context without needing to open every individual record.
Users at Cloud Kicks want to see information that is more useful for their role on the Case page. How should a Platform Administrator make the pages more dynamic and easier to use?
In the Lightning App Builder, Component Visibility Filters allow an administrator to show or hide parts of a record page based on specific criteria, such as the user's profile, a field value, or the record type. This is the best way to make pages 'dynamic.' For example, the administrator can configure a 'Financial Details' component to only appear when the user viewing the case has the 'Finance User' profile, or hide a 'Recall Instructions' component unless the 'Case Reason' is set to 'Product Defect.' This prevents 'information overload' by ensuring that users only see the tools and data relevant to their specific role or the current state of the record. Simply deleting components (Option D) or removing fields (Option C) would affect all users equally, failing to provide role-specific utility. Component visibility creates a personalized, streamlined experience that improves user productivity and reduces clutter on complex record pages.
A Platform Administrator at Ursa Major Solar imported records into an object by mistake. Which two tools should the administrator use to undo this import?
To 'undo' a mistaken import, the administrator must delete the incorrectly created records. Two standard tools facilitate this:
Mass Delete Records (Option D): This is a browser-based tool in Setup that allows administrators to delete up to 250 records at a time (standard) or use criteria to identify and remove larger sets of records. It is the quickest way for smaller mistakes.
Data Loader (Option B): For large-scale errors, the administrator can use the Success file generated during the original import (which contains the new record IDs) and perform a 'Delete' operation.
The Data Import Wizard (Option C) is for adding or updating data, but it does not have a 'Delete' function. Weekly Data Export (Option A) is a backup tool and cannot be used to remove existing data from the system.
Heather Allen
1 month agoFrank Moore
2 months agoRonald Robinson
2 months agoAmanda Turner
3 months agoEmily Turner
3 months agoSarah Allen
4 months agoRonald Roberts
4 months agoMargaret Smith
5 months agoNathan Moore
5 months agoEmily Collins
6 months agoSarah Lopez
6 months agoJennifer Brown
6 months agoAnthony Campbell
6 months agoStephanie Parker
6 months agoMaria Clark
5 months agoLisa Nelson
5 months agoNina
7 months agoBambi
7 months agoGerald
7 months agoBeth
7 months agoTu
8 months agoElke
8 months agoBrinda
8 months agoSilva
9 months agoLeota
9 months agoSharita
9 months agoArlean
9 months agoMarilynn
10 months agoGeorgiann
10 months agoTijuana
10 months agoQuentin
10 months ago