AI Specialist Agentforce-Specialist Full Course Free

When the preview button is greyed out in a Flex prompt template, it is often because the records related to the prompt have not been selected. Flex prompt templates pull data dynamically from Salesforce records, and if there are no records specified for the prompt, it can't be previewed since there is no content to generate based on the template.

Option B, not saving or activating the prompt, would not necessarily cause the preview button to be greyed out, but it could prevent proper functionality.

Option C, missing a merge field, would cause issues with the output but would not directly grey out the preview button.

Ensuring that the related records are correctly linked is crucial for testing and previewing how the prompt will function in real use cases.

Salesforce Agentforce Specialist References:

Refer to the documentation on troubleshooting Flex templates here:

Since security and data privacy are critical, the best option for the Agentforce Specialist is to integrate the fine-tuned LLM (Large Language Model) into Salesforce by adding it to Einstein Studio Model Builder. Einstein Studio allows organizations to bring their own AI models (BYOM), ensuring the model is securely managed within Salesforce’s environment, adhering to data privacy standards.

Option A (embedding via iFrame) is less secure and doesn’t integrate deeply with Salesforce's data and security models.

Option C (making callouts to OpenAI) raises concerns about data privacy, as sensitive Salesforce data would be sent to an external system.

Einstein Studio provides the most secure and seamless way to integrate custom AI models while maintaining control over data privacy and compliance. More details can be found in Salesforce's Einstein Studio documentation on integrating external models.

Per the AgentForce Data Cloud Integration Guide, the AI Agent Session (AIAGENTSESSION) object represents an overarching container that tracks a continuous interaction between one or more AI agents and a user. The document describes: “AI Agent Session is the parent container for a contiguous set of AI Agent interactions. It captures metadata, start and end times, and the relationship to individual messages exchanged during the session.”

Option A, AIAGENTINTERACTION, represents a single step or event within the session, while AIAGENTINTERACTIONMESSAGE (Option B) represents individual messages or exchanges within that interaction. Therefore, AIAGENTSESSION is the correct DLO for reporting on broader agent behavior and performance across an entire engagement.

References (AgentForce Documents / Study Guide):

AgentForce Data Cloud Reporting Guide: “Understanding Agent DLO Hierarchy”

AgentForce Study Notes: “AI Agent Session, Interaction, and Message Object Relationships”

Salesforce Data Cloud for AI Agents: “AI Agent Session Overview”

Universal Containers (UC) is using Apex classes within an Agent Action for their Agentforce Agent. Deploying Apex in Salesforce has specific requirements, especially when tied to Agentforce functionality. Let’s evaluate the options.

Option A: The Apex classes must have at least 75% code coverage from unit tests, and all dependencies must be in the deployment package.Salesforce enforces a strict requirement that all Apex classes must achieve at least 75% code coverage from unit tests for deployment to production, regardless of their use case (e.g., Agentforce, triggers, or web services). Additionally, when Apex is invoked by an Agent Action (e.g., via a Flow or direct invocation), all dependencies (e.g., referenced classes, objects) must be included in the deployment package to ensure functionality. This is a standard deployment consideration in Salesforce and applies to Agentforce, making this the correct answer.

Option B: Apex classes invoked by an Agent Action may be deployed with less than 75% test coverage as long as the agent is not activated in production.Salesforce’s 75% code coverage requirement is mandatory for production deployment, regardless of whether the agent is activated. There’s no exemption based on activation status—coverage is enforced at the deployment stage. This option is incorrect and contradicts Salesforce’s Apex deployment rules.

Option C: The Apex classes may bypass the 75% code coverage requirement as long as they are only used by the agent.No such bypass exists in Salesforce. The 75% code coverage rule applies universally to all Apex in production, including classes used by Agentforce. Agent-specific usage doesn’t waive this requirement, making this incorrect.

Why Option A is Correct:

The 75% code coverage requirement and inclusion of dependencies are fundamental Salesforce deployment rules, applicable to Apex in Agent Actions. This ensures reliability and functionality in production, as per official documentation.