Certified-Data-Architecture-and-Management-Designer Certified Data Architecture and Management Designer

Loading demo links...

Showing 13–15 of 15 questions

Question 13

Universal Containers (UC) is in the process of migrating lagacy inventory data from an enterprise resources planning (ERP) system into Sales Cloud with the following requirements:

Legacy inventory data will be stored in a custom child objects called Inventory_c.

Inventory data should be related to the standard Account object.

The Inventory_c object should Inhent the same sharing rules as the Account object.

Anytime an Account record is deleted in Salesforce, the related Inventory_c record(s) should be deleted as well.

What type of relationship field should a data architect recommend in this scenario?

Select an option, then click Submit answer.

  • Master-detail relationship filed on Account, related to Inventory_c

  • Master-detail relationship filed on Inventory_c, related to Account

  • Indirect lookup relationship field on Account, related to Inventory_c

  • Lookup relationship fields on Inventory related to Account


Question 14

Universal Containers (UC) has several custom Visualforce applications have been developed in which users are able to edit Opportunity records. UC struggles with data completeness on their Opportunity records and has decided to make certain fields required that have not been in the past. The newly required fields are dependent on the Stage of the Opportunity, such that certain fields are only required once an Opportunity advances to later stages. There are two fields. What is the simplest approach to handle this new requirement?

Select an option, then click Submit answer.

  • Update the Opportunity page layout to mark these fields as required.

  • Use a validation rule for each field that takes the Stage into consideration.

  • Update these Opportunity field definitions in Setup to be required.

  • Write an Apex trigger that checks each field when records are saved.


Question 15

Universal Containers (UC) uses Salesforce for tracking opportunities (Opportunity). UC uses an internal ERP system for tracking deliveries and invoicing. The ERP system supports SOAP API and OData for bi-directional integration between Salesforce and the ERP system. UC has about one million opportunities. For each opportunity, UC sends 12 invoices, one per month. UC sales reps have requirements to view current invoice status and invoice amount from the opportunity page. When creating an object to model invoices, what should the architect recommend, considering performance and data storage space?

Select an option, then click Submit answer.

  • Use Streaming API to get the current status from the ERP and display on the Opportunity page.

  • Create an external object Invoice _x with a Lookup relationship with Opportunity.

  • Create a custom object Invoice _c with a master -detail relationship with Opportunity.

  • Create a custom object Invoice _c with a Lookup relationship with Opportunity.