ADM-201 Questions and Answers

A Chatter Stream is a custom feed that users (or administrators) can create to consolidate updates from multiple sources. You can combine feeds from specific groups, individual people (like the CEO), and specific records into a single view. This allows users to stay organized and monitor diverse sets of information in one place without having to navigate between different groups or records. A Chatter Group (Option A) is for a specific set of members. A Daily Digest (Option B) is an email summary. A Chatter Feed (Option C) is a general term for the individual lists of updates but does not natively allow for the targeted " multi-source " consolidation that a Stream provides.

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.

Mobile Home is a customizable landing page for the Salesforce mobile app that acts as the default " start page " for users. It allows administrators to add various " cards " or " widgets, " including reports, pinned records, and upcoming events. By enabling and configuring Mobile Home, a Platform Administrator can place a specific Report card (such as " Top Opportunities " ) at the very top of the screen, ensuring it is the first thing users see upon opening the app. While adding the Reports tab (Option A) or Dashboards tab (Option D) allows users to find the information, it does not automatically present specific report data on the home screen. The " Today " feature (Option B) focuses on calendar events and tasks rather than customized reporting data 17 .

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.

Profiles in Salesforce serve as the foundation for what a user can " do " with records, specifically defining Object-Level Security (Create, Read, Edit, Delete permissions). The standard Marketing User profile typically does not include full " Edit " access to the Opportunity object by default, as marketing roles are traditionally focused on Leads and Campaigns. To fulfill the requirement of allowing marketers to maintain campaign relationships on Opportunities, the administrator must ensure the profile has the necessary object permissions. If the organization is using a custom profile based on the Marketing User template, the admin should edit the object permissions directly on that profile to include " Read " and " Edit " for Opportunities. This allows the marketers to view the records and update the " Primary Campaign Source " field. While a Permission Set could also grant this access, the question implies the admin is currently configuring the profile itself. Adjusting the profile ' s object permissions is the direct way to align the user ' s capabilities with the business ' s functional requirements.

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.

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.

Changing a field type is a significant configuration change that can have downstream impacts. When converting from Text to Picklist, a Platform Administrator must be aware of two critical consequences:

List View Deletion: Any list views that use that specific custom field as a filter will be automatically deleted or the filter will be removed. This happens because the filter logic for a text field (which uses operators like " contains " ) is fundamentally different from a picklist (which uses " equals " ).

Automation Impact: Assignment rules, escalation rules, and validation rules that reference the field may be disabled or function incorrectly. Because these automations rely on specific text strings, changing the field to a picklist requires the administrator to manually review and update the logic to ensure it aligns with the new picklist values.

Option A is incorrect because Salesforce does not automatically update code references. Option C is incorrect because data loss can still occur if existing text values do not exactly match the new picklist entries.

For an administrator who needs to deliver high-quality dashboards " quickly " and " doesn ' t know where to start, " the AppExchange is the best resource. Salesforce Labs provides several free, pre-configured dashboard packages (like the " CRM Dashboards " ) that include standard components for sales pipeline, lead tracking, and case management. These packages serve as an excellent baseline that can be installed in minutes and then customized to fit the specific needs of Cloud Kicks. Manually creating everything (Option D) is time-consuming. Einstein Analytics (Option B) is a separate, more complex product that requires extra licensing and setup. Option A is too narrow, as it focuses specifically on " Field Service " rather than general sales and service visibility.

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 the Salesforce architecture, the Username is a globally unique identifier4949. This means that once a username (e.g., admin@cloudkicks.com) is used in any Salesforce organization (including production, sandboxes, and developer editions), it cannot be used again in any other organization worldwide. This often causes confusion because while an Email Address can be reused across multiple Salesforce users and orgs, the Username must remain distinct51. If an administrator receives a duplicate username error, it means the desired username is already taken by a user in another instance of Salesforce. 54Option A is incorrect because usernames must be in email format, but they don ' t have to be a valid functioning email. Option B is incorrect because only the username has this global uniqueness requirement, not the email address.

A Dynamic Dashboard is a specific type of dashboard where the data displayed changes based on which user is currently viewing it. By setting the " View Dashboard As " property to " The logged-in user, " the dashboard components will respect each individual user ' s sharing settings, role hierarchy, and record ownership. For example, if a sales rep views a dynamic dashboard, they might only see their own $100k pipeline, while their manager viewing the same dashboard would see the team ' s combined $1M pipeline. This eliminates the need for an administrator to create and maintain dozens of identical dashboards for different individuals. Dashboard Filters (Option A) allow users to narrow down data but do not change the fundamental " running user " security context. Setting the dashboard to run as " Me " (the admin) or " Another person " (Options C and D) creates a static view where everyone sees the same data, which is the opposite of providing an individualized view.

