SF-Data-Arch Practice Test 18 — 15 Questions

Question 1

Which object type is most likely to cause performance issues in an LDV environment if not managed correctly?

Accepted Answer

An object with many lookup relationships to other parent objects.. Highly relational objects, especially those with many lookup relationships, are most prone to performance issues. Each lookup relationship can act as a locking point, and queries involving these fields often require complex joins. By understanding which objects are 'hot' in terms of frequency of access and relationship density, architects can prioritize them for indexing, archiving, and skinny table strategies to maintain system stability.

Answer

A flat custom object with no relationships.

Answer

An object containing only standard picklist fields.

Answer

A setup object maintained by the system administrator.

Question 2

Refer to the exhibit. In a 50 million record Account table, why might this query perform poorly?

Accepted Answer

The custom field is likely missing an index, causing a full table scan.. This query uses a filter on CreatedDate (a system-indexed field) and a custom field (Custom_External_ID__c). If Custom_External_ID__c is not indexed, the query optimizer must perform a full table scan. Even with a system index, if the combination of filters is not selective enough, the query will exceed the platform's selectivity threshold, leading to a non-selective query error or severe performance degradation.

Answer

The CreatedDate field is not indexed by default in Salesforce.

Answer

The Id field should be the only field in the WHERE clause.

Answer

Apex triggers are preventing the query from completing.

Question 3

A company is migrating 50 million records into Salesforce. They need to ensure data integrity while minimizing API consumption. Which strategy is most efficient for a one-time bulk data load?

Accepted Answer

Use the Bulk API 2.0 with CSV files.. Bulk API 2.0 is the recommended approach for large datasets as it optimizes throughput by automatically breaking large jobs into smaller batches. It significantly reduces the number of API calls required compared to standard REST or SOAP APIs. Properly architecting for data loads involves choosing tools that leverage Bulk API 2.0 to maintain governor limits and ensure successful processing of high-volume data without impacting real-time integrations.

Answer

Use the standard REST API with single-record inserts.

Answer

Utilize the SOAP API with synchronous processing.

Answer

Perform a manual data import via the UI.

Question 4

A company is migrating 100 million records into Salesforce. Which TWO actions should the architect take to optimize performance and prevent row locking?

Accepted Answer

Disable unnecessary triggers during the data load.. High-volume data loads require careful management of record locking and indexing. Disabling triggers during the load prevents unnecessary processing and lock contention. Furthermore, reducing the number of indexes on the target object minimizes the overhead required for every insert operation, as Salesforce must update every index on the object for each new record processed during the migration process.

Answer

Enable all custom indexes before the data load.

Answer

Use the Bulk API 2.0 with serial mode.

Answer

Increase the batch size to 10,000.

Question 5

Universal Containers wants to ensure data quality by preventing the creation of duplicate Leads from various sources. The architect recommends matching rules and duplicate rules. Which action should the architect take to ensure that users are alerted to potential duplicates during manual entry while blocking automated integrations?

Accepted Answer

Set 'Report' for record creation and 'Block' for API insertion.. To achieve this, the architect must configure duplicate rules with distinct settings for user-based versus integration-based scenarios. By setting the 'Report' action for user-facing rules, the UI displays an alert, while selecting 'Block' for API-based rules prevents duplicates from being inserted via integration tools. This tiered approach maintains data integrity across different entry points without hindering necessary manual workflows during prospect record creation.

Answer

Enable 'Block' for both user-facing and integration-based duplicate rules.

Answer

Apply 'Report' to the record creation rule and ignore the API settings.

Answer

Use a third-party AppExchange solution exclusively for integration rules.

Question 6

When designing a custom Data Model, when should an architect choose a 'Lookup' relationship over a 'Master-Detail' relationship?

Accepted Answer

When the child record must have its own sharing settings.. Lookup relationships offer flexibility where the parent and child records are logically distinct and can exist independently. This is ideal for scenarios where sharing is decoupled or when the child records should not be deleted upon parent deletion. By understanding these nuances, an architect avoids the 'cascading' consequences of Master-Detail relationships, which is vital for designing a loosely coupled, maintainable system that satisfies complex business requirements without unnecessary record interdependencies.

Answer

When the child records must inherit the parent's security.

Answer

When the child must be deleted when the parent is deleted.

Answer

When you need to create a Roll-up Summary field.

Question 7

A large enterprise discovers duplicate accounts across Salesforce and their legacy system. Before importing data, they decide to implement a 'Data Stewardship' program. What is the primary role of a data steward in this context?

Accepted Answer

Managing data quality, including defining rules and resolving data conflicts.. Data stewards bridge the gap between IT and business by overseeing the quality and lifecycle of master data. They define policies, resolve data conflicts, and ensure compliance with governance standards. This role is crucial because technical solutions alone cannot solve issues stemming from inconsistent business processes or ambiguous data definitions, requiring human oversight to make final decisions on data accuracy and business logic interpretation.

Answer

Writing custom Apex code to automate the merging of all duplicate accounts.

Answer

Performing daily backups of the Salesforce database to ensure disaster recovery.

Answer

Configuring Salesforce sharing rules to restrict access to sensitive account data.

Question 8

A Data Architect is designing a disaster recovery plan. Which data elements must be explicitly backed up outside of Salesforce to ensure business continuity?

Accepted Answer

System Metadata, Custom Settings, and complex relational data.. While Salesforce provides high availability, it does not provide a point-in-time restore for individual records or deleted data if the retention period has passed. Metadata, custom settings, and high-value transactional data must be exported and stored off-platform. This strategy ensures that if a catastrophic deletion occurs or if there is a need to revert to a specific state, the organization can reconstruct its configuration and data without relying solely on the platform's standard capabilities.

Answer

