QUESTION: 17

Lake Tahoe Bank, an existing Salesforce customer, is planning to implement Financial Services Cloud. Their Salesforce Admin is considering whether to use a new Salesforce org or upgrade the existing org.
Which three of the considerations below indicate that a new Salesforce org is the better choice9

The bank wants to use this project as an opportunity to retire customization
The current implementation is using a product-centric view and the bank wants to move to a customer-centric view.
Data migration is a big concern The current org has a large amount of data and the Bank wants to minimize data migration efforts.
The bank has limited redesign opportunities for business capabilities.
Existing business capabilities and processes can be redesigned to deliver a higher business impact

Answer(s): A,B,E

Explanation:

The following considerations indicate that a new Salesforce org is the better choice for implementing Financial Services Cloud:
The bank wants to use this project as an opportunity to retire customization. A new org will allow the bank to start fresh and avoid carrying over unnecessary or outdated customization that may conflict with Financial Services Cloud features or best practices. The current implementation is using a product-centric view and the bank wants to move to a customer-centric view. A new org will allow the bank to adopt the Financial Services Cloud data model, which is designed to provide a holistic view of the customer and their relationships, goals, financial accounts, activities, and interactions.
Existing business capabilities and processes can be redesigned to deliver a higher business impact. A new org will allow the bank to leverage the Financial Services Cloud capabilities, such as Action Plans, Relationship Groups, Rollup By Lookup, Service Processes, etc., to optimize their business processes and enhance their customer experience. Verified

Reference:

: Salesforce Help Article 6

Reveal Solution Next Question

QUESTION: 18

Lake Tahoe Bank is migrating customer records from the Individual Model to Person Accounts.
Which three steps should a Data Architect take to ensure a successful migration?

Ensure Person Accounts is enabled on the org
Configure your Person Account record types m the Indrvidual Record Type Mapper.
Enable 'Individual to Person Account Migration' in Custom Settings.
Use a CSV field to map PersonRecordTypeld to the Person Account RecoroTypeld and use Data Loader to update Client Records
Log a case with Salesforce to perform the conversion from the indrvkJual Model to Person Accounts.

Answer(s): A,B,D

Explanation:

The following steps are required to migrate customer records from the Individual Model to Person Accounts in Financial Services Cloud:
Ensure Person Accounts is enabled on the org. You need to have Person Accounts enabled before you can convert Individual Model records to Person Accounts. You can enable Person Accounts by contacting Salesforce Support or by using the Enable Person Accounts option in Setup > Account Settings.
Configure your Person Account record types in the Individual Record Type Mapper. You need to map your existing Individual Model record types to the corresponding Person Account record types. You can do this by using the Individual Record Type Mapper option in Setup > Financial Services Settings. Use a CSV file to map PersonRecordTypeId to the Person Account RecordTypeId and use Data Loader to update Client Records. You need to update the Client records with the correct PersonRecordTypeId value that matches the Person Account RecordTypeId value. You can do this by using a CSV file and Data Loader to perform a bulk update operation. Verified

Reference:

: Salesforce Help Article 1 :
Salesforce Help Article 2 : Salesforce Help Article 3

Reveal Solution Next Question

QUESTION: 19

Which two limitations should a Salesforce Administrator consider before enabling Person Accounts?

Person Accounts can be enabled and disabled only by contacting Salesforce Support
Person Accounts cannot be disabled once they were enabled
Creating a client record via Salesforce Inbox is not supported.
AppExchange packages will not work if Person Accounts are enabled

Answer(s): B,C

Explanation:

The following limitations should be considered before enabling Person Accounts in Financial Services Cloud:
Person Accounts cannot be disabled once they were enabled. Enabling Person Accounts is an irreversible action that affects your data model and user interface. You should carefully evaluate your business needs and test the functionality in a sandbox or developer org before enabling it in production.
Creating a client record via Salesforce Inbox is not supported. Salesforce Inbox is a feature that allows you to access Salesforce data and actions from your email application. However, you cannot use Salesforce Inbox to create a client record as a Person Account. You can only create a client record as an Individual Model record using Salesforce Inbox. Verified

Reference:

: Salesforce Help Article 4 :
Salesforce Help Article 5

Reveal Solution Next Question

QUESTION: 20

The Salesforce Admin wants to make it easier for call center agents to complete some common tasks by setting up flows and launch them from the Retail Banking Console.
What does the Admin have to keep in mind when setting up Flows?

Flows can be used to provide step-by-step guidance for address changes, without the need for then agent to navigate to different screens.
To open. edit, or create a Flow in Flow Builder, the user needs the Run Flows permission.
To use Financial Services Cloud Flows, you'll need the Financial Services Managed Package installed m the org and the Financial Services Cloud a permission set assigned to the user.
To use a Flow, a user must have access to the underlying object and its field

Answer(s): C

Reveal Solution Next Question

Free FINANCIAL-SERVICES-CLOUD Exam Braindumps (page: 6)

QUESTION: 17

Explanation:

Reference:

QUESTION: 18

Explanation:

Reference:

QUESTION: 19

Explanation:

Reference:

QUESTION: 20

FINANCIAL-SERVICES-CLOUD Exam Discussions & Posts