Data-Architect Practice Exam Questions Spring 2025 Page 11

UC has to built a B2C ecommerce site on Heroku that shares customer and order data with a Heroku Postgres database. UC is currently utilizing Postgres as the single source of truth for both customers and orders. UC has asked a data architect to replicate the data into salesforce so that salesforce can now act as the system of record. What are the 3 considerations that data architect should weigh before implementing this requirement? Choose 3 answers:

A.

Consider whether the data is required for sales reports, dashboards and KPI’s.

B.

Determine if the data is driver of key process implemented within salesforce.

C.

Ensure there is a tight relationship between order data and an enterprise resource plaining (ERP) application.

D.

Ensure the data is CRM center and able to populate standard of custom objects.

E.

A selection of the tool required to replicate the data.

F.

– Heroku Connect is required but this is confusing

A.

Consider whether the data is required for sales reports, dashboards and KPI’s.

B.

Determine if the data is driver of key process implemented within salesforce.

D.

Ensure the data is CRM center and able to populate standard of custom objects.

Explanation:

✅ A. Consider whether the data is required for sales reports, dashboards, and KPIs.
If Salesforce is to become the system of record, data must be accessible for reporting and analytics within Salesforce. This helps determine whether data should reside natively or be exposed externally.

✅ B. Determine if the data is a driver of key processes implemented within Salesforce.
Data used to trigger automation (flows, triggers, approvals) must be present within Salesforce. If customer or order data drives core CRM processes, full replication becomes necessary.

✅ D. Ensure the data is CRM-centric and able to populate standard or custom objects.
Salesforce excels when data is aligned to its data model (accounts, contacts, orders, etc.). Mapping to proper standard/custom objects ensures the platform can function optimally.

❌ C. Tight ERP relationship – While important, it’s unrelated to the core Salesforce data replication goal.

❌ E. Tool selection – A valid concern, but more of an implementation detail than a primary architectural consideration.

❌ F. Vague/confusing statement – Not a valid answer choice.

Universal Containers (UC) is transitioning from Classic to Lightning Experience. What does UC need to do to ensure users have access to its notices and attachments in Lightning Experience?

A.

Add Notes and Attachments Related List to page Layout in Lighting Experience.

B.

Manually upload Notes in Lighting Experience.

C.

Migrate Notes and Attachment to Enhanced Notes and Files a migration tool

D.

Manually upload Attachments in Lighting Experience.

C.

Migrate Notes and Attachment to Enhanced Notes and Files a migration tool

Explanation:

✅ C. Migrate Notes and Attachments to Enhanced Notes and Files using a migration tool
Lightning Experience does not natively support the legacy "Notes and Attachments" component. Data should be migrated to Enhanced Notes and Files using tools like the Salesforce-provided migration utility to ensure visibility and usability in Lightning.

❌ A. Add Related List – Doesn’t make legacy notes/files visible in Lightning.

❌ B & D. Manual uploads – Not scalable and error-prone for existing data.

North Trail Outfitters (NTD) is in the process of evaluating big objects to store large amounts of asset data from an external system. NTO will need to report on this asset data weekly. Which two native tools should a data architect recommend to achieve this reporting requirement?

A.

Standard reports and dashboards

B.

Async SOQL with a custom object

C.

Standard SOQL queries

D.

Einstein Analytics

B.

Async SOQL with a custom object

D.

Einstein Analytics

Explanation:

✅ B. Async SOQL with a custom object
Big Objects are queried using Async SOQL, not regular SOQL, especially for large datasets. This allows scheduled and batched access for processing or syncing to reporting objects.

✅ D. Einstein Analytics
Big Objects integrate with Einstein Analytics for advanced dashboards and analytics, making it ideal for weekly reporting.

❌ A. Standard Reports – Not supported on Big Objects.

❌ C. Standard SOQL – Doesn’t work on Big Objects due to indexing and limits.

A customer wants to maintain geographic location information including latitude and longitude in a custom object. What would a data architect recommend to satisfy this requirement?

A.

Create formula fields with geolocation function for this requirement.

B.

Create custom fields to maintain latitude and longitude information

C.

Create a geolocation custom field to maintain this requirement

D.

Recommend app exchange packages to support this requirement.

C.

Create a geolocation custom field to maintain this requirement

Explanation:

✅ C. Create a geolocation custom field
Salesforce provides native Geolocation field types that store latitude and longitude in a single field and allow proximity searches and mapping functionality. Best practice for location data.

❌ A. Formula fields – Can’t store actual location values.

❌ B. Separate fields – Workable but not as efficient or queryable.

❌ D. AppExchange – Unnecessary when native functionality is available.

What makes Skinny tables fast? Choose three answers.

A.

They do not include soft-deleted records

B.

They avoid resource intensive joins

C.

Their tables are kept in sync with their source tables when the source tables are modified

D.

They can contain fields from other objects

E.

They support up to a max of 100 of columns

A.

They do not include soft-deleted records

B.

They avoid resource intensive joins

C.

Their tables are kept in sync with their source tables when the source tables are modified

Explanation:

✅ A. They do not include soft-deleted records – Helps reduce the volume of data for performance gains.

✅ B. They avoid resource-intensive joins – Skinny tables denormalize data, reducing complex queries.

✅ C. Kept in sync with source tables – Salesforce ensures skinny tables are updated with changes, keeping them reliable.

❌ D. Contain fields from other objects – False. Skinny tables can only include fields from the same object.

