Data-Architect 無料問題集「Salesforce Certified Data Architect」

（A）Patients as Accounts, Payment providers as Accounts, & Doctors as Person Accounts

（B）Patients as Person Accounts, Payment providers as Accounts, & Doctors as Person Account

（C）Patients as Person Accounts, Payment providers as Accounts, & Doctors as Contacts

（D）Patients as Contacts, Payment providers as Accounts, & Doctors as Accounts

（A）Select Clear the value of this field option while configuring the lookup relationship.

（B）Change the lookup relationship to master-detail relationship.

（C）Create a custom object to maintain the relationship between products and customers.

（D）Create multiple similar products and distribute the skew across those products.

（A）Change integration to let product master systems update product data directly in Salesforce via the Salesforce API.

（B）Build Apex Triggers in Salesforce that ensure products have the correct names and labels after data is loaded into salesforce.

（C）Add custom fields to the Product standard object in Salesforce to store data from the different source systems.

（D）Define a data taxonomy for product data and apply the taxonomy to the product data in the data warehouse.

（A）Encrypt Sensitive Customer information maintained in SF.

（B）Prevent Sales users access to customer PII information

（C）Event monitoring to monitor all user activities

（D）Transaction security policies to prevent export of SF Data.

（E）Restrict access to SF from users outside specific geography

（A）Use custom big objects to maintain Sales Orders in Salesforce.

（B）Use external objects to maintain Sales Order in Salesforce.

（C）Us custom objects to maintain Sales Orders in Salesforce.

（D）Use Standard order object to maintain Sale Orders in Salesforce

（A）Use Metadata API to create big object.

（B）Go to Object Manager in setup and select new to create big object.

（C）Go to Big Object in setup select new to create big object.

（D）Use DX to create big object.

（A）The Opportunity engagement system should become the system of record for Opportunity records.

（B）Stakeholders should be brought together to discuss the appropriate data strategy moving forward.

（C）A policy should be adopted so that the system whose record was most recently updated should prevail in conflicts.

（D）The MDM strategy defines Salesforce as the system of record, so Salesforce Opportunity values prevail in all conflicts.

（A）Use metadata API, to extract field attribute information and use the extract to classify and build reports

（B）Create a custom object and field to capture necessary compliance information and build custom reports.

（C）Build reports for field information, then export the information to classify and report for Audits.

（D）Use field metadata attributes for compliance categorization, data owner, and data sensitivity level.

（A）A performance test plan must be created and submitted to Salesforce customer support.

（B）Application performance benchmarked in a sandbox can also be expected in production.

（C）Applications with highly customized code or large volumes should be performance tested.

（D）All Force.com applications must be performance tested in a sandbox as well as production.

（A）Review the time zones of the User loading the data.

（B）Defer sharing calculations of the Salesforce Org.

（C）Determine if the legacy system is still in use.

（D）Deactivate approval processes and workflow rules.

（E）Remove custom indexes on the data being loaded.

（A）Identify the recovery point objective.

（B）Identify the data retention requirements

（C）Identify how the archive data will be accessed and used.

（D）Identify the recovery time objective.

（A）Leverage mashup to display historical records in Salesforce.

（B）Leverage real-time integration to pull records into Salesforce.

（C）Bring all data Salesforce, and delete it after a year.

（D）Build a chair solution to go the legacy system and display records.

（A）Einstein Analytics

（B）AppExchange Apps

（C）Weekly Snapshots

（D）Setup Audit Trails

（A）Set up staging data base, and define external IDs to merge, clean duplicate data, and load into Salesforce.

（B）Define external IDs for an object, Insert data from one database, and use upsert for a second database

（C）Define external IDs for an object, migrate second database to first database, and load into Salesforce.

（D）Define duplicate rules in Salesforce, and load data into Salesforce from both databases.

（A）SOAP API

（B）Bulk API

（C）Streaming API

（D）REST API

（A）Assign dummy user to highest role in role hierarchy

（B）Create multiple dummy user and assign leads to them

（C）Periodically delete leads to reduce number of leads

（D）Assign dummy user last role in role hierarchy

（A）Enable Defer Sharing Calculation prior to making sharing rule changes.

（B）Delete old sharing rules and build new sharing rules

（C）Log a case with salesforce to make sharing rule changes.

（D）Log out all users and make changes to sharing rules.

（A）Have the ERP poll Salesforce nightly and bring in the desired Opportunities.

（B）Implement an hourly integration to send Salesforce Opportunities to the ERP system.

（C）Implement a workflow rule that sends Opportunity data through Outbound Messaging.

（D）Implement a Master Data Management system to determine system of record.

（A）Use the Force.com IDE to save the metadata files in source control.

（B）Maintain a data dictionary with the justification for each field.

（C）Review the setup audit trail for configuration changes.

（D）Put the business purpose in the Description of each field.