In their legacy system. Universal Containers has a monthly accounts receivable report that compiles data from Accounts, Contacts, Opportunities, Orders. and Order Line Items. What difficulty will an architect run into when implementing this in Salesforce?

• A.Salesforce allows up to four objects in a single report type.
• B.Custom report types cannot contain Opportunity data.
• C.A report cannot contain data from Accounts and Contacts.
• D.Salesforce does not support Orders or Order Line Items.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) loads bulk leads and campaigns from third-party lead aggregators on a weekly and monthly basis. The expected lead record volume is 500K records per week, and the expected campaign records volume is 10K campaigns per week. After the upload, Lead records are shared with various sales agents via sharing rules and added as Campaign members via Apex triggers on Lead creation. UC agents work on leads for 6 months, but want to keep the records in the system for at least 1 year for reference. Compliance requires them to be stored for a minimum of 3 years. After that, data can be deleted. What statement is true with respect to a data archiving strategy for UC?

• A.UC can store long-term lead records in custom storage objects to avoid counting against storage limits.
• B.UC can leverage recycle bin capability, which guarantees record storage for 15 days after deletion.
• C.UC can leverage a "tier"-based approach to classify the record storage need.
• D.UC can leverage the Salesforce Data Backup and Recovery feature for data archival needs.

Comment: *

Name: *

Email: *

Verification: *

DreamHouse Realty has a data model as shown in the image. The Project object has a private sharing model, and it has Roll-Up summary fields to calculate the number of resources assigned to the project, total hours for the project, and the number of work items associated to the project.
There will be a large amount of time entry records to be loaded regularly from an external system into Salesforce.

What should the Architect consider in this situation?

• A.Calculate summary values instead of Roll-Up by using triggers.
• B.Calculate summary values instead of Roll-Up by using workflow.
• C.Load all data after deferring sharing calculations.
• D.Load all data using external IDs to link to parent records.

Comment: *

Name: *

Email: *

Verification: *

Northern Trail Outfitters (NTO) has the following systems:
Customer master-source of truth for customer information
Service cloud-customer support
Marketing cloud-marketing support
Enterprise data warehouse-business reporting
The customer data is duplicated across all these system and are not kept in sync. Customers are also complaining that they get repeated marketing emails and have to call into update their information.
NTO is planning to implement master data management (MDM) solution across the enterprise.
Which three data will an MDM tool solve?
Choose 3 answers

• A.Data loss and recovery
• B.Data standardization
• C.Data accuracy and quality
• D.Data completeness
• E.Data duplication

Comment: *

Name: *

Email: *

Verification: *

Northern Trail Outfitters (NTO) has outgrown its current Salesforce org and will be migrating to a new org shortly. As part of this process, NTO will be migrating all of its metadata and data. NTO's data model in the source org has a complex relationship hierarchy with several master-detail and lookup relationships across objects, which should be maintained in the target org.
Which three things should a data architect do to maintain the relationship hierarchy during migration? (Choose three.)

• A.Use data loader to export the data from the source org and then import/upsert into the target org in sequential order.
• B.Redefine the master-detail relationship fields to lookup relationship fields in the target org.
• C.Create an external ID field for each object in the target org and map source record IDs to this field.
• D.Keep the relationship fields populated with the source record IDs in the import file.
• E.Replace source record IDs with new record IDs from the target org in the import file.

Comment: *

Name: *

Email: *

Verification: *