Scenario practice questions

An administrator needs to create a field on the Account object that calculates the number of days since the last contact with the client. The value must update automatically. Which field type is most appropriate?

Trap 1: Roll-up Summary field

Roll-up Summary fields are restricted to master-detail relationships and perform aggregations like COUNT, SUM, MIN, or MAX. They cannot perform date-based arithmetic or compare record fields against the current system date, making them unsuitable for calculating the elapsed time since a specific date value on a single record.

Trap 2: Number field populated by a Flow

While a Flow could update a number field, it is not the most efficient solution here. Flows are triggered by events and might not update accurately if the underlying date changes but no record change event occurs. A Formula field is declarative and updates instantly whenever the record is viewed.

Trap 3: Text field updated by a Validation Rule

Validation Rules are used to restrict record saving if data quality requirements are not met; they cannot be used to calculate or populate values into fields. Using a text field would require manual intervention or external automation, which contradicts the requirement for an automated and self-updating value.

A
Roll-up Summary field
Why it fails: Roll-up Summary fields are restricted to master-detail relationships and perform aggregations like COUNT, SUM, MIN, or MAX. They cannot perform date-based arithmetic or compare record fields against the current system date, making them unsuitable for calculating the elapsed time since a specific date value on a single record.
B
Number field populated by a Flow
Why it fails: While a Flow could update a number field, it is not the most efficient solution here. Flows are triggered by events and might not update accurately if the underlying date changes but no record change event occurs. A Formula field is declarative and updates instantly whenever the record is viewed.
C
Formula field
Formula fields are designed to derive values from other fields or system functions like TODAY() or NOW(). They are read-only to users and update automatically whenever the record is accessed, providing the most reliable and maintenance-free way to represent calculated data points like the duration of time.
D
Text field updated by a Validation Rule
Why it fails: Validation Rules are used to restrict record saving if data quality requirements are not met; they cannot be used to calculate or populate values into fields. Using a text field would require manual intervention or external automation, which contradicts the requirement for an automated and self-updating value.

Question 2hardmulti select

An administrator at Cosmic Enterprises is preparing an Agentforce Service Agent for a new return policy topic. Before activation, the security team requires that the agent never expose customer payment card digits and that every interaction be traceable for compliance review. (Choose two.)

Trap 1: Reduce the agent's topic scope so it only answers questions about…

Narrowing topics limits what the agent attempts to answer, which can reduce risk incidentally, but it does not mask card digits when payment data does enter context and it generates no compliance record of interactions. The security team's requirements are technical controls, and scope reduction is a design choice that leaves both controls absent.

Trap 2: Assign the agent user a profile with Modify All Data so it can…

Granting Modify All Data would let the agent read and change virtually every record, which expands exposure instead of limiting it and violates least privilege. Broader access does nothing to prevent raw card digits from reaching the model or to create an audit record, so it works against both security requirements rather than satisfying either of them.

Trap 3: Create a validation rule on the payment object that blocks saving…

A validation rule restricts what users and integrations can persist, which is useful data hygiene, but it does not govern what an agent sends to or receives from a model at runtime. Existing records with digits would still be retrievable and could appear in responses, and the rule produces no interaction trace, so neither requirement is met.

A
Reduce the agent's topic scope so it only answers questions about store hours and shipping times.
Why it fails: Narrowing topics limits what the agent attempts to answer, which can reduce risk incidentally, but it does not mask card digits when payment data does enter context and it generates no compliance record of interactions. The security team's requirements are technical controls, and scope reduction is a design choice that leaves both controls absent.
B
Enable the Einstein Trust Layer audit trail to capture prompts, responses, and masking events.
The audit trail records interactions between Salesforce, the model, and connected systems, including which masking rules fired. This creates the traceability the security team demands, allowing reviewers to reconstruct what the agent was asked, what it returned, and whether sensitive data was masked, which is precisely the compliance visibility the scenario requires.
C
Assign the agent user a profile with Modify All Data so it can retrieve any record a customer references.
Why it fails: Granting Modify All Data would let the agent read and change virtually every record, which expands exposure instead of limiting it and violates least privilege. Broader access does nothing to prevent raw card digits from reaching the model or to create an audit record, so it works against both security requirements rather than satisfying either of them.
D
Create a validation rule on the payment object that blocks saving records containing full card numbers.
Why it fails: A validation rule restricts what users and integrations can persist, which is useful data hygiene, but it does not govern what an agent sends to or receives from a model at runtime. Existing records with digits would still be retrievable and could appear in responses, and the rule produces no interaction trace, so neither requirement is met.
E
Configure Data Masking rules in the Einstein Trust Layer for the fields that hold card digits.
The Einstein Trust Layer Data Masking capability replaces sensitive values with masked tokens before data leaves Salesforce for the model, and rehydrates them only where appropriate. Applying masking to card-number fields ensures the large language model never receives the raw digits, directly satisfying the requirement that the agent cannot expose payment card data in its responses or prompts.