❌ E. Max of 100 columns – The limit is actually 100 fields but not a core reason they are "fast".

Universal Containers (UC) has multi -level account hierarchies that represent departments within their major Accounts. Users are creating duplicate Contacts across multiple departments. UC wants to clean the data so as to have a single Contact across departments. What two solutions should UC implement to cleanse their data? Choose 2 answers

A.

Make use of a third -party tool to help merge duplicate Contacts across Accounts.

B.

Use Data.com to standardize Contact address information to help identify duplicates.

C.

Use Workflow rules to standardize Contact information to identify and prevent duplicates.

D.

Make use of the Merge Contacts feature of Salesforce to merge duplicates for an Account.

A.

Make use of a third -party tool to help merge duplicate Contacts across Accounts.

B.

Use Data.com to standardize Contact address information to help identify duplicates.

Explanation:

✅ A. Use a third-party deduplication tool – These tools are essential for cross-account duplicate detection and merging, as native Salesforce deduplication is limited to within a single account.

✅ B. Use Data.com (or Data Integration Service) – Helps standardize data, which is essential before deduplication processes begin.

❌ C. Workflow rules for standardization – Not effective or scalable for cleansing data.

❌ D. Merge Contacts feature – Only merges within an account, not across multiple accounts.

Universal containers is implementing Salesforce lead management. UC Procure lead data from multiple sources and would like to make sure lead data as company profile and location information. Which solution should a data architect recommend to make sure lead data has both profile and location information?

A.

Ask sales people to search for populating company profile and location data

B.

Run reports to identify records which does not have company profile and location dat

C.

Leverage external data providers populate company profile and location data

D.

Export data out of Salesforce and send to another team to populate company profile and location data

C.

Leverage external data providers populate company profile and location data

Explanation:

✅ C. Leverage external data providers
Using third-party data enrichment providers is the most scalable and accurate way to append company profiles and locations to leads from multiple sources, reducing manual effort and improving data quality.

❌ A. Ask salespeople – Manual entry is inefficient and prone to error.

❌ B. Reports – Reactive, not proactive; doesn’t improve data quality directly.

❌ D. Export and populate externally – Slow and disconnected from Salesforce.

Universal Containers has a custom object with millions of rows of data. When executing SOQL queries, which three options prevent a query from being selective? (Choose three.)

A.

Using leading % wildcards.

B.

Using trailing % wildcards.

C.

Performing large loads and deletions.

D.

Using NOT and != operators.

E.

Using a custom index on a deterministic formula field.

A.

Using leading % wildcards.

D.

Using NOT and != operators.

E.

Using a custom index on a deterministic formula field.

Explanation:

✅ A. Leading % wildcards – Prevent indexed field usage, making queries non-selective.

✅ D. Using NOT or != operators – Bypass indexes and require full scans.

✅ E. Custom index on a deterministic formula – While deterministic formulas can be indexed, they still may not be selective depending on how they're used.

❌ B. Trailing wildcards – Still allows index usage (LIKE 'value%' is optimized).

❌ C. Loads/deletions – Can impact performance but don’t directly make a query non-selective.

Northern Trail Outfitters (NTO) has implemented Salesforce for its sales users. The opportunity management in Saiesforce Is implemented as follows:
1. Sales users enter their opportunities in Salesforce for forecasting and reporting purposes.
2. NTO has a product pricing system (PPS) that is used to update the Opportunity Amount field on opportunities on a daily basis.
3. PPS is the trusted source within NTO for Opportunity Amount.
4. NTO uses Opportunity Forecast for its sales planning and management.
Sales users have noticed that their updates to the Opportunity Amount field are overwritten when PPS updates their opportunities. How should a data architect address this overwriting issue?

A.

Create a custom field for Opportunity amount that PSS updates separating the field sales user updates.

B.

Change PSS integration to update only Opportunity Amount field when the value is null.

C.

Change Opportunity Amount field access to Read Only for sales users field-level security.

D.

Create a custom field for Opportunity amount that sales users update separating the field that PPS updates.

D.

Create a custom field for Opportunity amount that sales users update separating the field that PPS updates.

Explanation:

✅ D. Create a custom field for Opportunity amount that sales users update
Separating user-entered values from system-updated values is a best practice when integrating with external systems. Sales reps can enter values in one field, while PPS can control another, avoiding overwrites and enabling auditability.

❌ A. PPS gets a custom field – Not optimal because PPS is the trusted source, it should own the standard field.

❌ B. Only update if null – Not reliable or sustainable.

❌ C. Read-only for reps – Removes sales users’ ability to forecast or adjust amounts, defeating usability.

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.

Event monitoring to monitor all user activities

B.

Restrict access to SF from users outside specific geography

C.

Prevent Sales users access to customer PII information

D.

Transaction security policies to prevent export of SF Data.

E.

Encrypt Sensitive Customer information maintained in SF.

A.

Event monitoring to monitor all user activities

D.

Transaction security policies to prevent export of SF Data.

E.

Encrypt Sensitive Customer information maintained in SF.

Explanation:

✅ A. Event Monitoring – Provides detailed user activity logs, important for auditing and compliance.

✅ D. Transaction Security Policies – Can block or alert on actions like data exports to enforce policies.

✅ E. Platform Encryption – Encrypts sensitive PII and financial data at rest to meet regulatory requirements.

❌ B. IP restriction – Controlled via Profile/Login IP Ranges, not Shield.

❌ C. Preventing PII access – Can be achieved with field-level security, not Shield specifically.

Data-Architect Practice Test Questions