ADM-201 Salesforce Certified Platform Administrator (Plat-Admn-201) Questions and Answers

To " predict upcoming revenue " and " benchmark performance, " Salesforce provides the Collaborative Forecasting feature.

Forecasting (Option B): This tool allows managers to see their pipeline summarized by time period (quarters) and category. It provides a real-time view of what the team expects to close.

Opportunity Stages (Option D): Forecasting relies directly on the Opportunity Stage. Each stage is mapped to a " Forecast Category " (e.g., Pipeline, Best Case, Commit, Closed). By accurately defining these stages and their associated probabilities, the Platform Administrator ensures that the forecast reflects a realistic revenue prediction.

Sales Quotes (Option A) are for generating customer-facing documents. List Views (Option C) are for managing individual records but do not provide the multi-quarter aggregation and benchmarking capabilities required by the sales director.

Deal Change Highlights is a feature in Lightning Experience that helps sales teams quickly identify recent changes to opportunities. In list views and the Kanban view, changes to the " Amount " or " Close Date " fields are highlighted with green (for positive changes) or red (for negative changes) arrows and text for seven days. This allows reps and managers to visually prioritize deals that have recently shifted in value or timing without having to open each record. Big Deal Alerts (Option A) send emails for high-value deals. Report Filters (Option B) are for general data analysis. The Opportunity Path (Option D) helps guide users through stages but does not highlight recent field-level data changes in a list format.

The most efficient and standard way to automate case creation from inbound emails is by using Email-to-Case . When setting up Email-to-Case, the Platform Administrator configures " Routing Addresses " . For each routing address (e.g., support@company.com or billing@company.com), the administrator can specify a default owner or queue for the cases created via that specific address . This ensures that when a customer sends an email to the " Support " address, it is automatically routed to the Support Queue, and an email to the " Billing " address is routed to the Billing Queue . This configuration is handled directly within the Email-to-Case setup pages and does not require additional escalation rules (Option A) or complex custom flows (Option C) for the initial assignment . While a custom email service (Option B) is possible, it is a developer-centric approach that is generally unnecessary given the robust native capabilities of the standard Email-to-Case feature . This setup streamlines the intake process and ensures that customer issues are immediately visible to the correct service team34.

The Lightning App Builder is the primary tool for creating custom user interfaces in both the desktop and mobile versions of Salesforce. For mobile customization, administrators primarily focus on two page types:

App Page: These are custom " landing pages " or " home pages " for an app. They can contain a mix of components like lists, charts, and flows, and they appear as items in the mobile navigation menu.

Record Page: These allow administrators to customize the layout of a specific object (like an Account or a custom Property record) for mobile users. Admins can use " Component Visibility Rules " to show or hide specific sections when the record is viewed on a mobile device, ensuring a streamlined experience on smaller screens.

There is no such thing as a " User Page " (Option B) in the App Builder. While dashboards can be viewed on mobile, they are created in the Dashboard Builder, not the Lightning App Builder (Option D).

Flow Builder is the standard and most versatile tool for performing automated data maintenance, including the deletion of records. A " Schedule-Triggered Flow " can be configured to run at specific intervals (e.g., daily at midnight) to find records that meet certain criteria—such as Leads that have been " Unqualified " for over a year—and use the " Delete Records " element to remove them from the system. While the " Mass Delete Records " tool (Option C) exists in the Setup menu, it is a manual administrative tool and cannot be scheduled or fully automated based on complex field-level logic. Automation Studio (Option B) is a Marketing Cloud tool, not a core Salesforce platform feature for record management. Flow Orchestration (Option D) is used for complex, multi-user business processes rather than simple data cleanup tasks. Therefore, for recurring, criteria-based record deletion, Flow Builder is the recommended solution.