Standard Account and Contact records, as they are managed by Salesforce.

Answer

Chatter posts and historical activity logs for all users.

Answer

All temporary batch job execution logs.

Question 9

Refer to the exhibit. The query is part of a bulk apex process. What is the potential risk with this query in a large-scale data environment?

Accepted Answer

The query will hit governor limits if the result set is too large.. The primary risk is hitting the SOQL 'Too many query rows' limit or 'CPU time' limit when joining large related datasets. While the query looks standard, processing the nested collection of contacts for 50,000 accounts can consume significant memory and CPU cycles. Architects must implement batching and pagination to ensure the process remains within governor limits and provides stable performance.

Answer

The query fails because nested SOQL is not supported.

Answer

The query will cause a SOQL injection vulnerability.

Answer

The query is invalid because it misses the 'FROM' clause.

Question 10

Refer to the exhibit. An architect is using the Salesforce CLI to perform a high-volume data upsert. What is the significance of the '-i Legacy_ID__c' parameter in this command?

Accepted Answer

It defines the custom External ID field used to match existing records.. When performing an upsert operation via the Bulk API (or CLI), the system needs a way to determine if a record already exists or if a new one should be created. The '-i' parameter specifies the External ID field that the system will use as the unique key for this matching process.

Answer

It specifies the internal Salesforce ID field for the upsert.

Answer

It indicates the field that should be used as the primary index for PK Chunking.

Answer

It tells the CLI to ignore all records that have a null value in that field.

Question 11

Which TWO of the following are true regarding the impact of 'Formula Fields' on Large Data Volumes?

Accepted Answer

Filtering on formula fields causes full table scans.. Formula fields are calculated at runtime, which means their values are not stored in the database. When querying or filtering on a formula field, the system must compute the value for every record, which is computationally expensive. As the data volume grows, this causes significant performance issues because the database cannot utilize indexes on formula fields (unless they are deterministic and specifically indexed), leading to slow, resource-intensive queries.

Answer

Formula fields are indexed by default.

Answer

They improve query performance by pre-calculating data.

Answer

Values are stored in the database for fast retrieval.

Question 12

Refer to the exhibit. The Data Architect is tasked with ensuring that order status options are limited based on the geographic region of the order. Which feature should be used to implement this?

Accepted Answer

Dependent Picklists.. Dependent picklists are the standard Salesforce mechanism for limiting the values of one picklist based on the selection of another. By defining a controlling field (Region) and a dependent field (Status), the architect ensures data entry accuracy and prevents invalid combinations of status and geography from being saved, which is vital for regional reporting and process consistency.

Answer

Record Types.

Answer

Validation Rules.

Answer

Custom Metadata Types.

Question 13

Which document is the most critical for Data Governance to ensure that Salesforce Orgs remain compliant with regional data residency requirements?

Accepted Answer

Data Inventory and Mapping.. The Data Inventory and Mapping document is critical because it identifies exactly where sensitive data resides. To comply with data residency laws, architects must know which Org holds data and where those Orgs are physically hosted. Without this mapping, it is impossible to audit compliance or implement the necessary architectural controls to keep data within specific geographic borders as required by law.

Answer

User Access Request Log.

Answer

Service Level Agreement (SLA).

Answer

Salesforce Org release notes.

Question 14

A global Salesforce org maintains an Account record that is simultaneously updated by an inbound ERP integration, a nightly Data Loader batch, and a sales rep via the Lightning UI. During a data quality audit, the governance board finds that conflicting values for the 'Annual Revenue' field have overwritten each other, and no one can determine which source was authoritative at any point in time. The board wants to ensure that future conflicts are detected, attributed to a source system, and resolved according to a documented priority order before the record is committed. Which governance mechanism should the Data Architect recommend to satisfy this requirement?

Accepted Answer

Implement a Master Data Management (MDM) system of record with survivorship rules that encode the source priority order and write the golden record back to Salesforce.. The requirement is a governed, deterministic conflict-resolution process that records which source system was authoritative. An MDM system of record with survivorship rules encodes the source priority order as governed metadata, applies it automatically when sources disagree, and preserves lineage for audit. Field history, manual review queues, and permission-based write exclusion either act too late, rely on human latency, or block legitimate writes without resolving the underlying conflict.

Answer

Create a validation rule that blocks updates to Annual Revenue unless the running user has the 'Data Governance' permission set, and grant that permission set only to the ERP integration user.

Answer

Implement a Data Steward review queue using a custom object and a scheduled Flow that asks the data steward to manually approve each conflicting value.

Answer

Enable Field History Tracking on Annual Revenue and create a report that shows all changes, then distribute the report to the governance board weekly.

Question 15

Universal Containers maintains a custom object, Shipment__c, that has a Master-Detail relationship to Account and a Lookup to Carrier__c. A Data Architect is asked to design a new object, Shipment_Line__c, that must always belong to exactly one Shipment__c, must inherit Shipment__c's sharing rules, and must not be independently owned by a different user. Which relationship type should be used between Shipment_Line__c and Shipment__c?

Accepted Answer

Master-Detail, with Shipment__c as the master and Shipment_Line__c as the detail.. The requirement is true containment with inherited sharing and no separate ownership. A Master-Detail relationship enforces that the detail cannot exist without the master, rolls up the master's sharing and organization-wide defaults, and ties the detail's ownership to the master. A required lookup can approximate containment but leaves the child independently owned and separately shared, which violates the stated constraints.

Answer

Hierarchical relationship, using the User object to control ownership and access to Shipment_Line__c.

Answer

Lookup, with a required field to Shipment__c and a sharing rule that grants access based on the Shipment__c owner.

Answer

Self-relationship on Shipment__c, with a field pointing to the parent Shipment__c record.