Data-Architect Exam Dumps : Salesforce Certified Platform Data Architect (Plat-Arch-201)

Creating an account plan object with a lookup relationship to Account with validation rules to enforce the Account association can help UC meet their requirement. A lookup relationship allows different accessibility requirements for the account plan object and the account object, as well as different ownership and sharing settings. A validation rule can ensure that each account plan has an account associated with it.

According to the exam guide, one of the objectives is to "describe the use cases and considerations for using AppExchange apps and Wave Analytics"1. This implies that options A and B are both valid approaches to provide more analytical insights. Option C is not correct because weekly snapshots are used to track changes over time, not to provide advanced analytics3. Option D is not correct because setup audit trails are used to monitor changes in the setup menu, not to provide analytical insights.

The three considerations needed prior to a SF Connect implementation are to develop an object relationship strategy, identify the external tables to sync into external objects, and assess whether the external data source is reachable via an ODATA endpoint. SF Connect is a feature that allows integrating external data sources with Salesforce using external objects. External objects are similar to custom objects, but they store metadata only and not data. They enable on-demand access to external data via standard Salesforce APIs and user interfaces. To implement SF Connect, a data architect needs to consider how the external objects will relate to other objects in Salesforce, which external tables will be exposed as external objects, and whether the external data source supports ODATA protocol for data access.