Salesforce Certified Platform Data Architect 온라인 연습
최종 업데이트 시간: 2026년06월04일
당신은 온라인 연습 문제를 통해 Salesforce Plat-Arch-201 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Plat-Arch-201 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 257개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Evaluating a third-party AppExchange app, such as OwnBackup or Spanning, etc., for backup and archival purposes is the best approach to address the requirement of having a one-day SLA for any data loss. These apps can provide automated backups, granular restores, and compliance features that can help UC recover from any data loss or corruption scenarios.
정답:
Explanation:
Exporting in multiple batches and using PK Chunking are two steps that can help correct the issues with exporting large volumes of Order records using Informatica Cloud Loader. Exporting in multiple batches can reduce the load on the system and avoid timeouts or errors. Using PK Chunking can split a large data set into smaller chunks based on the record IDs and enable parallel processing of each chunk.
정답:
Explanation:
Creating a custom lookup field on the standard Product to reference the parent record in the hierarchy is the correct way to modify the standard Product object model to support a hierarchical data structure. This allows UC to create a self-relationship on the Product object and define parent-child relationships among products.
정답:
Explanation:
Using leading % wildcards, performing large loads and deletions, and using NOT and != operators are three options that prevent a query from being selective. These options can cause the query to scan a large number of records or indexes, which can negatively impact the performance and scalability of the query5. Using a custom index on a deterministic formula field, on the other hand, can improve the query selectivity by allowing the query to use the index instead of scanning all the records6.
정답:
Explanation:
Setting Customer-Reference_c as an External ID (unique) is the recommended solution to ensure that support agents using global search and reports can quickly find shipment records. This is because external ID fields are indexed and can be used as filters in reports and list views4. Making the field unique also ensures that there are no duplicate values that could confuse the search results.
정답:
Explanation:
Leveraging a “tier”-based approach to classify the record storage need is a true statement with respect to a data archiving strategy for UC. This approach involves defining different tiers of data based on their usage, value, and retention policies, and then applying appropriate storage and archiving solutions for each tier.
정답:
Explanation:
Integrating with a third-party database or service for address validation and enrichment is a scalable strategy that can improve the quality of the Account addresses by comparing them with a reliable source of data1. Leveraging Data.com Clean to clean up Account address fields with the D&B database is another scalable strategy that can automatically update and enrich Account records with verified information from Data.com2.
정답:
Explanation:
The two best practices that should be followed when using SOSL for searching are: Keep searches specific and avoid wildcards where possible. Use Find in “ALL FIELDS” for faster searches. These best practices are helpful because they optimize the search performance and relevance.
For example, keeping searches specific and avoiding wildcards where possible can reduce the number of results returned and improve the search accuracy. Using Find in “ALL FIELDS” for faster searches can leverage Salesforce’s pre-defined indexes on common fields and return results more quickly than specifying individual fields.
정답:
Explanation:
The recommended solution to address the requirements of Universal Containers (UC) is to roll-up discount request amount at the line-item-level and line-item-level summary discount at the opportunity level. This solution would allow UC to show all sums of discounts across line items at an opportunity level using standard roll-up summary fields. Since UC has a multi-level master-detail relationship for opportunities, a custom opportunity line item object, and a custom discount request object, they can use two levels of roll-up summary fields to aggregate the discount amounts from the child objects to the parent objects. For example, they can create a roll-up summary field on the custom line item object to sum up the discount request amounts from the custom discount request object. Then, they can create another roll-up summary field on the opportunity object to sum up the line-item-level summary discounts from the custom line item object.
정답:
Explanation:
The three characteristics of a Skinny table that help improve report and query performance are: Skinny tables can contain frequently used fields and thereby help avoid joins. Skinny tables are kept in sync with changes to data in the source tables. Skinny tables do not include records that are available in the recycle bin. These characteristics are beneficial because they reduce the query complexity and execution time, and improve the data accuracy and freshness. For example, skinny tables can contain frequently used fields from multiple objects, such as Account and Contact, and thereby help avoid joins that can slow down queries4. Skinny tables are updated automatically when the source tables are modified, so they always reflect the latest data5. Skinny tables do not include records that are available in the recycle bin, so they only contain active records that are relevant for reports and queries.
정답:
Explanation:
The three questions that should be considered when designing an appropriate archiving strategy are: If reporting is necessary, can the information be aggregated into fewer, summary records? Will the data being archived need to be reported on or accessed in any way in the future? Are there any regulatory restrictions that will influence the archiving and purging plans? These questions are important because they help determine the scope, frequency, and method of archiving and purging data from Salesforce. For example, if reporting is necessary, then summary records or analytics snapshots can be used to store aggregated data and reduce the number of records that need to be archived1. If the data being archived needs to be accessed in the future, then offsite storage or external objects can be used to retain the data and make it available on demand2. If there are any regulatory restrictions, such as GDPR or HIPAA, then the archiving and purging plans need to comply with them and ensure data security and privacy
정답:
Explanation:
The recommended solution for Universal Containers (UC) to implement its new Internet of Things technology is to create a new Container Reading custom object with a master-detail relationship to Container which is created when a new measure is received for a specific container. Implement an archiving process that runs every hour. This solution would allow UC to store and access current and historical temperature and humidity data for each container on Salesforce, and use reports and dashboards to analyze it. However, since UC expects a large volume of data over time, they should implement an archiving process that moves data off-platform after a certain period of time to avoid hitting the Org data storage limit and maintain optimal performance. The other options are not recommended, as they would either not store the historical data on Salesforce, or create too many custom fields on the Container object that could impact performance and usability.
정답:
Explanation:
The two recommended options to assign Account ownership to mitigate potential performance problems are to let a “system user” own all the Account records without assigning any role to this user in Role Hierarchy, or to let a “system user” own the Account records and assign this user to the lowest-level role in the Role Hierarchy. This is because these options would reduce the number of sharing calculations and rules that need to be applied to the Account records, and improve the performance and scalability of the system34. The other options are not recommended, as they would increase the sharing complexity and overhead, and potentially expose sensitive data to unauthorized users.
정답:
Explanation:
The recommended course of action to appropriately integrate the new Opportunity engagement system with Salesforce is to bring the stakeholders together to discuss the appropriate data strategy moving forward. This is because there may be valuable data in both systems that need to be reconciled and harmonized, and the Master Data Management (MDM) strategy may need to be revised or updated to accommodate the new system. The other options are not recommended, as they may result in data loss, inconsistency, or duplication
정답:
Explanation:
The recommended approach to re-run the test is to refresh the full copy sandbox and re-run the data migration test. A full copy sandbox is a replica of the production Org, including all data, metadata, and attachments. Refreshing a full copy sandbox means creating a new copy of the production Org and replacing the existing sandbox. This would ensure that the test is run on a clean and up-to-date environment, without any leftover data or configuration from previous tests. Truncating or hard deleting objects would not be sufficient, because they would not remove all the data or metadata from the sandbox, and they could also affect other dependent objects or processes.