Data-Architect Practice Exam Questions Spring 2025 Page 9

Universal Containers (UC) requires 2 years of customer related cases to be available on SF for operational reporting. Any cases older than 2 years and upto 7 years need to be available on demand to the Service agents. UC creates 5 million cases per yr. Which 2 data archiving strategies should a data architect recommend? Choose 2 options:

A.

Use custom objects for cases older than 2 years and use nightly batch to move them.

B.

Sync cases older than 2 years to an external database, and provide access to Service agents to the database

C.

Use Big objects for cases older than 2 years, and use nightly batch to move them.

D.

Use Heroku and external objects to display cases older than 2 years and bulk API to hard delete from Salesforce.

C.

Use Big objects for cases older than 2 years, and use nightly batch to move them.

D.

Use Heroku and external objects to display cases older than 2 years and bulk API to hard delete from Salesforce.

Explanation:

✅ C. Use Big objects for cases older than 2 years, and use nightly batch to move them.
Big Objects are designed to handle massive amounts of data that do not need to be accessed frequently, which makes them ideal for storing historical data like cases older than 2 years. They support standard querying via SOQL with some limitations and are cost-effective for long-term storage. A nightly batch job ensures that eligible data is moved regularly.

✅ D. Use Heroku and external objects to display cases older than 2 years and bulk API to hard delete from Salesforce.
Heroku with external objects (via Salesforce Connect) is a good strategy for providing on-demand access to historical data that is stored outside Salesforce. This method maintains Salesforce data volume limits and performance, and Bulk API can be used to delete old records after they’ve been archived externally.

❌ A. Use custom objects for cases older than 2 years and use nightly batch to move them.
This increases storage usage in Salesforce and does not significantly reduce org size. It also lacks the querying performance benefits of Big Objects or external systems.

❌ B. Sync cases older than 2 years to an external database, and provide access to Service agents to the database
While viable in concept, this lacks seamless integration within the Salesforce UI. Service agents would need to leave Salesforce to access case data, which hurts productivity.

Universal Containers has two systems. Salesforce and an on -premise ERP system. An architect has been tasked with copying Opportunity records to the ERP once they reach a Closed/Won Stage. The Opportunity record in the ERP system will be read-only for all fields copied in from Salesforce. What is the optimal real-time approach that achieves this solution?

A.

Implement a Master Data Management system to determine system of record.

B.

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

C.

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

D.

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

B.

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

Explanation:

✅ B. Implement a workflow rule that sends Opportunity data through Outbound Messaging.
Outbound Messaging is a native point-and-click feature that supports real-time integration (or near real-time) without requiring Apex code. It’s ideal for one-way data transfers like copying Closed/Won Opportunities to a read-only ERP system.

❌ A. Implement a Master Data Management system
MDM is overkill for this use case. It adds unnecessary complexity when Salesforce is clearly the system of record for Opportunities.

❌ C. Have the ERP poll Salesforce nightly
Polling is not real-time and is resource inefficient. It can also miss near-term updates or cause synchronization delays.

❌ D. Implement an hourly integration
An hourly schedule is not considered "real-time". Outbound Messaging provides immediate updates, which is the core requirement here.

Universal Containers (UC) has a custom discount request object set as a detail object with a custom product object as the master. There is a requirement to allow the creation of generic discount requests without the custom product object as its master record. What solution should an Architect recommend to UC?

A.

Mandate the selection of a custom product for each discount request.

B.

Create a placeholder product record for the generic discount request.

C.

Remove the master-detail relationship and keep the objects separate.

D.

Change the master-detail relationship to a lookup relationship.

D.

Change the master-detail relationship to a lookup relationship.

Explanation:

✅ D. Change the master-detail relationship to a lookup relationship.
Master-detail relationships require the detail record to have a parent. To allow creation of standalone discount requests, a lookup relationship is appropriate. It allows flexibility—linking to a custom product when applicable and remaining unlinked otherwise.

❌ A. Mandate the selection of a custom product
This violates the requirement for "generic" discount requests which must exist without a product.

❌ B. Create a placeholder product record
This is a workaround and introduces unnecessary data just to satisfy a structural constraint.

❌ C. Remove the master-detail relationship and keep the objects separate
This breaks the existing data model. A lookup allows partial detachment without redesigning object relationships completely.

Universal Containers wants to develop a dashboard in Salesforce that will allow Sales Managers to do data exploration using their mobile device (i.e., drill down into sales-related data) and have the possibility of adding ad-hoc filters while on the move. What is a recommended solution for building data exploration dashboards in Salesforce?

A.

Create a Dashboard in an external reporting tool, export data to the tool, and add link to the dashboard in Salesforce.

B.

Create a Dashboard in an external reporting tool, export data to the tool, and embed the dashboard in Salesforce using the Canval toolkit.

C.

Create a standard Salesforce Dashboard and connect it to reports with the appropriate filters.

D.

Create a Dashboard using Analytics Cloud that will allow the user to create ad-hoc lenses and drill down.

D.

Create a Dashboard using Analytics Cloud that will allow the user to create ad-hoc lenses and drill down.

Explanation:

✅ D. Create a Dashboard using Analytics Cloud
Analytics Cloud (Tableau CRM) offers advanced features like mobile-optimized dashboards, drill-downs, ad-hoc filters, and interactive lenses. It is purpose-built for data exploration and supports offline capabilities.

❌ A & B. Use external reporting tools
These approaches involve data duplication, security management, and external logins. Not ideal for ad-hoc, mobile-first interaction.

❌ C. Standard Salesforce Dashboard
Standard dashboards are limited in interactivity and filtering on mobile. They are better for static reporting than exploration.

