AP-211 Salesforce Accredited Agentforce Health Professional Free Practice Exam Questions (2026 Updated)

Setting up Virtual Care entails installing the Virtual Care unmanaged package, configuring Salesforce Scheduler for video visit time slots, and assigning the Health Cloud Video Calls permission set. Virtual Care supports remote care delivery and video visits while integrating with scheduling and patient-access experiences. From a deployment perspective, the configuration must be activated, licensed, permissioned, or migrated in the correct sequence so that the functionality is available to users without weakening the organization ' s existing security and governance controls. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Assign Health Cloud Video Calls permission set.; Install the Virtual Care unmanaged package.; Set up and configure Salesforce Scheduler.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Deploy - Virtual Care

===============

Patient list security honors standard Salesforce object and field-level security (hidden fields omit columns, missing object access prevents list creation) and list-view sharing settings. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (If a user ' s field-level security restricts access to a field used as a display column, the column does not appear in the list.; Users with profile or permission sets that restrict access to an object cannot create a list using that object.; Administrators can restrict access to patient or member lists using standard Salesforce sharing settings on the list.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - Security; Sharing

===============

Advanced Therapy Management Multi-Step Scheduling automatically orchestrates and books dependent sequential appointments (apheresis, manufacturing slot, infusion) across multiple locations. Advanced Therapy Management coordinates complex personalized-treatment journeys, including multi-step scheduling and therapy orchestration for activities such as apheresis, manufacturing, and infusion. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Advanced Therapy Management) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - Advanced Therapy Management

===============

For a patient contact center handling scheduling and billing inquiries, the primary end-user persona is the Contact Center Agent, supported by the Salesforce Administrator and Integration Architect as technical stakeholders. From a discovery perspective, the consultant should validate the current-state workflow with the people who perform it, document pain points and handoffs, and translate the findings into functional, data, security, and integration requirements before solution design begins. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Personas: Contact Center agent | Stakeholders: Salesforce administrator, Integration architect ✔ (Correct Answer)) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Discovery - Provider; Integration; Scheduling

===============

Standard provider data model objects include Provider Education (credentials/schooling), Healthcare Practitioner Facility (facility affiliations), and Healthcare Provider Specialty. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Provider Education; Healthcare Practitioner Facility; Healthcare Provider Specialty) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - Provider

===============

The Health Cloud Clinical Data Model is explicitly aligned to HL7 FHIR R4 standard entities, including Medication, MedicationRequest, MedicationStatement, and MedicationDispense. The FHIR-aligned Clinical Data Model represents clinical concepts such as conditions, encounters, observations, procedures, allergies, and medication information in a consistent healthcare structure. FHIR R4 provides standardized healthcare resources and REST-oriented semantics, reducing dependence on proprietary object structures when clinical data is exchanged with EHRs, payers, or other healthcare systems. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach.

Study Guide references/topics:Design - Clinical data model; FHIR; Medication

===============

OmniStudio FlexCards (UI), Integration Procedures (data orchestrator combining internal and external APIs), and DataRaptors (internal data transform) form the recommended declarative stack for composite data display. OmniStudio separates presentation, guided interaction, Salesforce data access, and server-side orchestration through FlexCards, OmniScripts, DataRaptors/Data Mappers, and Integration Procedures. DataRaptors, now also represented as Data Mappers in current OmniStudio terminology, declaratively extract, transform, and load Salesforce data for OmniStudio components. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Integration Procedures; DataRaptors; FlexCards) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - OmniStudio; DataRaptor; Integration Procedure

===============

Health Cloud provides a purpose-built Social Determinants of Health (SDOH) data model (CareBarrier, CareBarrierType, CareIntervention) designed to capture and address non-clinical factors. Social Determinants of Health capture nonclinical factors such as transportation, food, housing, and financial barriers and connect those determinants to care barriers and interventions. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Leverage the Social Determinants data model in Health Cloud and extend it as needed.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - Social Determinants

===============

Standard provisioning for Health Cloud users requires the Health Cloud permission set license (or Health Cloud User) alongside the Health Cloud Platform permission set license. From a deployment perspective, the configuration must be activated, licensed, permissioned, or migrated in the correct sequence so that the functionality is available to users without weakening the organization ' s existing security and governance controls. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Health Cloud permission set license; Health Cloud Platform permission set license) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Deploy - Agentforce Health architecture and implementation

===============

