When a Lead is converted into an Account, Contact, and Opportunity, standard fields are mapped automatically. However, custom fields require manual configuration to ensure d3ata flows through the conversion process. First, the Platform Administrator must create a corresponding custom picklist field on the Contact object (Option B) with the same values as the Lead field. Second, the administrator must go to the Lead Object Manager, select "Fields & Relationships," and click Map Lead Fields (Option C). Here, the admin explicitly maps the Lead custom picklist to the newly created Contact custom picklist. Without this mapping, the data will be lost during conversion.
Validation rules (Option A) and making the field required (Option D) ensure data exists on the Lead but do not facilitate the transfer of that data to the Contact.

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. 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. Auto-Response Rules (Option B) are only for sending automated emails to customers, not for internal ownership changes. Validation Rules (Option D) are used to prevent data entry errors and cannot change record ownership.

When an object's Organization-Wide Default (OWD) is set to Private, the "Record Sharing" engine must be used to grant additional access.
Sharing Rules: These allow the administrator to grant lateral access to records based on criteria or ownership (e.g., share all "Large Deals" with the "Strategic Sales" group).
Role Hierarchy: This standard feature automatically grants vertical access, ensuring that managers and users higher in the hierarchy can see and edit records owned by their subordinates.
Profiles (Option D) control what actions a user can perform (Create, Read, Edit) but do not grant access to specific records that the user does not own in a Private model. A Sharing Set (Option B) is a specific feature used for Experience Cloud (Community) users to grant them access to records related to their account and is not used for standard internal sales users.

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.

Grounding is the process by which an AI agent retrieves and uses specific, trusted data to ensure its responses are accurate and relevant. During this process, Salesforce's Einstein Trust Layer performs several critical checks, including identifying Prompt Injection risks. Prompt injection refers to attempts by a user to "trick" the AI into ignoring its instructions or revealing sensitive data by entering malicious commands into the chat interface. By checking for these risks during the grounding phase, the agent can ensure that the instructions it uses to generate a response remain secure and aligned with company policies. While the agent respects field security,
"Encrypted fields" (Option C) are handled at the data access layer rather than as part of the linguistic grounding check. Standard Agentforce agents do not browse the open web for verification (Option D) as they are intended to remain grounded strictly in the company's verified internal data.