Creating effective Agentforce prompts requires a focus on clarity and simplicity to ensure the Large Language Model (LLM) follows instructions accurately. According to Salesforce best practices, administrators should use natural, easy-to-understand language and provide clear, concise instructions1919. This approach helps the AI accurately reason through the task without becoming confused by overly complex or nested logic (Option A). While technical accuracy is important, relying heavily on jargon or abbreviations (Option B) can sometimes lead to unexpected results if the LLM interprets those terms differently in various contextsFurthermore, providing high-level theoretical concepts (Option C) often results in vague or " creative " answers that may not be helpful for technical troubleshooting, which requires specific and actionable steps22. Using direct instructions like " Summarize the issue in three bullet points " is more effective than broad guidelines.

When naming actions for an AI agent, consistency is key to helping the Large Language Model (LLM) categorize and understand the available tools. Following a consistent naming convention, such as starting all retrieval actions with the verb " Get, " allows the agent to more easily map user intent (e.g., " I need information about... " ) to the appropriate action. This reduces ambiguity during the reasoning phase of the agentic loop. Using inconsistent verbs like Find, Retrieve, or Identify (Option D) can confuse the model regarding which action is most appropriate for a given task. Removing verbs entirely (Option A) makes it harder for the model to distinguish between an action (doing something) and a data object (a thing). Adding " Salesforce " (Option B) is generally redundant as the agent ' s context is already within the Salesforce environment.

When a user needs to be temporarily prevented from logging in—but their records, role, and historical data need to remain intact—the best practice is to Freeze the user. Freezing an account stops the user from accessing the system immediately without " Deactivating " them. Deactivation can be problematic if the user is a " running user " for dashboards or is part of active hierarchy logic that might break if the account is disabled. Freezing is a simple " one-click " action on the user record. Reassigning the license (Option A) would require deactivating the user first. Changing login hours (Option B) or IP addresses (Option D) at the profile level would impact all users assigned to that profile, not just the individual manager on leave. Freezing provides a targeted and temporary solution for managing individual user access.

In this scenario, the two teams are " peers " in the role hierarchy (both reporting to the same manager). In a private sharing model, peers cannot see each other ' s records by default. To grant lateral access between these specific groups, an Owner-based Sharing Rule is the most effective solution. The administrator can create a rule stating that any records owned by members of " Role: Sales Team A " should be shared with members of " Role: Sales Team B " with specific access levels (e.g., Read/Write). Hierarchical sharing (Option C) only grants upward visibility to the Manager role, not across to the other team34. Manual sharing (Option D) is inefficient for an entire team35. Criteria-based sharing (Option A) is used when record field values determine access, whereas this requirement is based specifically on who owns the records36.

The Mass Transfer Records tool is a built-in Salesforce feature designed specifically for the scenario of a person leaving the company or changing roles. It allows a Platform Administrator to select a " From " user and a " To " user and then choose specific record types to transfer, such as Accounts and Opportunities. A major advantage of this tool is that it gives the administrator the option to transfer related records (like open opportunities or cases) and keep existing teams (like Account Teams) intact during the move. While Data Loader (Option A) or Dataloader.io (Option B) could technically perform a bulk update of the " OwnerId " field, they require several steps, including exporting data, manipulating CSV files, and re-uploading. The Data Import Wizard (Option D) is primarily for creating or updating records from an external file and does not have a dedicated " transfer " function. Mass Transfer is the fastest and safest standard way to reassign ownership within the Setup menu.

To allow users to post snapshots of dashboard components and engage in discussions about data directly on the dashboard, the Platform Administrator must enable Feed Tracking for dashboards. In Salesforce, Chatter Feed Tracking allows changes to records and interactions to be tracked and shared in the Chatter feed. For dashboards specifically, enabling this feature allows users to " Follow " a dashboard and use the " Post to Feed " functionality on individual dashboard components. This is highly effective for management teams who want to call out specific successes or areas of concern by tagging team members in a post that includes the visual chart. Reporting snapshots (Option A) are used for historical trend reporting, not social sharing. Downloading charts (Option B) is a manual file-handling process rather than an integrated social feature. Setting the " View Dashboard As " (Option C) determines data visibility but does not control Chatter functionality.