Question 3mediummultiple choice

A sales manager wants their team to see a dynamic feed of updates, files, and posts related to a specific opportunity directly on the opportunity record page. The administrator needs to add a component that shows this information without requiring users to navigate away. Which component should the administrator add to the Lightning record page?

Trap 1: Activities component

The Activities component displays tasks and events related to the record, not a feed of posts, files, and updates. It is useful for tracking scheduled interactions, but it does not provide the social collaboration feed that the sales manager wants. Therefore, it does not meet the requirement of showing dynamic updates and files from Chatter.

Trap 2: Report Chart component

The Report Chart component displays a chart from a report directly on the record page. It is intended for data visualization, not for collaboration or feed updates. It cannot show posts, comments, or files, so it is not suitable for providing the dynamic feed the sales manager requested.

Trap 3: Related List component

The Related List component shows lists of related records, such as contacts or products, based on the page layout. It does not display Chatter posts, files, or updates. While useful for viewing related data, it does not fulfill the requirement for a dynamic collaboration feed on the opportunity record.

A
Activities component
Why it fails: The Activities component displays tasks and events related to the record, not a feed of posts, files, and updates. It is useful for tracking scheduled interactions, but it does not provide the social collaboration feed that the sales manager wants. Therefore, it does not meet the requirement of showing dynamic updates and files from Chatter.
B
Report Chart component
Why it fails: The Report Chart component displays a chart from a report directly on the record page. It is intended for data visualization, not for collaboration or feed updates. It cannot show posts, comments, or files, so it is not suitable for providing the dynamic feed the sales manager requested.
C
Chatter Feed component
The Chatter Feed component on a Lightning record page displays the record's feed, including posts, comments, files, and updates. This directly provides the dynamic collaboration stream the sales manager wants, allowing users to see relevant interactions without leaving the opportunity page. It is the standard component for record-based Chatter collaboration in Lightning Experience.
D
Related List component
Why it fails: The Related List component shows lists of related records, such as contacts or products, based on the page layout. It does not display Chatter posts, files, or updates. While useful for viewing related data, it does not fulfill the requirement for a dynamic collaboration feed on the opportunity record.

Question 4mediummultiple choice

Universal Containers has a custom object 'Projectc' that has a lookup relationship to Account. The administrator needs to create a formula field on Projectc that displays the Account's Industry. However, when viewing a Project record, the Industry field is blank even though the related Account has an Industry value. What is the most likely cause?

Trap 1: The formula field is referencing a field that is not accessible to…

Formula fields run in system mode and do not enforce field-level security for the referenced fields. Even if the user does not have access to the Industry field on Account, the formula field would still display the value. Therefore, field-level security is not the cause of the blank value.

Trap 2: The formula field is using the wrong syntax to reference the…

If the syntax were incorrect, the formula field would either not save or return an error, not a blank value. Salesforce validates formula syntax at save time. A blank result indicates that the referenced field is empty or the lookup is empty, not a syntax error.

Trap 3: The Account's Industry field is not included in the page layout.

Page layout settings do not affect formula field calculations. The formula field evaluates based on data, not on whether the referenced field is on a layout. Even if Industry is not on the Account page layout, the formula field would still display the value if the lookup is populated and the field has data.

