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

（A）Contact Salesforce to enable Defer Sharing Rules

（B）Implement data archiving for old Shipment records.

（C）Configure shipment OWD to Public Read/Write.

（D）Contact Salesforce to create Skinny tables on Shipment.

（A）Will the data being archived need to be reported on or accessed in any way in the future?

（B）If reporting is necessary, can the information be aggregated into fewer, summary records?

（C）How many fields are defined on the custom objects that need to be archived?

（D）Which profiles and users currently have access to these custom object records?

（E）Are there any regulatory restrictions that will influence the archiving and purging plans?

（A）Custom metadata records are not copied from production to sandbox.

（B）Custom metadata records are editable in Apex.

（C）Custom metadata types are available for reporting.

（D）Custom metadata records are deployable using packages.

（A）Improve reporting performance by replacing the existing reports in Sales Cloud with new reports based on Analytics Cloud.

（B）Improve reporting performance by creating an Apex trigger for the Report object that will pre-fetch data before the report is run.

（C）Improve reporting performance by creating a dashboard that is scheduled to run the reports only once per day.

（D）Improve reporting performance by creating a custom Visualforce report that is using a cache of the records in the report.

（A）Whether the systems are cloud -based or on -premise.

（B）The number of systems that are integrating with each other.

（C）Whether the system of record changes for different tables.

（D）Whether or not Salesforce replaced a legacy CRM.

（A）Customers are created as Person Accounts and related to Business and Residential Accounts using the Account Contact relationship.

（B）Customer are created as individual objects and relate with Accounts for Business and Residence accounts.

（C）Costumers are created as Accounts for Residence Account and use Parent Account to relate Business Account.

（D）Customers are created as Contacts and related to Business and Residential Accounts using the Account Contact Relationships.

（A）SOAP API

（B）Bulk API

（C）Streaming API

（D）REST API

（A）Change opportunity amount field access to read only for sales users using field level security.

（B）Create a custom field for opportunity amount that PPS updates separating the field that sales user updates.

（C）Change PPS integration to update only opportunity amount fields when values is NULL.

（D）Create a custom field for opportunity amount that sales users update separating the fields that PPS updates.

（A）Salesforce does NOT allow more than four objects in a single report type.

（B）Salesforce does NOT support Orders or Order Line Items.

（C）Custom report types CANNOT contain Opportunity data.

（D）A report CANNOT contain data from Accounts and Contacts.

（A）Use cookies to track when visitors submit multiple forms.

（B）Ensure the website visitor is browsing using an HTTPS connection.

（C）Prefer picklist form fields over free text fields, where possible.

（D）Do client-side validation of phone number and email field formats.

（A）Ask SF support to increase the query timeout value.

（B）Use a custom auto number and formula field and use that to chunk records while extracting data.

（C）The REST API to extract data as it automatically chunks records by 200.

（D）Use ETL tool for extraction of records.

（A）Integrate Salesforce with the ERP environment.

（B）Utilize an MDM strategy to outline a single source of truth.

（C）Build synchronization reports and dashboards.

（D）Utilize workbench to update files within systems.

（A）Create one skinny table per report.

（B）Index key fields used in report criteria.

（C）Share each report with fewer users.

（D）Enable Divisions for large data objects.

（A）Enable " Set Audit Fields " and assign the permission to the user loading the data for the duration of the migration.

（B）Create a new field on the Contact object to capture the Created Date. Hide the standard Created Date field using Field -Level Security.

（C）After the data is migrated, perform an update on all records to set the original date in a standard Created Date field.

（D）Write an Apex trigger on the Contact object, before insert event to set the original value in a standard Created Date field.