Salesforce Certified Platform Administrator (SF-Admin) — Questions 151–202

Standard Case Assignment Rules evaluate incoming case records against defined criteria, such as the customer's billing country, and automatically route matching records to the appropriate user or queue. This functionality is native, scalable, and designed specifically to handle automated queue assignments without requiring custom code or complex process automation flows.

Custom lead fields can be mapped to custom account, contact, or opportunity fields during the lead conversion process. By configuring Lead Field Mapping in the Object Manager, administrators ensure data continuity from the lead lifecycle stage into the core sales pipeline. This mapping is vital for accurate reporting, as it prevents data loss and maintains historical campaign tracking for customer relationship management.

Login IP Ranges are the standard configuration tool for restricting access to Salesforce based on network security requirements. By setting these ranges at the Profile level, administrators create a whitelist of trusted IP addresses. This is a critical security practice in Salesforce, ensuring that sensitive organizational data remains accessible only from approved physical or virtual office locations, thereby mitigating unauthorized access risks.

A public Chatter group supports self-service membership, file sharing, posts, and dashboards, which directly addresses the collaboration, calendar, battle card, and pipeline metrics requirements. Unlisted groups require manual membership, list views lack collaborative features, and Experience Cloud sites are for external users and require administrator-managed access.

A Picklist field is designed to let users select one value from a predefined set and is fully compatible with list view and report filters. The other field types either do not enforce a predefined list (Text), are not filterable (Text Area), or are read-only (Formula). Therefore, Picklist is the only correct choice to meet both the selection and filtering requirements.

Administrators must first verify the Page Layout configuration to ensure the related list is present. If it is missing from the layout, no other system-level permission will make it appear for the user. Checking the page layout is the foundational step in troubleshooting visibility issues, ensuring that the UI component is properly defined before investigating complex permission sets, profile settings, or potential field-level security constraints.

Case Escalation Rules automatically track age and trigger automated actions when milestones are missed. Administrators can configure these rules to reassign cases to different queues or users and send automated email alerts to management or support tiers. This ensures critical service level agreements are strictly maintained and visibility is preserved across organizational hierarchies.

Campaign Influence attributes opportunity revenue to the campaigns that touched the deal, and with Customizable Campaign Influence and Auto-Association enabled, the campaign is linked automatically when the originating lead converts. Marketing can then report on influenced pipeline and revenue per campaign without manual data entry, which matches the requirement precisely.

Salesforce platform architecture does not support formula fields as controlling fields for dependent picklists because formula values are calculated dynamically on the fly. Dependent picklists require static field types such as standard or custom picklists and checkboxes to accurately map dependent dependency matrix values. Recognizing this constraint prevents administrators from designing broken schema configurations.

Criteria-based sharing rules are the ideal tool for this requirement because they allow administrators to grant access to records based on field values rather than just record ownership. This ensures that users only collaborate on and view data that aligns with their assigned territory or geographic focus, maintaining data security and organizational compliance without requiring manual record sharing or complex custom development.

Field-level security (FLS) is the most common cause for missing fields. Even with object-level permissions, FLS overrides access at the field level. By checking the Field-Level Security settings in the Object Manager, an administrator can verify if the user's profile or permission set has 'Visible' access to the field, ensuring the UI and API respect the user's specific access rights.

To ensure the flow runs only when a Case is created and the Priority is 'High', the administrator must set the trigger to run on create only and configure entry criteria that check if Priority equals 'High'. Entry criteria are evaluated before the flow runs, making them the most efficient filter. A Decision element could also check Priority, but entry criteria are the standard configuration for this purpose.

A Topic represents a specific intent or category of customer inquiry that the agent is trained to understand and act upon. By grouping related phrases, instructions, and actions under a Topic, you organize the agent's capabilities logically. This allows the AI model to quickly identify the user's intent and select the appropriate process to follow, which is fundamental for providing relevant and structured support.

Validation Rules are the most appropriate declarative tool for enforcing data integrity based on field-level conditions. By checking if the current stage is 'Closed Won' and comparing the record's prior value to its current value, an administrator can prevent changes to historical data. This approach is superior to page layouts or permission sets, as it enforces the business logic at the database level regardless of the user's interface.

Managing a high-quality knowledge base requires control over who sees which articles and an approval process for publication. Data Categories provide the structural hierarchy for visibility and filtering, while Workflow/Approvals ensure that articles are reviewed for accuracy before being exposed to customers. Together, these tools maintain the integrity of the knowledge base and ensure that sensitive or draft content remains hidden.

The correct configuration limits the flow to update events and uses the ISCHANGED operator on the Stage field along with an equality check for Closed Won. This ensures the flow runs only when an update causes Stage to transition to Closed Won, avoiding unnecessary executions on creation or on updates where Stage was already Closed Won. It precisely satisfies the stated automation requirement.