Universal Container has implemented Sales Cloud to manage patient and related health records. During a recent security audit of the system it was discovered that same standard and custom fields need to encrypted. Which solution should a data architect recommend to encrypt existing fields?

A.

Use Apex Crypto Class encrypt customer and standard fields.

B.

Implement classic encryption to encrypt custom and standard fields.

C.

Implement shield platform encryption to encrypt and standard fields

D.

Expert data out of Salesforce and encrypt custom and standard fields.

C.

Implement shield platform encryption to encrypt and standard fields

Explanation:

✅ C. Implement Shield Platform Encryption
Shield Platform Encryption is designed for encrypting both standard and custom fields at rest. It works natively in Salesforce and supports compliance needs like HIPAA and GDPR.

❌ A. Apex Crypto Class
Not usable on standard fields and not integrated with the Salesforce platform security model.

❌ B. Classic Encryption
Limited to custom text fields and lacks flexibility or compatibility with modern Salesforce features.

❌ D. Export and encrypt
This approach is insecure, breaks platform trust, and is not real-time. It doesn’t protect data in Salesforce.

As part of a phased Salesforce rollout. there will be 3 deployments spread out over the year. The requirements have been carefully documented. Which two methods should an architect use to trace back configuration changes to the detailed requirements? Choose 2 answers

A.

Review the setup audit trail for configuration changes.

B.

Put the business purpose in the Description of each field.

C.

Maintain a data dictionary with the justification for each field.

D.

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

B.

Put the business purpose in the Description of each field.

C.

Maintain a data dictionary with the justification for each field.

Explanation:

✅ B (Field Descriptions): Documents business purpose directly in setup metadata (visible to admins).

✅ C (Data Dictionary): External tracker maps fields to requirements/justifications.

❌ A: Audit trails log changes but not reasons.

❌ D: Source control tracks code, not business context.

A large automobile manufacturer has decided to use Salesforce as its CRM. It needs to maintain the following dealer types in their CRM:
Local dealers
Regional distributor
State distributor
Service dealer
The attributes are different for each of the customer types. The CRM users should be allowed to enter only attributes related to the customer types. The processes and business rules for each of the customer types could be different. How should the different dealers be maintained in Salesforce?

A.

Use Accounts for dealers, and create record types for each of the dealer types.

B.

Create dealers as Accounts, and build custom views for each of the dealer types.

C.

Use Accounts for dealers and custom picklist field for each of the dealer types

D.

Create Custom objects for each dealer types and custom fields for dealer attributes.

A.

Use Accounts for dealers, and create record types for each of the dealer types.

Explanation:

✅ A. Use Accounts with record types for each dealer type
This allows shared functionality across dealers while enabling customization (layouts, picklists, processes) per dealer type. It supports reporting, security, and automation out of the box.

❌ B. Custom views only
This limits extensibility—can’t change page layout, validation rules, or automation per dealer type.

❌ C. Picklist for type
Insufficient flexibility. A picklist does not support layout or process differentiation like record types.

❌ D. Custom objects per dealer
Overkill. This creates redundant structures and complicates reporting and maintenance.

Which API should a data architect use if exporting 1million records from Salesforce?

A.

Bulk API

B.

REST API

C.

Streaming API

D.

SOAP API

A.

Bulk API

Explanation:

✅ A. Bulk API
Designed for handling large data volumes. It allows batching, is optimized for speed, and minimizes governor limits, making it the best tool for exporting millions of records.

❌ B. REST API
Not optimized for large volumes. Record limits and rate limits make it inefficient for 1M+ records.

❌ C. Streaming API
Used for event notifications, not data export.

❌ D. SOAP API
Slower and subject to strict limits. Not ideal for high-volume data operations.

Universal Containers has successfully migrated 50 million records into five different objects multiple times in a full copy sandbox. The Integration Engineer wants to re-run the test again a month before it goes live into Production. What is the recommended approach to re-run the test?

A.

Truncate all 5 objects quickly and re-run the data migration test.

B.

Refresh the full copy sandbox and re-run the data migration test.

C.

Hard delete all 5 objects’ data and re-run the data migration test.

D.

Truncate all 5 objects and hard delete before running the migration test.

B.

Refresh the full copy sandbox and re-run the data migration test.

Explanation:

Refreshing the sandbox:
1. Resets to a clean production copy
2. Automates data purge (avoids manual deletion limits)
3. Tests against current org state

Rejected Options:

❌ A/C/D: Manual deletion risks partial data or governor limits.

Universal Containers is creating a new B2C service offering for consumers to ship goods across continents. This is in addition to their well-established B2B offering. Their current Salesforce org uses the standard Account object to track B2B customers. They are expecting to have over 50,000,000 consumers over the next five years across their 50 business regions. B2C customers will be individuals. Household data is not required to be stored. What is the recommended data model for consumer account data to be stored in Salesforce?

A.

Use the Account object with Person Accounts and a new B2C page layout.

B.

Use the Account object with a newly created Record Type for B2C customers.

C.

Create a new picklist value for B2C customers on the Account Type field.

D.

Use 50 umbrella Accounts for each region, with customers as associated Contacts.

A.

Use the Account object with Person Accounts and a new B2C page layout.

Explanation:

✅ A. Use Person Accounts with a B2C layout
Person Accounts are built for individual customers and are scalable to tens of millions. With appropriate indexing and partitioning, they suit B2C use cases where the "Contact is the Account".

❌ B. New Record Type on Account
Does not allow individual-centric data model. Not suitable for representing consumers as standalone entities.

❌ C. Picklist field
Too limited and doesn’t provide layout/process/data separation for B2C.

❌ D. Umbrella Accounts + Contacts
Artificial hierarchy and not scalable. This breaks Salesforce’s conceptual model and complicates sharing/reporting.

Data-Architect Practice Test Questions