Correct Answer: A

Explanation: According to the Salesforce documentation2, Health Cloud uses Business APIs that should be used instead of object level APIs when creating records in Health Cloud objects. Business APIs are custom REST APIs that perform complex business logic and validations on Health Cloud objects. Object level APIs are standard REST or SOAP APIs that performCRUD operations on individual objects. Business APIs ensure data integrity and consistency across Health Cloud objects, while object level APIs may result in data errorsor inconsistencies2.

Correct Answer: B

Explanation: The individual Data Model may be used to represent members ......(B) is the recommended approach to represent members and patients during the implementation by Patient Managers as per the Salesforce recommendation. Leveraging Person Accounts is not the recommended approach to .........(A), as Person Accounts are used to represent providers, not members or patients. Salesforce does not recommend using Member Accounts to represent members ......? as Member Accounts are used to represent payer organizations, not members or patients. Leveraging Candidate Accounts are not the recommended approach to .........(D), as Candidate Accounts are used to represent potential members or patients, not existing ones.

Correct Answer: B

Actionable Relationship Center can help Bloomington Caregivers to easily view all of the complex associations between patients, personal relationships, healthcare practitioners, other people, and organizations inhealthcare. Actionable Relationship Center displays a graphical representation of the relationships between the record and other records in Health Cloud, such as Account, Contact, Care Team Member, Referral, and Care Plan. Users can also perform actions onthe related records, such as creating tasks, sending messages, or updating fields.

Correct Answer: D

Explanation: To help streamline caller authentication for Contact Center agents, a consultant should recommend Bloomington Caregivers use the Identity Verification Flow Templates feature in Health Cloud. This feature allows agents to launch a flow from the utility bar or a record page to verify a caller's identity before processing their requests involving sensitive information. The flowprompts the agent to search for the caller in Health Cloud, select a reason for the call, ask verification questions based on predefined rules, and capture engagement details8. Customer Identity OmniScript Templates, Reusable Verification FlexCards, or Verify Customer Identity Process Flow are not features that exist in Health Cloud.

Correct Answer: BCD

Explanation: Install HC managed package (B), verify that chatter is enabled ? and configure the console view (D) are three steps required to configure HC. Install HC unmanaged Package (A) is not a valid step, as there is no unmanaged package for HC. Enable the options for contact to related with multiple accounts (E) is not a required step, as it is only needed if using Contacts instead of Person Accounts.