Global Search is the most powerful tool for quickly retrieving information across the entire Salesforce organization. By indexing all records, it allows users to locate specific items, accounts, or contacts without needing to navigate through individual apps or tabs. This drastically reduces the time spent searching, significantly boosting daily productivity by providing a single, reliable entry point for accessing the data required for ongoing projects and customer interactions.

Escalating a live agent conversation to a person requires a routing mechanism that carries session context, which is provided by Omni-Channel treating the agent session as a routable work item. Case rules, audit logging, and prompt wording all operate on records or model behavior rather than on the active messaging session, so none of them can deliver the transcript to a human without the customer repeating information.

Data Export Service provides a scheduled weekly or monthly backup service that automatically compiles all org data into downloadable CSV files and attachments. This native administrative feature ensures compliance with data retention policies without requiring complex third-party managed packages or custom script development.

Lightning App Builder provides a visual interface for assembling pages using standard and custom components. Understanding the capabilities, such as defining filter-based component visibility and assigning page-level activations, is critical for administrators to create dynamic user experiences. These tools allow for personalized interfaces without requiring custom code, significantly reducing maintenance overhead while improving user efficiency for different roles or business processes.

Formula fields are the standard way to perform calculations across fields within a record. They are read-only and update dynamically whenever the underlying data changes. This is a foundational skill for administrators, as it allows for the creation of derived data points without writing code, enabling business logic to be embedded directly into the schema for reporting and display purposes.

Salesforce's duplicate management feature, consisting of matching rules and duplicate rules, is designed to prevent duplicates during data import. Matching rules identify potential duplicates based on criteria like name or email, and duplicate rules determine the action. When enabled for Leads, imports through any tool will respect these rules, ensuring duplicates are blocked or flagged.

The 'Fields & Relationships' section in the Object Manager is the centralized location for managing all metadata related to an object's fields. Renaming a field label is a common administrative task that is performed here. This is important for keeping the user interface intuitive and ensuring that terminology remains consistent across the organization as business requirements evolve over time, thereby improving overall user adoption and system clarity.

A Formula field is the ideal choice for this scenario because it performs real-time calculations based on existing record data without requiring manual input. By utilizing the TODAY() function, the field dynamically calculates the duration. This ensures the information remains accurate and relevant for sales teams tracking client engagement, which is vital for maintaining high-quality customer relationships and prioritizing follow-up activities effectively.

Roll-up summary fields are designed to aggregate child records on a parent record and display the result directly on the parent's page layout. Summing Opportunity Amount through a roll-up on Account gives the analyst a live total without running a report, which matches the requirement precisely.

Agentforce leverages Large Language Models that maintain a 'conversation window' or 'state' by passing the history of the current session back to the model with every request. This allows the AI to remember what was previously said and provide relevant, consistent follow-up answers. Managing this state effectively is crucial for a natural, human-like interaction, allowing the agent to resolve complex queries that require multiple exchanges of information.

Cross filters are specifically designed to filter parent records based on conditions on related child records. By creating a report on Accounts and applying a cross filter for Projects with Status 'Active', the report returns only Accounts that have at least one related Project meeting that condition. This is the standard Salesforce feature for this use case.

Set Component Visibility in Lightning App Builder allows administrators to apply filters that evaluate record fields, user attributes, or device type. By setting a filter on the Priority field to equal High, the component will only appear for cases that meet that criterion. This is the correct declarative approach to conditionally display a component based on record data.

A Roll-up Summary field is the native Salesforce feature used to aggregate data from child records to a parent record. By creating a roll-up summary on the Account object that filters for 'Closed Won' opportunities, the administrator can maintain an accurate, real-time total of business value. This simplifies reporting and provides sales managers with immediate visibility into account health without needing complex custom code or manual calculations.

A validation rule is the most efficient and standard way to enforce data integrity when a record is being saved. By writing a formula that checks if the stage is 'Closed Won' and if the close date is greater than today, the system provides immediate feedback to the user, preventing incorrect data entry before the record is ever committed to the database, ensuring clean reporting and accurate forecasting.

Generating a summary and persisting it requires two capabilities: model-based text generation and a deterministic record update. A Prompt Template produces the summary, and an Agent Action can consume that output and write it to the case field. Calculated insights, Einstein Activity Capture, and static instructions cannot generate a dynamic summary and store it on the record.

Dashboards in Salesforce often run based on a stored 'Running User' context, which may have different data access levels than the individual user viewing the dashboard. If the 'Running User' has wider visibility, the dashboard might show data the viewer should not see, or if restricted, might show less. This discrepancy highlights the importance of understanding the 'Running User' vs. 'Viewer' security context for dashboards.