A
The lookup relationship is not populated on the Project record.
If the lookup relationship to Account is empty on the Project record, the formula field that references Account.Industry will return blank. The formula field can only display the Industry if there is a related Account. The most likely cause is that the Project record does not have an Account lookup value.
B
The formula field is referencing a field that is not accessible to the user's profile.
Why it fails: Formula fields run in system mode and do not enforce field-level security for the referenced fields. Even if the user does not have access to the Industry field on Account, the formula field would still display the value. Therefore, field-level security is not the cause of the blank value.
C
The formula field is using the wrong syntax to reference the Account's Industry.
Why it fails: If the syntax were incorrect, the formula field would either not save or return an error, not a blank value. Salesforce validates formula syntax at save time. A blank result indicates that the referenced field is empty or the lookup is empty, not a syntax error.
D
The Account's Industry field is not included in the page layout.
Why it fails: Page layout settings do not affect formula field calculations. The formula field evaluates based on data, not on whether the referenced field is on a layout. Even if Industry is not on the Account page layout, the formula field would still display the value if the lookup is populated and the field has data.

Question 5mediummultiple choice

An administrator at Northern Trail Outfitters created an Agentforce Service Agent that resolves billing inquiries. After activation, the agent successfully handles English chats but ignores Spanish chats entirely, even though the org's Einstein Translation and Language Settings are enabled. The administrator confirmed the agent's Employee Agent is assigned and the Messaging channel is live. What should the administrator do to allow the agent to respond to Spanish-speaking customers?

Trap 1: Enable the Einstein Translation for Messaging setting on the…

Einstein Translation for Messaging translates incoming and outgoing messages on a channel, but it does not grant an Agentforce agent the ability to process a language it was not configured for. The agent would still receive untranslated Spanish input in its reasoning layer, so the agent would remain unable to respond meaningfully to those conversations.

Trap 2: Create a duplicate Service Agent with the Spanish locale and route…

Creating a duplicate agent adds maintenance overhead and does not address the underlying language configuration of the existing agent. Agentforce supports multiple languages per agent, so a second agent is unnecessary. Routing rules also cannot reliably detect language before the agent begins processing the conversation, making this approach fragile and inefficient.

Trap 3: Assign the agent's Einstein Agent User a permission set that…

There is no 'Agentforce Multilingual' user permission that governs agent language capabilities. Language support for an agent is a configuration setting within Agentforce Studio, not a permission assigned to the Einstein Agent User. Adding permission sets would not enable the agent to process Spanish input or produce Spanish responses.

A
Enable the Einstein Translation for Messaging setting on the Messaging channel and refresh the embedded deployment.
Why it fails: Einstein Translation for Messaging translates incoming and outgoing messages on a channel, but it does not grant an Agentforce agent the ability to process a language it was not configured for. The agent would still receive untranslated Spanish input in its reasoning layer, so the agent would remain unable to respond meaningfully to those conversations.
B
Create a duplicate Service Agent with the Spanish locale and route Spanish chats to it using Omni-Channel routing rules.
Why it fails: Creating a duplicate agent adds maintenance overhead and does not address the underlying language configuration of the existing agent. Agentforce supports multiple languages per agent, so a second agent is unnecessary. Routing rules also cannot reliably detect language before the agent begins processing the conversation, making this approach fragile and inefficient.
C
Add the Spanish language to the agent's supported languages in Agentforce Studio and republish the agent.
Agentforce agents maintain their own language configuration independent of org-wide translation settings. Adding Spanish under the agent's language settings in Agentforce Studio, then republishing, makes the agent capable of understanding and replying in Spanish. Org-level translation only translates metadata, not agent runtime conversations, so this agent-specific change is required for the scenario.
D
Assign the agent's Einstein Agent User a permission set that includes the 'Agentforce Multilingual' user permission.
Why it fails: There is no 'Agentforce Multilingual' user permission that governs agent language capabilities. Language support for an agent is a configuration setting within Agentforce Studio, not a permission assigned to the Einstein Agent User. Adding permission sets would not enable the agent to process Spanish input or produce Spanish responses.