[2024年01月]更新のSalesforce Data-Architect問題集合格率を上げるならData-Architect試験問題集
あなたのゴールを成し遂げるための問題集！あなたのSalesforce Certified Data Architectの試験準備を合格するために実際のSalesforce Data-Architect問題集をおすすめします
質問 # 62
UC has millions of case records with case history and SLA dat
a. UC's compliance team would like historical cases to be accessible for 10 years for Audit purpose.
What solution should a data architect recommend?
- A. Archive Case data using Salesforce Archiving process
- B. Use a custom object to store archived case data.
- C. Purchase more data storage to support case object
- D. Use a custom Big object to store archived case data.
正解：D
解説：
The best solution to store historical cases for 10 years for audit purpose is to use a custom Big object to store archived case data. Big objects are a type of custom object that can store massive amounts of data on the Salesforce platform without affecting performance or storage limits. They also support point-and-click tools, triggers, and Apex code. Big objects can be used for archiving historical data that needs to be retained for compliance or analytics purposes3. Archiving case data using Salesforce Archiving process is not a good option because it only supports archiving cases that are closed for more than one year, and it does not allow customizing the archival criteria or accessing the archived data via Apex or APIs4. Purchasing more data storage to support case object is expensive and may impact performance. Using a custom object to store archived case data is not scalable and may consume a lot of storage space.
質問 # 63
A data architect has been tasked with optimizing a data stewardship engagement for a Salesforce instance Which three areas of Salesforce should the architect review before proposing any design recommendation? Choose 3 answers
- A. Review the sharing model to determine impact on duplicate records.
- B. Run key reports to determine what fields should be required.
- C. Export the setup audit trail to review what fields are being used.
- D. Review the metadata xml files for redundant fields to consolidate.
- E. Determine if any integration points create records in Salesforce.
正解：A、B、E
解説：
Determining if any integration points create records in Salesforce, running key reports to determine what fields should be required, and reviewing the sharing model to determine impact on duplicate records are three areas of Salesforce that the architect should review before proposing any design recommendation. These areas will help to identify the sources and quality of data, the business rules and validations for data entry, and the access and visibility of data across users and roles. Reviewing the metadata xml files for redundant fields to consolidate, and exporting the setup audit trail to review what fields are being used are not necessary steps for optimizing a data stewardship engagement, as they are more related to metadata management and audit tracking.
質問 # 64
Universal Containers (UC) has implemented a master data management strategy, which uses a central system of truth, to ensure the entire company has the same customer information in all systems. UC customer data changes need to be accurate at all times in all of the systems. Salesforce is the identified system of record for this information.
What is the correct solution for ensuring all systems using customer data are kept up to date?
- A. Send customer data nightly to the system of truth in a scheduled batch job.
- B. Send customer record changes from Salesforce to each system in a nightly batch job.
- C. Send customer record changes from Salesforce to the system of truth in real time.
- D. Have each system pull the record changes from Salesforce using change data capture.
正解：D
質問 # 65
Universal Containers would like to have a Service-Level Agreement (SLA) of 1 day for any data loss due to unintentional or malicious updates of records in Salesforce. What approach should be suggested to address this requirement?
- A. Evaluate a third-party AppExchange app, such as OwnBackup or Spanning, etc., for backup and archival purposes.
- B. Schedule a Weekly Extract Service for key objects and extract data in XL sheets to on-premise systems.
- C. Store all data in shadow custom objects on any updates and deletes, and extract them as needed .
- D. Build a daily extract job and extract data to on-premise systems for long-term backup and archival purposes.
正解：A
質問 # 66
UC has multiple SF orgs that are distributed across regional branches. Each branch stores local customer data inside its org's Account and Contact objects. This creates a scenario where UC is unable to view customers across all orgs.
UC has an initiative to create a 360-degree view of the customer, as UC would like to see Account and Contact data from all orgs in one place.
What should a data architect suggest to achieve this 360-degree view of the customer?
- A. Use an ETL tool to migrate gap Accounts and Contacts into each org.
- B. Use Salesforce Connect's cross-org adapter.
- C. Consolidate the data from each org into a centralized datastore
- D. Build a bidirectional integration between all orgs.
正解：C
解説：
Consolidating the data from each org into a centralized datastore is the best suggestion to achieve a 360-degree view of the customer. This way, UC can have a single source of truth for all customer data and avoid data silos and inconsistencies. The other options are not feasible because they either require complex integration, additional cost, or data duplication.
質問 # 67
Universal Containers (UC) is in the process of migrating legacy 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 object called Inventory_c.
Inventory data should be related to the standard Account object.
The Inventory object should Invent 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?
- A. Lookup relationship fields on Inventory related to Account
- B. Master-detail relationship filed on Account, related to Inventory_c
- C. Indirect lookup relationship field on Account, related to Inventory_c
- D. Master-detail relationship filed on Inventory_c, related to Account
正解：D
解説：
According to the Salesforce documentation, a relationship field is a field that allows linking one object to another object in Salesforce. There are different types of relationship fields that have different characteristics and behaviors, such as master-detail, lookup, indirect lookup, external lookup, etc.
To recommend a type of relationship field for this scenario, where legacy inventory data will be stored in a custom child object called Inventory__c, inventory data should be related to the standard Account object, the Inventory__c object should inherit the same sharing rules as the Account object, and anytime an Account record is deleted in Salesforce, the related Inventory__c record(s) should be deleted as well, a data architect should recommend:
Master-detail relationship field on Inventory__c, related to Account (option B). This means creating a field on the Inventory__c object that references the Account object as its parent. A master-detail relationship field establishes a parent-child relationship between two objects, where the parent object controls certain behaviors of the child object. For example, a master-detail relationship field can:
Inherit the sharing and security settings from the parent object to the child object. This means that the users who can access and edit the parent record can also access and edit the related child records.
Cascade delete from the parent object to the child object. This means that when a parent record is deleted, all the related child records are also deleted.
Roll up summary fields from the child object to the parent object. This means that the parent object can display aggregated information from the child records, such as count, sum, min, max, or average.
Master-detail relationship field on Account, related to Inventory__c (option A) is not a good solution, as it reverses the direction of the relationship. This means creating a field on the Account object that references the Inventory__c object as its parent. This is not possible, as a standard object cannot be on the detail side of a master-detail relationship. Indirect lookup relationship field on Account, related to Inventory__c (option C) is also not a good solution, as it is a special type of relationship field that allows linking a custom object to a standard object on an external system using an indirect reference. This is not applicable for this scenario, as both objects are in Salesforce and do not need an external reference. Lookup relationship field on Inventory__c related to Account (option D) is also not a good solution, as it establishes a looser relationship between two objects than a master-detail relationship. A lookup relationship field does not inherit sharing and security settings from the parent object to the child object, does not cascade delete from the parent object to the child object, and does not roll up summary fields from the child object to the parent object.
質問 # 68
NTO (Northern Trail Outlets) has a complex Salesforce org which has been developed over past 5 years. Internal users are complaining abt multiple data issues, including incomplete and duplicate data in the org. NTO has decided to engage a data architect to analyze and define data quality standards.
Which 3 key factors should a data architect consider while defining data quality standards? Choose 3 answers:
- A. Define data duplication standards and rules
- B. Measure data completeness and accuracy
- C. Define key fields in staging database for data cleansing
- D. Finalize an extract transform load (ETL) tool for data migration
- E. Measure data timeliness and consistency
正解：A、B、E
解説：
Defining data duplication standards and rules, measuring data timeliness and consistency, and measuring data completeness and accuracy are three key factors that a data architect should consider while defining data quality standards. Defining data duplication standards and rules can help prevent or reduce duplicate records in the org by specifying criteria and actions for identifying and merging duplicates. Measuring data timeliness and consistency can help ensure that the data is up-to-date, reliable, and synchronized across different sources. Measuring data completeness and accuracy can help ensure that the data is sufficient, relevant, and correct for the intended purposes.
質問 # 69
Universal Containers (UC) manages Vehicle and Service History in Salesforce. Vehicle (Vehicle__ c) and Service History (Service-History__ c) are both custom objects related through a lookup relationship.
Every week a batch synchronization process updates the Vehicle and Service History records in Salesforce. UC has two hours of migration window every week and is facing locking issues as part of the data migration process.
What should a data architect recommend to avoid locking issues without affecting performance of data migration?
- A. Insert the order in another custom object and use Batch Apex to move the records to Service_ Order__ c object.
- B. Change the lookup configuration to "Clear the value of this field" when lookup record is deleted.
- C. Use Bulk API parallel mode for data migration
- D. Use Bulk API serial mode for data migration
正解：D
質問 # 70
Northern Trail Outfitters needs to implement an archive solution for Salesforce dat a. This archive solution needs to help NTO do the following:
1. Remove outdated Information not required on a day-to-day basis.
2. Improve Salesforce performance.
Which solution should be used to meet these requirements?
- A. Create a full copy sandbox, and use it as a source for retaining archived data.
- B. Identify a location to store archived data and use scheduled batch jobs to migrate and purge the aged data on a nightly basis,
- C. Use a formula field that shows true when a record reaches a defined age and use that field to run a report and export a report into SharePoint.
- D. Identify a location to store archived data, and move data to the location using a time-based workflow.
正解：B
解説：
Identifying a location to store archived data and using scheduled batch jobs to migrate and purge the aged data on a nightly basis can be a way to meet the requirements for an archive solution. The article provides a use case of how to use Heroku Connect, Postgres, and Salesforce Connect to archive old data, free up space in the org, and still retain the option to unarchive the data if needed. The article also explains how this solution can improve Salesforce performance and meet data retention policies.
質問 # 71
Universal Container (UC) has accumulated data over years and has never deleted data from its Salesforce org. UC is now exceeding the storage allocations in the org. UC is now looking for option to delete unused from the org.
Which three recommendations should a data architect make is order to reduce the number of records from the org?
Choose 3 answers
- A. Identify records in objects that have not been modified or used In last 3 years.
- B. Use Rest API to permanently delete records from the Salesforce org.
- C. Archive the records in enterprise data warehouse (EDW) before deleting from Salesforce.
- D. Use hard delete in Bulk API to permanently delete records from Salesforce.
- E. Use hard delete in batch Apex to permanently delete records from Salesforce.
正解：A、C、D
解説：
Using hard delete in Bulk API, identifying records that have not been modified or used in last 3 years, and archiving the records in EDW before deleting from Salesforce are all good recommendations to reduce the number of records from the org1. Using hard delete in batch Apex or Rest API may not be as efficient or scalable as Bulk API
質問 # 72
NTO has been using salesforce for sales and service for 10 years. For the past 2 years, the marketing group has noticed a raise from 0 to 35 % in returned mail when sending mail using the contact information stored in salesforce.
Which solution should the data architect use to reduce the amount of returned mails?
- A. Use a 3rd-party data source to update contact information in salesforce.
- B. Have the sales team to call all existing customers and ask to verify the contact details.
- C. Delete contacts when the mail is returned to save postal cost to NTO.
- D. Email all customer and asked them to verify their information and to call NTO if their address is incorrect.
正解：A
質問 # 73
UC is planning a massive SF implementation with large volumes of dat
a. As part of the org's implementation, several roles, territories, groups, and sharing rules have been configured. The data architect has been tasked with loading all of the required data, including user data, in a timely manner.
What should a data architect do to minimize data load times due to system calculations?
- A. Enable granular locking to avoid "UNABLE _TO_LOCK_ROW" error.
- B. Leverage the Bulk API and concurrent processing with multiple batches
- C. Load the data through data loader, and turn on parallel processing.
- D. Enable defer sharing calculations, and suspend sharing rule calculations
正解：D
質問 # 74
Universal Container (US) is replacing a home-grown CRM solution with Salesforce, UC has decided to migrate operational (Open and active) records to Salesforce, while keeping historical records in legacy system, UC would like historical records to be available in Salesforce on an as needed basis.
Which solution should a data architect recommend to meet business requirement?
- A. Leverage mashup to display historical records in Salesforce.
- B. Build a chair solution to go the legacy system and display records.
- C. Leverage real-time integration to pull records into Salesforce.
- D. Bring all data Salesforce, and delete it after a year.
正解：A
解説：
According to the Using Mashups article on Salesforce Developers, one of the techniques for deploying large data volumes is to use mashups to display historical records in Salesforce. The article states that "Mashups are a way to display data from an external system within a Salesforce page without copying or synchronizing the data. Mashups use a combination of Visualforce, Apex callouts, and JavaScript code that runs in the browser. Mashups are useful when you want to display large amounts of read-only data that is stored outside of Salesforce." Therefore, a data architect should recommend this solution to meet the business requirement of UC.
質問 # 75
Which two aspects of data does an Enterprise data governance program aim to improve?
- A. Data usability
- B. Data integrity
- C. Data modeling
- D. Data distribution
正解：A、B
質問 # 76
NTO has implemented salesforce for its sales users. The opportunity management in salesforce 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 opportunity amount field on opportunities on a daily basis.
3. PPS is the trusted source within the 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 overriding issue?
- A. Create a custom field for opportunity amount that PPS updates separating the field that sales user updates.
- B. Change opportunity amount field access to read only for sales users using field level security.
- C. Create a custom field for opportunity amount that sales users update separating the fields that PPS updates.
- D. Change PPS integration to update only opportunity amount fields when values is NULL.
正解：B
解説：
Changing the opportunity amount field access to read only for sales users using field level security is the best way to address the overriding issue. This way, the sales users can still view the opportunity amount field but cannot edit it, and PPS can update it as the trusted source
質問 # 77
Universal Container require all customers to provide either a phone number of an email address when registering for an account.
What should the data architect use to ensure this requirement is met?
- A. validation Rule
- B. required Fields
- C. Apex Class
- D. Process Builder
正解：A
解説：
Using a validation rule is the best way to ensure that all customers provide either a phone number or an email address when registering for an account, as it allows defining a formula that evaluates whether a record meets certain criteria. Using required fields may not work if both phone number and email address are required. Using an Apex class or a Process Builder may be more complex or cumbersome than using a validation rule.
質問 # 78
Cloud Kicks has the following requirements:
* Their Shipment custom object must always relate to a Product, a Sender, and a Receiver (all separate custom objects).
* If a Shipment is currently associated with a Product, Sender, or Receiver, deletion of those records should not be allowed.
* Each custom object must have separate sharing models.
What should an Architect do to fulfill these requirements?
- A. Create two Master-Detail and one Lookup relationship to the parent records.
- B. Associate the Shipment to each parent record by using a VLOOKUP formula field.
- C. Create a Master-Detail relationship to each of the three parent records.
- D. Create a required Lookup relationship to each of the three parent records.
正解：D
質問 # 79
Universal Containers has a requirement to store more than 100 million records in salesforce and needs to create a custom big object to support this business requirement.
Which two tools should a data architect use to build custom object?
- A. Use DX to create big object.
- B. Go to Object Manager in setup and select new to create big object.
- C. Go to Big Object in setup select new to create big object.
- D. Use Metadata API to create big object.
正解：C、D
解説：
To build a custom big object to support storing more than 100 million records in Salesforce, a data architect should use Metadata API or Big Object in setup. Metadata API is an API that allows developers to create, retrieve, update, or delete metadata components in Salesforce programmatically. Big Object in setup is a user interface that allows admins to create big objects declaratively without writing code. Both tools can be used to define custom big objects and their fields, indexes, and relationships in Salesforce. Option A is incorrect because DX (Developer Experience) is a set of tools that allows developers to create and manage applications on Salesforce Platform, but it does not support creating big objects directly. Option D is incorrect because Object Manager in setup is a user interface that allows admins to create and manage standard and custom objects in Salesforce, but it does not support creating big objects declaratively.
質問 # 80
......
100% 無料Data-Architectデモ-試し読み [PDF]、今すぐゲットせよ：https://drive.google.com/open?id=1GKCGxZaHpCMGqD2QlGhdopwkiSnuBRrA
正確でかつ完璧 アンサーはまるでリアル試験問題：https://jp.fast2test.com/Data-Architect-premium-file.html