Component Visibility filters are a powerful feature in the Lightning App Builder that allow administrators to dynamically show or hide components based on record field values. This increases user productivity by decluttering the interface and presenting only relevant information based on the state of the record, such as showing a specific alert only when an Opportunity stage is 'Closed Lost'.

Field-Level Security (FLS) is the most common reason for a field to be hidden despite being on the layout. If the user's profile or assigned permission set has the visibility attribute unchecked for that field, the field will remain hidden. Troubleshooting this is a core competency for administrators, as it requires checking security settings rather than just UI configuration, ensuring data visibility complies with company privacy policies.

The error stems from the intersection of folder permissions and report type availability. If a user has object access but lacks access to the folder where the report is saved, they cannot run it. Additionally, if the report type requires access to related records or specific cross-filters that the user lacks permission for, the report remains inaccessible, necessitating a review of both sharing rules and folder-level permissions.

Field-level security is the primary mechanism to control access at the field layer. By creating a custom permission set or updating existing profiles, an administrator can hide specific fields from the sales user profile without needing to create complex sharing rules or record types. This ensures data security, maintains compliance with internal governance, and keeps the user interface clean for non-financial staff while preserving visibility for those who require it for decision-making.

When new users report missing welcome emails, administrators must verify system delivery logs and company-wide email configurations. Ensuring that deliverability settings are not restricted to test mode prevents legitimate outbound verification links from being suppressed by the Salesforce platform infrastructure.

The Formula field data type is required to perform mathematical calculations based on other fields within the same object. By using a formula, the system dynamically updates the commission value whenever the underlying amount changes. This ensures data integrity and reduces the need for manual calculations or automation triggers, streamlining the sales process and improving the accuracy of financial reporting across the organization.

Field-level security is the correct tool to control field editability per profile. Setting the field to 'Read-Only' for all profiles except Sales Manager allows viewing but prevents editing for others, while Sales Manager can edit. This meets the requirement without affecting data visibility.

Fiscal year settings are managed within the Company Information section of Salesforce Setup. Changing the fiscal year impacts reporting, forecasting, and historical data analysis. This is a global setting that affects the entire organization, so administrators must ensure that the change aligns with the financial planning and accounting cycles before modifying the default calendar-based fiscal year configuration.

To meet these requirements, the administrator must configure Organization-Wide Defaults to Private for the Case object and then implement Role Hierarchy or Sharing Rules. Role Hierarchy is the most efficient method here, as it automatically grants managers visibility into subordinates' records based on their organizational structure, ensuring that team-specific visibility is maintained while allowing management oversight of regional case data.

Field Level Security (FLS) is the correct control to restrict access to a specific field. By setting the field as 'Read-Only' or 'Hidden' for profiles other than the Sales Manager, the administrator ensures that sensitive discount information remains protected. This is critical for maintaining margin integrity and ensuring that only authorized personnel can view or apply discounts to customer deals.

Path is the feature that allows administrators to visualize the stages of a business process and provide guidance for each stage. By defining the key fields and guidance for success at every step of the case resolution, the administrator helps ensure that all agents follow a consistent, high-quality process, reducing variation and improving the reliability of the support outcomes across the entire team.

Record Types allow for different business processes and field layouts on the same object. By using them, administrators can maintain a single Account object while tailoring the UI and required fields for specific regions. This is a foundational concept in Salesforce that balances standardization with local flexibility, preventing the need for multiple redundant objects.

Expected Revenue is the standard field that automatically calculates the forecasted amount by multiplying Amount by Probability. To allow the sales team to see this value, the administrator must ensure it is included on the Opportunity page layout. This field is essential for accurate forecasting and is distinct from Amount or Probability alone.

A summary report grouped by Opportunity Owner with the appropriate filters provides a clear, grouped total of closed won amounts per sales representative. It automatically calculates subtotals, making it easy for the manager to identify top performers. This is the standard and most efficient solution for this type of analysis.

Salesforce Files centralize document management, allowing users to share, collaborate, and version control files directly within the platform. Unlike static attachments, Files provide real-time updates and version history, ensuring that all team members access the most recent information. This increases productivity by eliminating the need to search through external email threads or local drives, creating a single source of truth for project-related documentation accessible from any mobile or desktop device.

When creating a custom object in Salesforce, the platform mandates two specific components to ensure the object is identifiable and trackable within the system. The 'Label' provides the user-facing name, while the 'Plural Label' handles list views and tabs. Without these two identifiers, the metadata for the object cannot be generated, preventing the object from being accessible within the Lightning platform and the App Builder.

The 'Home' page is the centralized hub for Salesforce users. By default, it features the 'Today's Tasks' component, which provides an immediate, aggregated view of all tasks assigned to the user that are due soon or are currently overdue. This is the most efficient location for a user to manage their daily workload without having to navigate to individual record pages or complex report lists.