OmniStudio Document Generation allows users to dynamically generate personalized documents from Microsoft Word/DOCX or PDF templates using Salesforce record data. OmniStudio separates presentation, guided interaction, Salesforce data access, and server-side orchestration through FlexCards, OmniScripts, DataRaptors/Data Mappers, and Integration Procedures. Integrated Care Management structures care plans around reusable problems, goals, interventions, assessments, and care-team activities so care coordination can be standardized and personalized. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (OmniStudio Document Generation) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - OmniStudio; Care Plan

===============

Human-centered design and consulting best practices require identifying key user personas and conducting ' day-in-the-life ' shadowing/interviews to discover operational bottlenecks and define optimal workflows. From a discovery perspective, the consultant should validate the current-state workflow with the people who perform it, document pain points and handoffs, and translate the findings into functional, data, security, and integration requirements before solution design begins. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Identify personas and ask them to walk through a day in their life, taking notes and identifying opportunities for optimization.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Discovery - Agentforce Health architecture and implementation

===============

In Integrated Care Management, the Care Plan creation wizard is delivered as an OmniStudio OmniScript, allowing rapid declarative customization of steps, fields, and branch logic. OmniStudio separates presentation, guided interaction, Salesforce data access, and server-side orchestration through FlexCards, OmniScripts, DataRaptors/Data Mappers, and Integration Procedures. Integrated Care Management structures care plans around reusable problems, goals, interventions, assessments, and care-team activities so care coordination can be standardized and personalized. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (OmniScript) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - OmniStudio; Care Plan

===============

Access to Provider Network Management features requires the Provider Network Management permission set combined with the base Health Cloud Foundation permission set. Provider Network Management supports provider recruitment, credentialing, contracting, onboarding, network participation, and payment-agreement processes for payer organizations. From a deployment perspective, the configuration must be activated, licensed, permissioned, or migrated in the correct sequence so that the functionality is available to users without weakening the organization ' s existing security and governance controls. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Provider Network Management permission set; Health Cloud Foundation permission set) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Deploy - Provider Network Management

===============

Benefits Eligibility and Verification allows coordinators to perform real-time verification of a patient ' s insurance policy, copay, deductible, and coverage limits. Benefits Eligibility and Verification exposes insurance coverage information such as eligibility, copays, deductibles, coinsurance, and benefit limits through healthcare-specific workflows and integrations. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Benefits Eligibility and Verification) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - Benefits

===============

In Health Cloud Utilization Management, Care Request (parent) and Care Request Item (child line items) represent prior authorization and preauthorization requests and outcomes. Utilization Management structures care requests, authorization review, medical-necessity determination, concurrent review, and related payer-provider approval workflows. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Care Preauth and Care Preauth Item) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - Utilization Management

===============

Medication Management provides clinicians with a consolidated 360-degree view of a patient ' s medication regimen, prescription history, dosage, and reconciliation tools. Medication Management consolidates medication requests, statements, dispensing information, reconciliation, review, and interaction-oriented workflows so clinicians can evaluate a patient ' s regimen longitudinally. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Medication Management) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - Medication

===============

To make Provider Search available to external portal users, the admin must place the Provider Search component on an Experience Cloud site page and grant the external profile Read access to Care Provider Searchable Field. Provider Search uses healthcare-specific provider and facility relationships so users can search by criteria such as specialty, location, network, and practice attributes. From a deployment perspective, the configuration must be activated, licensed, permissioned, or migrated in the correct sequence so that the functionality is available to users without weakening the organization ' s existing security and governance controls. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Give the site user profile Read access to the Care Provider Searchable Field object.; Use Experience Builder to add the Provider Search component to a page on the site.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Deploy - Provider Search

===============

Remote Client Monitoring (RCM) in Health Cloud requires Code Sets (standard LOINC/SNOMED codes), Units of Measure (e.g., mmHg, bpm), Care Metric Targets (patient threshold goals), and Care Observations (incoming device telemetry readings). From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Code Sets, Units of Measure, Care Metric Targets, Care Observations) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - Agentforce Health architecture and implementation

===============

In Provider Network Management, the Payment Agreement object defines feefor-service, capitation, or value-based payment structures established with healthcare providers. Provider Network Management supports provider recruitment, credentialing, contracting, onboarding, network participation, and payment-agreement processes for payer organizations. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Payment Agreement) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - Provider Network Management

===============