The " Minimum Access - Salesforce " profile is a very restrictive standard profile designed to provide no access by default, adhering to the principle of least privilege. One of the specific permissions that is not included in this profile is the Lightning Experience User permission. Without this system permission, users will be defaulted to the Salesforce Classic interface (or potentially blocked from any UI if no other access is granted). To resolve this, the Platform Administrator should either edit the custom profile or, preferably, create a Permission Set that includes the " Lightning Experience User " checkbox and assign it to the affected users. This " unlocks " the modern Lightning interface for them. Options B and C relate to the design of specific pages, but they are irrelevant if the user isn ' t even allowed to enter the Lightning environment. Option A refers to a different feature set entirely and does not address basic UI access.

In Salesforce, certain dependencies prevent a user record from being deactivated. One of the most common blockers is if the user is the Running User of a Dashboard. Because the dashboard relies on that user ' s security context to display data to others, deactivating them would break the dashboard. To resolve this, the administrator must first change the running user of the dashboard to someone else. Being part of an Opportunity Team (Option C) or Account Team (Option D) does not prevent deactivation; the user simply remains on the team but is inactive. For Assignment Rules (Option B), while you cannot delete a user in a rule, deactivation is usually permitted, though it may result in an error when the rule attempts to assign a record to the inactive user. However, the " Running User " requirement is a hard system block.

An Approval Process consists of several stages, each with its own set of automated actions. When a record is first submitted, it is typically locked to prevent further edits. If a user needs to " reverse " that submission—perhaps because they realized they made a mistake or the deal terms changed—the administrator must configure Recall Actions12. A recall action is specifically designed to allow the submitter or an administrator to pull the record back out of the approval queue. Common recall actions include a Field Update to change the status back to " Draft " and, most importantly, an action to unlock the record so it can be edited again. Final Rejection Actions (Option A) occur when an approver denies the request, and Final Approval Actions (Option C) occur when the request is fully granted. Initial Submission Actions (Option D) are what lock the record and start the process in the first place.