When relating two objects where the child records must persist even if the parent record is deleted, a Lookup Relationship is the correct choice18. In this scenario, the Shipment object should have a lookup field pointing to the Account. Unlike a Master-Detail relationship (Option B), which automatically deletes child records (cascade delete) when the master is deleted, a Lookup relationship allows the child record to remain in the system, either by clearing the lookup field or simply leaving it as is. Option A and D are architecturally incorrect because the relationship field is always created on the " child " or " many " side of the relationship (Shipments) to point to the " parent " (Account). Using a Lookup relationship ensures data retention for historical shipment tracking while still allowing the shipment items to be visible via a related list on the Account page.

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.

To manage different levels of support service (Gold, Silver, Bronze), Salesforce uses the Entitlement Management feature. An " Entitlement " defines the specific type of support a customer is eligible for. To " ensure that this is part of every client ' s account " automatically, a Platform Administrator should use Flow Builder. A record-triggered flow can be set to run whenever an Account is updated to " Customer " status or when a specific " Service Level " field is populated. The flow can then automatically create or link an Entitlement record to that Account. This ensures that when a new case is opened, the support agent immediately sees the SLA (Service Level Agreement) associated with that customer. Routing Configurations (Option B) and Assignment Rules (Option D) handle who gets the case, but they do not define the level of service. Email-to-Case (Option C) is an intake method, not a service-level tracking tool.

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

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.

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.

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 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.

The fundamental way to control which records enter an Approval Process is by defining Entry Criteria. During the setup of an approval process, the administrator specifies field-level conditions (e.g., Amount > 50,000 AND Stage = Closed Won) that a record must meet to be eligible for approval. If a user attempts to submit a record that does not meet these criteria, Salesforce will display an error message and prevent the process from starting. This ensures that the finance or management teams are only notified of deals that actually require their sign-off. While a Screen Flow (Option C) could be used to launch the process, the entry criteria within the approval process itself act as the ultimate " gatekeeper " for the automation. Validation rules (Option D) prevent bad data but do not route records for approval. Dynamic Forms (Option B) can show or hide the " Submit for Approval " button, but they do not enforce the underlying business logic of the process itself.

In Salesforce, security restrictions like Login Hours and Login IP Ranges are managed at the Profile level. When these are configured on a profile, they are strictly enforced; if a user attempts to log in outside of the allowed hours or from an unauthorized IP address, the system will deny access entirely. This is one of the most robust ways to secure an organization against unauthorized access. Company Settings (Option A) can set " Trusted IP Ranges " for the whole org, but these only bypass multi-factor authentication; they do not restrict login. Roles (Option B) control record visibility, not system access. While Permission Sets (Option D) can grant many permissions, Login Hours and IP Ranges remain a core profile-level security setting.

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.

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.

The Data Import Wizard is the ideal tool for importing a relatively small number of records (up to 50,000) when those records involve standard objects like Accounts and Contacts simultaneously. One of the unique strengths of the Data Import Wizard is its ability to handle " Account and Contact " imports in a single pass, automatically linking the contacts to the correct accounts based on name or site. Because the volume in this request is only 300 records, the Data Import Wizard provides a simple, browser-based interface that includes built-in duplicate checking, which is highly beneficial for maintaining data quality. While the Data Loader (Option D) and Dataloader.io (Option A) can also handle 300 records, they are typically reserved for much larger datasets (up to 5 million records) or more complex objects. The " Wizard " is the most user-friendly and efficient choice for this specific sales rep request.

To help sales reps prioritize their pipeline and identify which deals are most likely to close, Einstein Opportunity Scoring is the most effective tool. Part of Salesforce ' s AI suite, Opportunity Scoring uses machine learning to analyze past won and lost opportunities to assign a score from 1 to 99 to every open deal. The score is accompanied by " Key Factors " —both positive and negative—that explain why the score was given (e.g., " The deal has progressed quickly through stages " or " The close date has been pushed three times " ). This allows reps to focus their time on high-scoring deals or take corrective action on deals with low scores. Einstein Lead Scoring (Option B) helps with the intake of new prospects but not with existing deals. Einstein Activity Capture (Option D) automates the logging of emails and events but does not provide prioritization logic. Einstein Search (Option A) improves search results but does not assist in deal management strategy.

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).

The Lightning App Builder includes a built-in Analysis tool (often referred to as Page Analysis or Analytics) that provides administrators with a performance score for a record page. This tool evaluates the page ' s metadata and components to identify factors that contribute to slow load times, such as having too many fields in a single section, using complex related lists, or including multiple heavy Lightning Web Components. It provides specific suggestions, such as using " Dynamic Forms " to break up the page or moving less-used components into separate tabs to improve the " time to interact " for the user. The Lightning Usage App (Option B) provides broad metrics on adoption and browser usage across the whole org but does not offer granular, component-level performance analysis for a single record page. Visibility Rules (Option C) are for showing/hiding content, not for technical performance auditing.

