Free Data Cloud for Agentforce Practice Questions — Salesforce Agentforce Specialist

Question 1 of 6 · Data Cloud for Agentforce

A financial services company uses Data Cloud to unify customer data from Salesforce CRM, a legacy banking system, and mobile app interactions. They want Agentforce to provide personalized investment recommendations based on real-time portfolio values, transaction history, and risk tolerance scores. The portfolio values update every 15 minutes via streaming API. Which Data Cloud configuration ensures Agentforce accesses the most current data while maintaining performance?

Streaming ingestion with real-time Identity Resolution ensures portfolio updates are immediately reflected in unified profiles. Calculated insights can combine streaming portfolio data with static risk tolerance scores, and the unified individual profile provides the single source of truth that Agentforce queries. Streaming refresh (available for high-frequency data streams) ensures Agentforce sees data within seconds of ingestion, critical for real-time financial recommendations.

Question 2 of 6 · Data Cloud for Agentforce

An insurance company's Data Cloud contains 50 million customer records with policy details, claims history, and call center interactions. They're deploying Agentforce to handle first-notice-of-loss claims. The agent needs to verify customer identity, retrieve active policies within 2 seconds, and check for fraud indicators based on claim patterns across the last 5 years. Data Cloud has Identity Resolution configured with deterministic matching on policy numbers. Which approach BEST optimizes Agentforce response time while maintaining data accuracy?

Low-latency query mode (optimized for sub-second response) combined with pre-computed calculated insights (fraud scores calculated daily in batch, stored on unified profiles) provides the fastest read performance. The Data Cloud connector for Agentforce is the native, supported integration path. Field-level security ensures compliance while maintaining speed. This architecture meets the 2-second SLA by avoiding real-time computation of 5-year fraud patterns during agent conversations.

Question 3 of 6 · Data Cloud for Agentforce

A retail company uses Data Cloud to create unified profiles from e-commerce purchases, in-store POS transactions, and loyalty program activity. They want Agentforce to proactively reach out to customers who have abandoned carts over $200 in the last 24 hours. The agent should reference specific products in the cart and offer personalized discounts based on lifetime value tier. Which Data Cloud activation method enables this Agentforce use case?

Streaming insights can trigger real-time actions when cart abandonment occurs. Writing to a custom object provides Agentforce with queryable, structured data including cart line items. Flow can evaluate lifetime value tier and conditionally trigger Agentforce outbound actions (available for proactive engagement scenarios). This architecture leverages Data Cloud's event detection while using native Salesforce automation for agent orchestration. The custom object serves as the activation target that Agentforce can reliably query.

Question 4 of 6 · Data Cloud for Agentforce

A healthcare provider has unified patient data in Data Cloud from EHR systems, patient portals, and appointment scheduling platforms. Due to HIPAA requirements, only nurses and doctors with active treatment relationships can access a patient's full medical history. Agentforce agents will help patients schedule appointments and answer general questions, but must NOT access diagnosis codes, lab results, or prescription history. Which Data Cloud configuration enforces this access control for Agentforce?

Data Cloud permission sets can restrict access to entire Data Model Objects (DMOs), preventing Agentforce from even querying tables containing sensitive medical data. Assigning a restricted permission set to the Agentforce service user (the integration user identity) enforces the principle of least privilege. Audit logging is critical for HIPAA compliance to track all access attempts. This approach uses Data Cloud's native security model correctly.

Question 5 of 6 · Data Cloud for Agentforce

A telecommunications company's Data Cloud unifies customer data from billing systems, network usage logs, support tickets, and device upgrade history. They want Agentforce to predict and proactively address network issues by analyzing usage patterns. When a customer's data usage spikes 300% above their 30-day average, Agentforce should initiate a conversation to recommend a higher-tier plan. Usage data streams into Data Cloud every 5 minutes. Which combination of Data Cloud features enables this predictive Agentforce action?

Data Cloud calculated insights support rolling window functions (30-day average) that can be refreshed frequently for high-velocity data. Activations can include comparison logic (though typically this is implemented as a segment criterion using the calculated insight). The architecture correctly uses streaming ingestion → calculated insight → activation → Agentforce trigger. While the 'activation that compares' is slightly simplified (you'd typically create a segment using the calculated insight, then activate that segment), this is the most architecturally sound option that uses native Data Cloud features without custom code.

Question 6 of 6 · Data Cloud for Agentforce

A B2B software company uses Data Cloud to create unified accounts from CRM opportunities, product usage telemetry, support case history, and invoice data. Their Agentforce agent assists customer success managers by providing renewal risk scores and expansion opportunities. The risk score calculation requires: contract end date, product usage trend (last 90 days), support ticket severity counts, and payment history. Usage telemetry streams in hourly; other data sources sync daily. Which Data Cloud design optimizes Agentforce performance for CSM conversations that require risk scores on-demand?

A single calculated insight can reference multiple data sources with different refresh cadences. Setting the calculated insight refresh to hourly ensures the risk score incorporates the latest telemetry data (most volatile source) while using daily data for slower-changing sources. Storing the risk score on the unified account profile provides a single query path for Agentforce without complex joins at query time. This balances data freshness with query performance — hourly refresh is sufficient for CSM conversations (not real-time trading) and avoids compute waste from constant recalculation.