AP-211 Salesforce Accredited Agentforce Health Professional Exam Topics and Questions
These Salesforce Accredited Agentforce Health Professional (AP-211) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise AP-211 sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Accredited Agentforce Health Professional certification exam.
Let's Practice Free Salesforce AP-211 Questions Aligned with Official Exam Topics
Discovery sets the foundation for everything that follows. Before a single Health Cloud object is configured, you need to know who you are building for, what they actually need, and how success will be measured. This topic tests whether you can translate a customer scenario into a structured set of requirements, not just a wish list. The marks here go to candidates who can separate stakeholder needs from technical constraints and map both to project scope. How Discovery is tested...
Discovery sets the foundation for everything that follows. Before a single Health Cloud object is configured, you need to know who you are building for, what they actually need, and how success will be measured. This topic tests whether you can translate a customer scenario into a structured set of requirements, not just a wish list. The marks here go to candidates who can separate stakeholder needs from technical constraints and map both to project scope.
How Discovery is tested
At 11%, Discovery delivers a focused set of scenario-based items. Expect to read a customer situation and identify the right personas or stakeholders to involve, or pick the capability areas that need analysis before implementation begins. The trap is moving too fast: many candidates jump to a solution before the scenario has finished establishing the problem. Items reward disciplined scoping. If a scenario describes a payer organization, the item will test whether you recognize the right stakeholders for that context, not just a generic list of roles. Functional and technical requirements are tested together, so you need to distinguish between what a customer wants to achieve and what the system must do to enable it. Candidates lose marks by conflating the two or by selecting requirements that are technically valid but misaligned with the stated outcomes. Read every scenario for the customer's goal before evaluating any option.
The ITExamsTopics practice test lets you filter by topic, so you can isolate Discovery items and see whether your scoping instincts are consistent before moving to the heavier design and implementation sections. The free demo gives you a first look at the item style at no cost.
The question below puts you in a Discovery scenario where stakeholder identification and requirements alignment are both in play.
Bloomington Caregivers want to offer its patients remote monitoring to bring data from patient devices into Health Cloud.
Which set of records should an administrator populate to implement this functionality?
Design carries the largest share of the exam, and that weight reflects how much of a real Health Cloud engagement lives in the decisions made before anyone opens Setup. You are expected to move fluidly between data modeling, security architecture, integration strategy, and vertical-specific configuration choices. Getting a single design decision wrong in practice means rework across the entire build. The exam mirrors that reality: a scenario can pivot on one object relationship or one sharing model choice. β Data...
Design carries the largest share of the exam, and that weight reflects how much of a real Health Cloud engagement lives in the decisions made before anyone opens Setup. You are expected to move fluidly between data modeling, security architecture, integration strategy, and vertical-specific configuration choices. Getting a single design decision wrong in practice means rework across the entire build. The exam mirrors that reality: a scenario can pivot on one object relationship or one sharing model choice.
β Data modeling and Health Cloud objects
Health Cloud carries its own object model on top of standard Salesforce, and the exam will test whether you know when to use a Health Cloud object versus a standard or custom one. Patients, providers, care team members, and healthcare facilities each have designated representations, and picking the wrong one breaks downstream functionality. You need to understand how objects like Account, Contact, and the Health Cloud-specific clinical objects relate to each other, and how the data model shifts depending on whether you are working in a payer, provider, or life sciences context. Data migration sits alongside modeling here: a migration strategy must account for the legacy system's structure, the target Health Cloud schema, and the integrity checks that bridge the two. Candidates who treat migration as a simple data load consistently lose marks on items that probe what happens when legacy data does not map cleanly to Health Cloud objects.
β Vertical solutions and Health Cloud modules
Health Cloud is not one product: it packages capabilities differently for payers, providers, pharma, and other healthcare verticals. The exam tests whether you can match a customer's business context to the right vertical solution and then identify which Health Cloud modules support the required processes. A provider use case calls for different configuration choices than a payer one, even when the surface-level requirement sounds similar. You also need to know how to design future-state business processes, which means understanding the current process well enough to identify where Health Cloud adds value and where a gap exists. Items in this area present a business objective and ask you to select the design approach that best supports it. The strongest option aligns the module choice to the stated objective without over-engineering the solution.
β Security, compliance, and access control
Healthcare data carries regulatory weight, and the exam expects you to translate compliance requirements into Salesforce security design. Organizational security covers profiles, permission sets, and role hierarchies. Data access goes further: sharing rules, manual sharing, and the specific Health Cloud consent and data use management features all appear. The key skill is reading a scenario's compliance constraint and selecting the access model that satisfies it without over-restricting legitimate users. Candidates lose marks by defaulting to the most restrictive option when the scenario specifies a sharing requirement, or by ignoring Health Cloud's own consent framework in favor of generic Salesforce sharing tools.
β Integration, reporting, and KPIs
An optimal integration strategy depends on the external system, the data volume, the latency requirement, and whether Health Cloud has a purpose-built connector. The exam tests your ability to match those variables to the right Salesforce integration pattern. Real-time versus batch, REST versus SOAP, and the role of MuleSoft or Health Cloud's FHIR APIs are all fair territory. Reporting and KPIs are paired with integration because both depend on data flowing correctly into Salesforce. Defining success metrics means choosing the right Salesforce reporting objects and structures so that what the customer wants to measure is actually measurable. Items reward designs where the KPI is traceable from the data source through to the report, not designs that assume the data will be there.
How Design is tested
At 42%, Design will determine whether you pass. The items are scenario-heavy and often multi-layered: a single prompt may embed a compliance requirement, a data modeling decision, and a vertical context all at once. Items reward candidates who read the constraint before evaluating options. The most common trap is selecting a technically valid design that does not satisfy the specific requirement in the scenario. For example, a sharing model that works in a general Salesforce context may violate a Health Cloud consent requirement described in the scenario. Best-practices questions test whether you know Salesforce's recommended approach, not just a working one. Vertical-specific items require you to distinguish between what Health Cloud does for payers versus providers, so vague answers that could apply to any context will rarely be the strongest option. Expect some items to present two plausible designs and ask you to choose based on a single differentiating factor buried in the scenario.
With Design covering nearly half the exam, volume of practice matters. Working through a full question bank exposes the range of scenario types across all eleven sub-topics and shows you which design areas you are consistently missing before exam day.
The question below presents a Design scenario where a Health Cloud configuration choice must be justified against a specific customer requirement.
A customer is looking to implement Discovery Framework to manage their intake and clinical assessments.
Which three capabilities should a consultant configure with Health Cloud out-of-the-box to enhance their assessment functionality?
Choose 3 answers
Implement matches Design in weight, which tells you something important: knowing the right design is only half the job. You also need to know how to execute it inside Salesforce. Where Design tests your decisions, Implement tests your hands-on knowledge of Health Cloud configuration, OmniStudio components, security setup, and integration tooling. The scenarios here assume a design already exists and ask you to carry it through to a working system. Gaps in configuration knowledge that seemed abstract in Design become...
Implement matches Design in weight, which tells you something important: knowing the right design is only half the job. You also need to know how to execute it inside Salesforce. Where Design tests your decisions, Implement tests your hands-on knowledge of Health Cloud configuration, OmniStudio components, security setup, and integration tooling. The scenarios here assume a design already exists and ask you to carry it through to a working system. Gaps in configuration knowledge that seemed abstract in Design become concrete and costly here.
β Installation, configuration, and application setup
Health Cloud installation follows a specific sequence, and the exam tests whether you know what that sequence is and where deviations cause problems. Installing packages in the wrong order, skipping permission set assignments, or misconfiguring the Health Cloud app settings are all sources of exam items. Configuration questions go beyond installation: given a finalized design, you need to select the right configuration steps to activate the required Health Cloud application or solution. This includes knowing which settings live in Health Cloud Setup versus standard Salesforce Setup, and which configuration choices are reversible versus permanent. Items reward candidates who know the difference between enabling a feature and configuring it correctly for a specific use case.
β OmniStudio components
OmniStudio is central to Health Cloud's user experience layer, and the exam expects you to know its components well enough to configure them for a given design. OmniScripts, DataRaptors, Integration Procedures, and FlexCards each serve a distinct purpose, and items test whether you select the right component for the stated requirement. The trap is treating OmniStudio as interchangeable tooling: using a DataRaptor where an Integration Procedure is required, or building an OmniScript for a display task that belongs in a FlexCard, will cost you marks. You need to understand how OmniStudio components interact with Health Cloud data and processes, not just what each component does in isolation. Expect scenarios that describe a workflow or a user interaction and ask you to identify the correct OmniStudio approach.
β Security, sharing, and visibility configuration
Security in the Implement topic is about execution: given a design that specifies an access model, you need to know how to configure it. Profiles, permission sets, permission set groups, role hierarchies, sharing rules, and Health Cloud's own consent configuration all have specific setup paths. Items test whether you configure the right object for the right purpose. A common error is configuring object-level access when the scenario requires field-level security, or setting up a sharing rule when an ownership-based default would achieve the same result more cleanly. Health Cloud adds complexity here because some access controls are specific to its clinical data model and do not behave like standard Salesforce sharing.
β Integration capabilities and reporting configuration
On the implementation side, integration means knowing which Salesforce API or tool to configure for a given scenario, not just which one to choose in theory. Standard REST and SOAP APIs, Platform Events, and Health Cloud's FHIR R4 support all appear. Items test whether you can match a described integration scenario to the correct Salesforce capability and identify the configuration steps involved. Reporting configuration closes the loop: given a set of agreed success criteria, you need to know how to build the Salesforce reports and dashboards that surface them. Items reward candidates who understand the relationship between the data model and the report type, because a report built on the wrong object will not return the metrics the customer needs.
How Implement is tested
Implement and Design share the same weight, so the exam is balanced equally between knowing what to build and knowing how to build it. Items here are configuration-specific: a scenario will describe a finalized design and ask which steps, settings, or components achieve it. The strongest options are precise. Vague answers that describe a general approach without specifying the correct Salesforce mechanism will not score. OmniStudio items are particularly unforgiving because the component names are similar and the use cases overlap at the edges. Candidates who have only read about OmniStudio without working through configuration scenarios tend to confuse DataRaptors with Integration Procedures in multi-step workflows. Security and integration items reward candidates who know the configuration path, not just the concept. A common source of lost marks is selecting a valid Salesforce feature that does not match the specific Health Cloud context described in the scenario. Read for the Health Cloud-specific detail before committing to an option.
Timed practice under exam conditions is the most efficient way to find configuration knowledge gaps in a topic this broad. The ITExamsTopics practice test lets you work through Implement items at exam pace so weak areas surface through your score, not through guesswork.
The question below drops you into an Implement scenario requiring a specific Health Cloud configuration decision against a defined design.
After the weight of Design and Implement, Deploy is a smaller but precise finish line. At 5%, it will not make or break your result on its own, but candidates who ignore it often drop marks they did not need to lose. Deployment in Health Cloud involves ordered steps with real consequences: running them in the wrong sequence or skipping post-deployment validation can leave a production org in a broken state. The mobile capabilities sub-topic adds a distinct dimension that...
After the weight of Design and Implement, Deploy is a smaller but precise finish line. At 5%, it will not make or break your result on its own, but candidates who ignore it often drop marks they did not need to lose. Deployment in Health Cloud involves ordered steps with real consequences: running them in the wrong sequence or skipping post-deployment validation can leave a production org in a broken state. The mobile capabilities sub-topic adds a distinct dimension that the earlier topics do not cover.
How Deploy is tested
Deploy items are scenario-driven and sequence-sensitive. A prompt will describe a deployment situation and ask you to identify the correct pre-deployment or post-deployment action for that specific use case. The examinable skill is knowing what must happen before go-live versus what happens after, and why the order matters. Candidates lose marks by treating pre- and post-deployment steps as interchangeable, or by selecting a step that belongs to a different Health Cloud capability than the one described. The mobile management sub-topic tests a narrower but distinct area: knowing how technician management works through Salesforce's mobile capabilities, including which tasks are handled in the mobile app versus the desktop experience. Items here reward specificity. A general statement about deployment best practices will not outscore an answer that identifies the correct action for the scenario's stated capability. With only a small number of items expected from this topic, getting each one right matters proportionally more than it might seem.
Checking a small topic like Deploy with targeted practice questions is faster than re-reading documentation. The ITExamsTopics PDF lets you scan Deploy items specifically and confirm your coverage without working through the full bank again.
The question below tests a Deploy scenario where the sequence of steps and the specific Health Cloud capability both affect the answer.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full AP-211 Exam Questions π