The Setup Audit Trail is the primary tool for tracking administrative and configuration changes within a Salesforce organization. It records a history of modifications made by any administrator, including the date and time of the change, which user made it, and exactly what was altered (e.g., creating a new field, changing a profile permission, or modifying a workflow rule). The history is available for the last six months of activity. Health Check (Option A) is a security tool that compares your settings against Salesforce standards. History Tracking (Option C) and Feed Tracking (Option D) are used to track changes to records (like an Account ' s phone number), whereas the Setup Audit Trail is dedicated to tracking metadata and system configuration.

The Activity Timeline is a standard Lightning component that displays open tasks, upcoming events, and past activities (like logged calls or sent emails) in a chronological view. If this timeline is missing from an Account page, it is usually because the component has been removed from the Lightning Record Page layout. To fix this, the Platform Administrator should open the Account record in the Lightning App Builder. From the list of standard components on the left, the admin must drag the Activities component onto the page canvas—typically in the right-hand column or a dedicated tab. Once the page is saved and activated, the timeline will be visible to users. Visibility of the timeline is a layout configuration, not a specific " Edit access " permission (Option B). Running a report (Option C) might confirm if data exists, but it won ' t fix the UI issue. There is no " button " for the Activity Timeline in the Object Manager (Option D); it is managed strictly as a component within the App Builder.

When defining Topics for an Agentforce agent, the quality of instructions is vital for ensuring the agent identifies the correct topic when a user asks a question. Best practice includes providing a variety of example user questions (utterances). This helps the agent ' s natural language processing (NLP) model recognize the different patterns and ways a human might phrase a request related to that specific topic. Writing instructions too generically (Option A) can lead to " topic overlap, " where the agent gets confused about which topic to use75. Minimal instructions (Option C) may reduce latency slightly but often result in poor accuracy and failed topic identification76. Using " plain language " is generally preferred over overly " business-specific " jargon (Option D) because the agent needs to match the way customers or employees naturally speak during a conversation

I apologize for that mistake. I understand now that you want the citations and source markers completely removed from the entire response, including the explanations. I will ensure they are not included moving forward.

In Salesforce Lightning Dashboards, Text Widgets allow administrators to add descriptive text, titles, and custom narratives directly alongside data visualizations. This is a key feature for " telling a compelling data story " because it allows the admin to provide context, explain the significance of certain charts, or provide instructions and motivational messages to the team. By adding text widgets, a dashboard moves from being a collection of raw charts to a guided analytical experience. The Highlights Panel (Option C) is a feature of Record Pages, not Dashboards. Assigning tasks (Option B) or sending mass emails (Option D) are communication methods but do not enhance the visual or narrative quality of the dashboard itself. Text widgets empower administrators to highlight trends and call out specific goals, making the data more actionable and easier to interpret for the sales reps.

The core logic of any approval process is contained within its Approval Steps18. While the overall process defines the " Entry Criteria " for which records can start the process, the individual Approval Steps are what define the actual " chain of approval " 19191919. Each step can have its own specific criteria to determine if a record should enter that particular step or skip to the next one. Furthermore, the Approval Step is where the administrator specifies the Assigned Approver, whether it be a specific user, a manager, or a queue. This granularity allows for complex routing, such as sending small discounts to a manager but large discounts to a VP. Process Definition Detail (Option A) provides a high-level overview of the process settings. Entry Criteria (Option C) only act as the initial gatekeeper. Approval Actions (Option D) are the automated results (like email alerts or field updates) that happen once a step is decided.

Case Escalation Rules are specifically designed to automate actions when a case has remained in a certain state for a defined period of time. In this scenario, the requirement involves two specific time-based triggers: moving the case after 2 hours and alerting a manager. Escalation rules allow the administrator to define " Escalation Actions " that execute when the time threshold is reached, such as " Reassign to Queue " and " Notify Manager " . Case Assignment Rules (Option D) only fire when a case is first created or manually triggered, not after a time delay 63 . Reports (Option A) and Dashboards (Option B) provide information but do not physically move records or perform automated reassignments.

When users click the " New Report " button, they are presented with a list of Report Types, which act as templates determining which objects and fields are available for the report. Often, an org has many standard report types that are irrelevant or confusing to the average user. To " limit the kinds of reports " and simplify the user experience, a Platform Administrator can use the Select Report Types to Hide feature in the Report and Dashboard Settings. By hiding unnecessary or redundant report types, the admin ensures that users only see the specific templates that align with company reporting standards. This reduces the risk of users creating inaccurate reports using the wrong data models. Report Folder Sharing (Option B) controls who can view or edit existing reports, but it does not restrict the creation of new ones from specific templates. While creating Custom Report Types is a way to define what data is available, the specific act of " limiting " the visible list is handled by the " Hide " functionality.

In the Agentforce environment, deactivating an agent to make configuration changes (like adding a Topic or Action) does not immediately terminate existing sessions. To ensure a smooth user experience, Salesforce allows ongoing conversations to continue using the version of the agent that was active when the session started. The " deactivation " simply prevents new sessions from being initiated. Once the administrator reactivates the agent, new sessions will utilize the updated configuration, while current users finish their interactions without interruption or " system errors " . The window does not automatically close, and the conversation is not " paused " in a way that requires the user to wait for reactivation

A Roll-up Summary Field is a powerful feature that calculates values from related records and displays them on a master record. However, this functionality is natively available only on the " Master " side of a Master-Detail relationship. For standard objects, Salesforce provides a built-in Master-Detail-like relationship between Accounts and Opportunities . Specifically, the Account object acts as the master, and the Opportunity object acts as the detail. This relationship allows a Platform Administrator to create roll-up summary fields on the Account to calculate the sum of " Total Opportunity Amount, " the " Minimum Close Date, " or a " Count " of all related opportunities . Other standard objects like Contacts (Option B) and Cases (Option C) have a lookup relationship to Accounts rather than a master-detail relationship, and therefore do not support native roll-up summaries20. Campaigns (Option D) also do not share this specific relationship with Accounts21. If an administrator needs to roll up data from these other objects, they would typically need to use a custom solution like Flow Builder or a third-party app, whereas Opportunities are supported natively out of the box .

When building prompt templates within the Prompt Builder, the most direct way to inject specific record data into the AI ' s instructions is through Merge Fields. Much like an email template or a mail merge, merge fields allow the administrator to reference specific fields from the object in context—in this case, the Case object. For example, an administrator might use {!$Input:Case.Subject} or {!$Input:Case.Description} within the prompt template. When the agent runs, it replaces these placeholders with the actual data from the specific case record being viewed. This ensures that the AI has the " grounding " information it needs to generate an accurate and relevant summary. While Flows (Option A) can be used for more complex data retrieval, Merge Fields are the standard, low-code tool for simple record-to-prompt data population. Agent Instructions (Option C) provide the " how-to " logic for the AI but do not themselves represent the dynamic data points from the Salesforce database.

The Company Information page in the Setup menu is the " source of truth " for an organization ' s high-level metadata and licensing. In the User Licenses related list on this page, the administrator can see every license type purchased (e.g., Salesforce, Salesforce Platform, Force.com), the total number of seats allocated, the number of seats currently in use, and the number of remaining available licenses. This is the first place an administrator should look for budgeting and capacity planning. " Usage-based entitlements " (Option A) tracks limited-resource features like Login minutes or Data Cloud credits, but not standard seat-based user licenses. Searching for license types (Option B) or checking user management settings (Option D) will not provide a consolidated summary of the total license pool.

To ensure that a field is populated on every single record, regardless of how it is created (manually, via API, or through an integration), the best method is to make the field universally required at the field definition level. When a field is marked as " Required " in the Object Manager, the Salesforce database will reject any attempt to save a record if that field is empty. While requiring a field on a Page Layout or Record Type (Option B) provides a good user experience for manual entry, it does not prevent records from being created without that data via the API or background processes25. Using a flow (Option A) to update the field is reactive rather than preventative26. Universal requirement is the most robust way to maintain data integrity for critical fields like " Billing System " that are essential for reporting and external system alignment.

Escalation Rules are designed specifically to perform actions when a Case record has remained in a certain state (like " Open " ) for a specified period. In this scenario, the Platform Administrator would set an escalation rule entry with the age set to 168 hours (7 days). When this time threshold is reached, the rule can automatically reassign the case to a new owner or a management queue 51 . Assignment Rules (Option C) are only triggered upon the initial creation of a record or when manually triggered by a user, and they do not have a built-in " timer " capability to fire days later 52 . Auto-Response Rules (Option B) are only for sending automated emails to customers, not for internal ownership changes 53 . Validation Rules (Option D) are used to prevent data entry errors and cannot change record ownership 54 .

Opportunity Contact Roles allow sales reps to link multiple Contacts to a single Opportunity and assign a specific " Role " to each, such as " Decision Maker, " " Influencer, " or " Economic Buyer. " This provides the visibility needed to understand the " buying committee " for a deal. It also allows for the designation of a " Primary Contact. " Opportunity Teams (Option A) are used to track internal staff working the deal. Account Teams (Option B) track collaboration at the account level but are not deal-specific. Standard fields (Option C) are insufficient for tracking a " one-to-many " relationship between an opportunity and multiple contacts with unique roles. Contact Roles are the standard feature designed exactly for stakeholder management in the sales process.

In the Salesforce Lightning Experience, the buttons and actions that appear in the header (Highlights Panel) of a record are controlled by the Salesforce Mobile and Lightning Experience Actions section of the Page Layout. If a specific action like " Log a Call " is missing, it is usually because it has not been dragged into this specific section in the Page Layout editor. While standard actions sometimes appear in the Activity component (Option A), they are explicitly configured for the header via the Page Layout. There is no specific " Log a Call permission " (Options C and D) that would hide only that button; if a user has permission to create Tasks, they generally have the ability to use the Log a Call feature if it is present on the layout.

A Delegated Approver is a user designated by an individual or an administrator to act on their behalf when an approval request is received. This is particularly useful for planned absences, such as vacations. While the delegated approver has the power to approve or reject a record, they cannot reassign the request to someone else. This is a temporary manual assignment and is different from a Manager (Option D), who is part of the permanent role hierarchy, or a Queue (Option B), which allows a group of people to share approval tasks. There is no feature called an " Approval Rule " (Option A) that handles temporary user reassignment in this manner.

To automate the update of related records (Opportunity Products) based on a change to a parent record (the Opportunity), Flow Builder is the most powerful and app7ropriate tool. Specifically, a " Record-Triggered Flow " can be configured to fire whenever an Opportunity is updated to the " Closed Won " stage. The flow can then use a " Get Records " element to find all Opportunity Product records associated with that specific Opportunity and an " Update Records " element to apply the discount value from the parent to each line item. Formula Fields are insufficient here because they are " read-only " and cannot physically push data into other records for permanent storage. Approval Processes manage status changes but are not designed for bulk child-record updates. Flow Builder provides the logic necessary to handle this " one-to-many " update scenario, significantly reducing manual data entry for sales reps and ensuring that the financial data on the products accurately reflects the agreed-upon deal terms.

For a custom object to support Tasks and Events, the " Allow Activities " setting must be enabled in the object ' s properties. When a Platform Administrator creates a custom object, this checkbox is often left unchecked by default35. Enabling this feature allows the " Related To " (WhatId) field on a Task or Event to be linked to records of that custom object type36. While adding the related list to the page layout (Option C) is a necessary step for visibility, it will not work if the underlying feature isn ' t enabled first37. Sharing rules (Option A) and profile permissions (Option D) manage access to existing records but do not control whether the object is technically capable of having activities associated with it.

The Opportunity Sales Path (or simply Path) is a visual representation of the stages in a sales process. It is the best tool for this requirement because it not only shows the current stage prominently at the top of the record but also allows administrators to define Key Fields and Guidance for Success for every stage. This guidance can include specific steps, tips, and links to company resources that explain exactly what a rep needs to do to move the deal to the next phase. Reports (Option A), List Views (Option D), and Big Deal Alerts (Option C) provide data and notifications but do not offer the contextual, stage-by-stage guidance that the Path provides.

The Mobile Only app is the default navigation experience in the Salesforce mobile app when no other Lightning apps have been assigned to a user for mobile use64. In this configuration, the navigation menu is controlled globally via the " Salesforce Navigation " setup page6565. A key behavior of this interface is that the first four items placed in the navigation list become the " persistent " icons that appear in the navigation bar at the bottom of the mobile screen for quick access66. These same items also appear at the top of the " Menu " tab67. Option A is incorrect because pages must have a corresponding Tab created before they can be added to the navigation menu68. Option B is incorrect because the " Mobile Only " navigation is a single global setting for the entire org; if you need different menus for different profiles, you must create and deploy specific Lightning Apps69. Option D is incorrect because standard objects do not appear automatically; the administrator must explicitly add them to the navigation list in Setup70. Understanding this behavior is essential for ensuring mobile users have a streamlined and intuitive interface

In the Salesforce Lightning Experience, the Highlights Panel at the top of a record page is controlled by the Compact Layout. The compact layout determines which fields (up to 7) appear in the record header and in the hover-over details. To add a new custom field to this area, the Platform Administrator must go to the Object Manager for Accounts, select Compact Layouts, and either edit the existing primary layout or create a new custom one. After adding the custom text area field to the " Selected Fields " list and saving, the field will immediately appear in the Highlights Panel for users. It is a common misconception that the standard Page Layout editor (Option D) controls the highlights panel; while the page layout controls the " Details " section and " Related Lists, " it does not manage the header area. Option B might make the field easier to find in the details section but will not place it in the highlights panel.

When an administrator needs to perform a " cleanup " of existing data in bulk, a Schedule-triggered flow is the most efficient choice. This type of flow can be configured to run once (or on a recurring schedule) and process all Lead records that meet the " inconsistent " criteria (e.g., Lead Source equals ' Website ' or ' Online ' )46. The flow can then automatically update those records to the standard " Web " value. A Record-triggered flow (Option B) only works on records as they are being created or updated, so it would not fix historical data unless every record was manually touched Screen flows (Option D) require manual user interaction for each record. 53Segment-triggered flows (Option A) are used in Data Cloud marketing conte54xts rather than standard core record cleanup.

In Salesforce reporting, a Bucket Column is the most efficient tool for categorizing records without the need for creating custom fields or complex formula logic. Bucketing allows an administrator to define ranges of values for a field—such as the " Contract Value " currency field—and assign a label to each range, such as " Small, " " Medium, " or " Large. " This is particularly useful for grouping data into segments that do not exist natively in the data model. For example, if a " Small " account is defined as anything under $50,000 and " Large " is over $200,000, the bucket tool allows the admin to visually organize these in the report builder interface. Unlike Grouping Rows, which merely clusters identical values together, a Bucket Column transforms raw data into meaningful categories for visualization. This feature significantly enhances data storytelling by providing a summarized view of account distribution based on specific financial thresholds without impacting the actual Account record or requiring administrative overhead for new fields.

When a specific user encounters an error that an administrator cannot replicate, the most effective troubleshooting technique is to " Login as " that user. This feature, which must be enabled in the organization ' s login policies, allows the administrator to see exactly what the user sees and experience the system through their specific profile, role, and sharing permissions22. This is vital for identifying issues related to Validation Rules, Field-Level Security, or Record-Triggered Flows that might only trigger under specific user contexts. Logging in as a system administrator (Option A) is ineffective because administrators often bypass certain restrictions that apply to standard users4. Asking for a password (Option D) is a major security violation and is never required in Salesforce5. By using the " Login as " feature, the admin can pinpoint whether the error is caused by the user ' s data input or a specific permission conflict assigned to their profile.

When a single picklist field needs to show different values to different users or for different business contexts, Record Types are the configuration point. While the master list of all possible values is defined in " Fields and Relationships " (Option D) or a " Global Value Set " (Option C), the Record Type determines which of those values are " available " for a specific type of record. For example, a " Wholesale " record type might show different discount levels than a " Retail " record type. If users are seeing inconsistent or incorrect options, the Platform Administrator must go to the specific Record Type settings for the Opportunity object, find the picklist in question, and move values between the " Available " and " Selected " columns. This provides a tailored user experience and prevents users from selecting values that do not apply to the specific type of record they are managing.

In Salesforce, when a Platform Administrator changes a field ' s data type from Auto Number to Text, the operation is considered " safe " regarding data retention. The existing values that were automatically generated by the system (e.g., " INV-1001 " ) will remain unchanged and stay within the field as static text strings12. However, once the change is saved, the system will no longer increment or automatically generate new numbers for future records; users will have to enter data manually. It is important to note that the reverse operation—changing a Text field to an Auto Number—is different, as it would require the administrator to decide whether to overwrite existing data or only number new records14. Options B, C, and D are incorrect because Salesforce explicitly supports this specific conversion without deleting or fundamentally transforming the existing data into a different format other than plain text.

In Salesforce, a dashboard’s running user determines which data is displayed to anyone viewing the dashboard. If a dashboard is configured with a " Static " running user (e.g., a Support Manager who has " View All " permissions), every user who views that dashboard will see the manager ' s level of data, regardless of their own personal sharing permissions. This bypasses the Organization-Wide Default (OWD) of " Private " for the Case object. When the support manager observes that reps can see all cases on a group dashboard, it is almost certainly because the dashboard is " running " as a user with high-level access. To correct this and ensure users only see data they are entitled to, the Platform Administrator should convert it into a Dynamic Dashboard. A dynamic dashboard is set to " Run as the logged-in user, " meaning the data reflected in the components will automatically filter based on the individual viewer ' s specific sharing rules and record ownership. This ensures that the dashboard remains a useful tool for the team while strictly adhering to the company ' s data privacy and security requirements.

Salesforce allows Queues to be designated as assigned approvers in an approval process. When a record is submitted for approval and routed to a queue, an email notification is sent to all queue members (depending on queue settings). The core behavior is that any member of the queue can " claim " the request and either approve or reject it. Once one member takes action, the step is considered complete, and the queue is treated as a single decision-making entity. Unanimous approval (Option A) is a specific setting for multiple individual assigned approvers, but it does not apply to queues in this way. Option C is incorrect because the purpose of a queue is to notify all members to ensure a timely response. Queues are supported for most standard and all custom objects (negating Option D).