An Approval Process is the dedicated Salesforce feature for managing workflows that require human " review and decision-making. " Unlike Assignment Rules (Option A), which simply change the owner of a record, an Approval Process locks the record to prevent further changes and routes a formal request to an " Approver. " This approver can then choose to Approve, Reject, or Reassign the request. The process can include multiple steps, entry criteria (e.g., " only if discount > 10% " ), and specific automated actions that occur once the final decision is made. Validation Rules (Option B) are used to prevent saving bad data, not for routing. Schema Builder (Option D) is a visualization tool for the data model. Therefore, when a business process requires an official " sign-off " or " decision, " the Approval Process engine is the correct architectural choice.

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.

Effective Agentforce instructions must be explicit about the data format, the source of the data, and the requirements for the input. Option D is the best choice because it provides the most detail for the Large Language Model (LLM). It specifies the format (18 character ID / three-digit code), the source (conversation history or user input), and the logic/dependency (required only when the product ID is present). This level of detail prevents the agent from guessing or providing incomplete data to the underlying Salesforce action. Options A and C are too vague and could lead to errors. Option B is better but lacks the explicit " Required " tag and format details found in Option D. High-quality instructions act as a contract between the agent ' s natural language understanding and the structured data requirements of the Salesforce system.

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.

When the Organization-Wide Default (OWD) for an object is set to Private, users can only see records they own or those shared with them. While the Role Hierarchy automatically grants " upward " visibility (managers see what subordinates own), it does not naturally allow for " lateral " visibility or visibility across different branches of the hierarchy. To solve this, a Platform Administrator should use Sharing Rules. Sharing Rules allow the admin to create exceptions to the Private OWD based on record ownership or specific criteria. For example, the admin can create an " Owner-based Sharing Rule " that shares all records owned by the " East Coast Sales " role with the VP of Sales (or a Public Group the VP belongs to). This provides a scalable way to grant the necessary visibility for reporting without making the data public to the entire company. Sharing Rules are a core security feature that ensures the right people have access to the right data while maintaining the principle of least privilege.

Salesforce allows for the creation of multiple Business Hours records to support global teams working in different time zones. To solve the requirement for Ursa Major Solar, the Platform Administrator should create two distinct sets of business hours: one for " Pacific Support " (9 AM - 5 PM PT) and one for " Eastern Support " (9 AM - 5 PM ET). This is essential because Business Hours are used by the system to calculate escalation rules and milestones correctly. For example, an escalation rule for an Eastern-based case 1should start counting at 9 AM ET, not 9 AM PT. Adjusting the current record to " accommodate " both (Option A) would result in a 12-hour window that doesn ' t accurately reflect either team ' s true availability. Users cannot manually set their own business hours (Option B) in a way that affects system automation. Creating one set per time zone ensures that the support team ' s performance metrics and automated routing are accurate and localized.

Case Escalation Rules are the dedicated tool for time-based notifications and reassignments in Service Cloud. The Platform Administrator can set an escalation rule entry that triggers when a case is " Older than 2 hours " and meets specific status criteria (e.g., Status = New). The rule can then be configured to send an Email Notification to a manager or a specific distribution list. This ensures that management is alerted to potential SLA breaches. Assignment Rules (Option A) only run when a case is first created. Formula fields (Option C) can calculate time but cannot send notifications. Omni-Channel Supervisor (Option D) allows for real-time monitoring but does not provide automated email alerting based on specific time-elapsed thresholds.

To provide both a " quick view " and a way to " update " records efficiently, a List View combined with the Kanban view is the most effective solution. The Platform Administrator can create a public list view with the filter " Close Date equals NEXT 90 DAYS. " By switching this list view to the Kanban display, sales reps can see their deals organized by stage. The Kanban view allows for rapid updates via drag-and-drop, which automatically changes the Stage field, and provides side-panel editing for other key fields. While reports (Option A) and dashboards (Option B) are good for visualization, they are not optimized for the rapid, bulk record updates the manager is requesting. The Kanban view is a native productivity feature designed specifically to streamline pipeline management for sales users.

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 .

A Master-Detail Relationship is a tight coupling between two objects that provides several unique functionalities:

Master Object Types: The master can be either a standard object (like Account) or a custom object (Option B).

Roll-up Summaries: This relationship type is the only one that natively supports Roll-up Summary fields, allowing the master record to calculate counts, sums, or averages of fields on the detail records (Option C).

Ownership and Security: The detail record inherits its owner and its security/sharing settings from the master record. Consequently, there is no " Owner " field on a detail record; it is always owned by the owner of the master (Option D).

Option A is incorrect because detail records cannot have independent permissions. Option E is incorrect because an object can only have a maximum of two master-detail relationships. This relationship is ideal for parent-child scenarios where the child ' s existence is entirely dependent on the parent.

A common cause of errors in an Approval Process is a breakdown in the " Approver " chain. If an approval step is configured to route to a specific user or a manager who has been deactivated, Salesforce will throw an error when the current step tries to advance. The Platform Administrator should check the " Next Approver " field on the record or the step definition in Setup to ensure the target user is active and has a valid Salesforce license. While field visibility (Options B and C) is important for the user experience, missing field access typically doesn ' t " error out " the approval engine itself; it just prevents the user from seeing the data. Checking for inactive users is the first step in troubleshooting runtime errors in automated routing processes.