DreamHouse Realty has a legacy system that captures Branch Offices and Transactions. DreamHouse Realty has 15 Branch Offices. Transactions can relate to any Branch Office. DreamHouse Realty has created hundreds of thousands of Transactions per year.
A Data Architect needs to denormalize this data model into a single Transaction object with a Branch Office picklist.
What are two important considerations for the Data Architect in this scenario? (Choose two.)

• A.Limitations on Org data storage.
• B.Limitations on master-detail relationships.
• C.Bulk API limitations on picklist fields.
• D.Standard list view in-line editing.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers has a requirement to store more than 100 million records in salesforce and needs to create a custom big object to support this business requirement.
Which two tools should a data architect use to build custom object?

• A.Use Metadata API to create big object.
• B.Go to Big Object In setup select new to create big object.
• C.Go to Object manager In setup and select new to create big object.
• D.Use DX to create big object.

Comment: *

Name: *

Email: *

Verification: *

A customer is operating in a highly reputated industry and is planning to implement SF. The customer information maintained in SF, includes the following:
Personally, identifiable information (PII)
IP restrictions on profiles organized by Geographic location
Financial records that need to be private and accessible only by the assigned Sales associate.
User should not be allowed to export information from Salesforce.
Enterprise security has mandate access to be restricted to users within a specific geography and detail monitoring of user activity. Which 3 Salesforce shield capabilities should a data architect recommend? Choose 3 answers:

• A.Prevent Sales users access to customer PII information
• B.Event monitoring to monitor all user activities
• C.Transaction security policies to prevent export of SF Data.
• D.Restrict access to SF from users outside specific geography
• E.Encrypt Sensitive Customer information maintained in SF.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) has a multi-level master-detail relationship for opportunities, a custom opportunity line item object, and a custom discount request. UC has opportunity as master and custom line item object as detail in master-detail relationship. UC also has a custom line item object as master and a custom discount request object as detail in another master-detail relationship. UC has a requirement to show all sums of discounts across line items at an opportunity level. What is the recommended solution to address these requirements?

• A.Remove the master-detail relationships and rely completely on workflow/triggers to summarize the discount amount.
• B.Update the master-detail relationships to lookup relationships in order to allow the discount amount to roll up.
• C.Roll-up discount request amount at the line-item-level and line-item-level summary discount at the opportunity level.
• D.Use roll-up for the line-item-level summary and a trigger for the opportunity amount summary, as only one level roll-up is allowed.

Comment: *

Name: *

Email: *

Verification: *

Every year, Ursa Major Solar has more than 1 million orders. Each order contains an average of 10 line items.
The Chief Executive Officer (CEO) needs the Sales Reps to see how much money each customer generates year-over-year. However, data storage is running low in Salesforce.
Which approach for data archiving is appropriate for this scenario?

• A.1. Annually delete orders and order line items. 2. Ensure the customer has order information in another system.
• B.1. Annually export and delete order line items. 2. Store them in a zip file in case the data is needed later.
• C.1. Annually aggregate order amount data to store in a custom object. 2. Delete those orders and order line items.
• D.1. Annually export and delete orders and order line items. 2. Store them in a zip file in case the data is needed later.

Comment: *

Name: *

Email: *

Verification: *