Practice Free Plat-Arch-201 Exam Online Questions
Question #91
Poor customer experience and higher costs
On analysis, it found that there are duplicate leads that are resulting to mitigate the issues?
- A . Build process is manually search and merge duplicates.
- B . Standard lead information across all channels.
- C . Build a custom solution to identify and merge duplicate leads.
- D . Implement third-party solution to clean and event lead data.
- E . Implement de-duplication strategy to prevent duplicate leads
Correct Answer: B, D, E
B, D, E
Explanation:
According to the Salesforce documentation2, duplicate leads are leads that have the same or similar information as other leads in Salesforce. Duplicate leads can cause poor customer experience, higher costs, and inaccurate reporting.
To mitigate the issues caused by duplicate leads, some of the recommended practices are:
Standardize lead information across all channels (option B). This means using consistent formats, values, and fields for capturing lead data from different sources, such as web forms, email campaigns, or third-party vendors. This can help reduce data quality issues and make it easier to identify and prevent duplicate leads.
Implement a third-party solution to clean and enrich lead data (option D). This means using an external service or tool that can validate, correct, update, and enhance lead data before or after importing it into Salesforce. This can help improve data quality and accuracy, and reduce duplicate leads.
Implement a de-duplication strategy to prevent duplicate leads (option E). This means using Salesforce features or custom solutions that can detect and block duplicate leads from being created or imported into Salesforce. For example, using Data.com Duplicate Management3, which allows defining matching rules and duplicate rules for leads and other objects.
Building a process to manually search and merge duplicates (option A) is not a good practice, as it can be time-consuming, error-prone, and inefficient. Building a custom solution to identify and merge duplicate leads (option C) is also not a good practice, as it can be complex, costly, and difficult to maintain. It is better to use existing Salesforce features or third-party solutions that can handle duplicate leads more effectively.
B, D, E
Explanation:
According to the Salesforce documentation2, duplicate leads are leads that have the same or similar information as other leads in Salesforce. Duplicate leads can cause poor customer experience, higher costs, and inaccurate reporting.
To mitigate the issues caused by duplicate leads, some of the recommended practices are:
Standardize lead information across all channels (option B). This means using consistent formats, values, and fields for capturing lead data from different sources, such as web forms, email campaigns, or third-party vendors. This can help reduce data quality issues and make it easier to identify and prevent duplicate leads.
Implement a third-party solution to clean and enrich lead data (option D). This means using an external service or tool that can validate, correct, update, and enhance lead data before or after importing it into Salesforce. This can help improve data quality and accuracy, and reduce duplicate leads.
Implement a de-duplication strategy to prevent duplicate leads (option E). This means using Salesforce features or custom solutions that can detect and block duplicate leads from being created or imported into Salesforce. For example, using Data.com Duplicate Management3, which allows defining matching rules and duplicate rules for leads and other objects.
Building a process to manually search and merge duplicates (option A) is not a good practice, as it can be time-consuming, error-prone, and inefficient. Building a custom solution to identify and merge duplicate leads (option C) is also not a good practice, as it can be complex, costly, and difficult to maintain. It is better to use existing Salesforce features or third-party solutions that can handle duplicate leads more effectively.
Question #91
Poor customer experience and higher costs
On analysis, it found that there are duplicate leads that are resulting to mitigate the issues?
- A . Build process is manually search and merge duplicates.
- B . Standard lead information across all channels.
- C . Build a custom solution to identify and merge duplicate leads.
- D . Implement third-party solution to clean and event lead data.
- E . Implement de-duplication strategy to prevent duplicate leads
Correct Answer: B, D, E
B, D, E
Explanation:
According to the Salesforce documentation2, duplicate leads are leads that have the same or similar information as other leads in Salesforce. Duplicate leads can cause poor customer experience, higher costs, and inaccurate reporting.
To mitigate the issues caused by duplicate leads, some of the recommended practices are:
Standardize lead information across all channels (option B). This means using consistent formats, values, and fields for capturing lead data from different sources, such as web forms, email campaigns, or third-party vendors. This can help reduce data quality issues and make it easier to identify and prevent duplicate leads.
Implement a third-party solution to clean and enrich lead data (option D). This means using an external service or tool that can validate, correct, update, and enhance lead data before or after importing it into Salesforce. This can help improve data quality and accuracy, and reduce duplicate leads.
Implement a de-duplication strategy to prevent duplicate leads (option E). This means using Salesforce features or custom solutions that can detect and block duplicate leads from being created or imported into Salesforce. For example, using Data.com Duplicate Management3, which allows defining matching rules and duplicate rules for leads and other objects.
Building a process to manually search and merge duplicates (option A) is not a good practice, as it can be time-consuming, error-prone, and inefficient. Building a custom solution to identify and merge duplicate leads (option C) is also not a good practice, as it can be complex, costly, and difficult to maintain. It is better to use existing Salesforce features or third-party solutions that can handle duplicate leads more effectively.
B, D, E
Explanation:
According to the Salesforce documentation2, duplicate leads are leads that have the same or similar information as other leads in Salesforce. Duplicate leads can cause poor customer experience, higher costs, and inaccurate reporting.
To mitigate the issues caused by duplicate leads, some of the recommended practices are:
Standardize lead information across all channels (option B). This means using consistent formats, values, and fields for capturing lead data from different sources, such as web forms, email campaigns, or third-party vendors. This can help reduce data quality issues and make it easier to identify and prevent duplicate leads.
Implement a third-party solution to clean and enrich lead data (option D). This means using an external service or tool that can validate, correct, update, and enhance lead data before or after importing it into Salesforce. This can help improve data quality and accuracy, and reduce duplicate leads.
Implement a de-duplication strategy to prevent duplicate leads (option E). This means using Salesforce features or custom solutions that can detect and block duplicate leads from being created or imported into Salesforce. For example, using Data.com Duplicate Management3, which allows defining matching rules and duplicate rules for leads and other objects.
Building a process to manually search and merge duplicates (option A) is not a good practice, as it can be time-consuming, error-prone, and inefficient. Building a custom solution to identify and merge duplicate leads (option C) is also not a good practice, as it can be complex, costly, and difficult to maintain. It is better to use existing Salesforce features or third-party solutions that can handle duplicate leads more effectively.
Question #93
Universal Containers (UC) has adopted Salesforce as its primary sales automated tool. UC has 100,00 customers with a growth rate of 10% a year, UC uses an on-premise web-based billing and invoice system that generates over 1 million invoices a year supporting a monthly billing cycle.
The UC sales team needs to be able to pull a customer record and view their account status, Invoice history, and opportunities without navigating outside of Salesforce.
What should a data architect use to provide the sales team with the required functionality?
- A . Create a custom object and migrate the last 12 months of Invoice data into Salesforce so it can be displayed on the Account layout.
- B . Write an Apex callout and populate a related list to display on the account record.
- C . Create a mashup page that will present the billing system records within Salesforce.
- D . Create a visual force tab with the billing system encapsulated within an iframe.
Correct Answer: C
C
Explanation:
To provide the sales team with the required functionality, a data architect should use a mashup page that will present the billing system records within Salesforce. A mashup page is a web page that combines data from multiple sources into a single integrated view. A mashup page can be created using Visualforce or Lightning Web Components, and can use Salesforce Connect or custom integrations to access external data from the on-premise web-based billing and invoice system. This will allow the sales team to pull a customer record and view their account status, invoice history, and opportunities without navigating outside of Salesforce.
Option A is incorrect because creating a custom object and migrating the last 12 months of invoice data into Salesforce so it can be displayed on the account layout will consume a lot of storage space and may not reflect the latest data from the billing system.
Option B is incorrect because writing an Apex callout and populating a related list to display on the account record will require additional development effort and may not be scalable or performant for large volumes of data.
Option D is incorrect because creating a visual force tab with the billing system encapsulated within an iframe will not allow the sales team to view the billing system records within the customer record, but rather in a separate tab.
C
Explanation:
To provide the sales team with the required functionality, a data architect should use a mashup page that will present the billing system records within Salesforce. A mashup page is a web page that combines data from multiple sources into a single integrated view. A mashup page can be created using Visualforce or Lightning Web Components, and can use Salesforce Connect or custom integrations to access external data from the on-premise web-based billing and invoice system. This will allow the sales team to pull a customer record and view their account status, invoice history, and opportunities without navigating outside of Salesforce.
Option A is incorrect because creating a custom object and migrating the last 12 months of invoice data into Salesforce so it can be displayed on the account layout will consume a lot of storage space and may not reflect the latest data from the billing system.
Option B is incorrect because writing an Apex callout and populating a related list to display on the account record will require additional development effort and may not be scalable or performant for large volumes of data.
Option D is incorrect because creating a visual force tab with the billing system encapsulated within an iframe will not allow the sales team to view the billing system records within the customer record, but rather in a separate tab.
Question #94
Each contact may attend multiple conferences and each conference may be related to multiple contacts.
How should a data architect model the relationship between the contact and conference objects?
- A . Implement a Contact Conference junction object with master detail relationship to both contact and conference_c
- B . Create a master detail relationship field on the Contact object.
- C . Create a master detail relationship field on the Conference object.
- D . Create a lookup relationship field on contact object.
Correct Answer: A
A
Explanation:
Implementing a Contact Conference junction object with master detail relationship to both contact and conference_c is the correct way to model the relationship between the contact and conference objects, as it allows a many-to-many relationship between them. This means that each contact can attend multiple conferences, and each conference can be related to multiple contacts. Creating a master detail relationship field on either the contact or the conference object would create a one-to-many relationship, which does not meet the requirements. Creating a lookup relationship field on contact object would also create a one-to-many relationship, and would not enforce referential integrity.
A
Explanation:
Implementing a Contact Conference junction object with master detail relationship to both contact and conference_c is the correct way to model the relationship between the contact and conference objects, as it allows a many-to-many relationship between them. This means that each contact can attend multiple conferences, and each conference can be related to multiple contacts. Creating a master detail relationship field on either the contact or the conference object would create a one-to-many relationship, which does not meet the requirements. Creating a lookup relationship field on contact object would also create a one-to-many relationship, and would not enforce referential integrity.
Question #95
UC has migrated its Back-office data into an on-premise database with REST API access. UC recently implemented Sales cloud for its sales organization. But users are complaining about a lack of order data inside SF.
UC is concerned about SF storage limits but would still like Sales cloud to have access to the data.
Which design patterns should a data architect select to satisfy the requirement?
- A . Migrate and persist the data in SF to take advantage of native functionality.
- B . Use SF Connect to virtualize the data in SF and avoid storage limits.
- C . Develop a bidirectional integration between the on-premise system and Salesforce.
- D . Build a UI for the on-premise system and iframe it in Salesforce
Correct Answer: B
B
Explanation:
The best design pattern to satisfy the requirement of accessing order data from an on-premise database with REST API access without consuming SF storage limits is to use SF Connect to virtualize the data in SF and avoid storage limits. SF Connect is an integration tool that allows users to access and integrate data from external sources using external objects. External objects are similar to custom objects, except that the data resides in another system and is accessed in real time via web service callouts. SF Connect supports various adapters to connect to different types of external data sources, such as OData, cross-org, or Apex custom adapter11. Migrate and persist the data in SF to take advantage of native functionality is not a good option because it would consume SF storage limits and require data synchronization between systems. Develop a bidirectional integration between the on-premise system and Salesforce is not a good option because it would be complex and costly to implement and maintain, and it would also consume SF storage limits. Build a UI for the on-premise system and iframe it in Salesforce is not a good option because it would not provide a seamless user experience and it would not allow users to search, report, or perform actions on the external data.
B
Explanation:
The best design pattern to satisfy the requirement of accessing order data from an on-premise database with REST API access without consuming SF storage limits is to use SF Connect to virtualize the data in SF and avoid storage limits. SF Connect is an integration tool that allows users to access and integrate data from external sources using external objects. External objects are similar to custom objects, except that the data resides in another system and is accessed in real time via web service callouts. SF Connect supports various adapters to connect to different types of external data sources, such as OData, cross-org, or Apex custom adapter11. Migrate and persist the data in SF to take advantage of native functionality is not a good option because it would consume SF storage limits and require data synchronization between systems. Develop a bidirectional integration between the on-premise system and Salesforce is not a good option because it would be complex and costly to implement and maintain, and it would also consume SF storage limits. Build a UI for the on-premise system and iframe it in Salesforce is not a good option because it would not provide a seamless user experience and it would not allow users to search, report, or perform actions on the external data.
Question #96
UC has a requirement to migrate 100 million order records from a legacy ERP application into the salesforce platform. UC does not have any requirements around reporting on the migrated data.
What should a data architect recommend to reduce the performance degradation of the platform?
- A . Create a custom object to store the data.
- B . Use a standard big object defined by salesforce.
- C . Use the standard “Order” object to store the data.
- D . Implement a custom big object to store the data.
Correct Answer: D
D
Explanation:
Implementing a custom big object to store the data is the best recommendation to reduce the performance degradation of the platform, as it allows storing large volumes of data that do not need real-time access or reporting. Custom big objects can be defined using metadata API or developer console, and support up to 1 billion records per object. Creating a custom object or using the standard order object would consume a lot of storage space and impact the performance of queries and reports. Using a standard big object defined by salesforce would not be applicable for order records, as standard big objects are predefined for specific use cases such as audit trails or field history.
D
Explanation:
Implementing a custom big object to store the data is the best recommendation to reduce the performance degradation of the platform, as it allows storing large volumes of data that do not need real-time access or reporting. Custom big objects can be defined using metadata API or developer console, and support up to 1 billion records per object. Creating a custom object or using the standard order object would consume a lot of storage space and impact the performance of queries and reports. Using a standard big object defined by salesforce would not be applicable for order records, as standard big objects are predefined for specific use cases such as audit trails or field history.
Question #97
Due to security requirements, Universal Containers needs to capture specific user actions, such as login, logout, file attachment download, package install, etc.
What is the recommended approach for defining a solution for this requirement?
- A . Use a field audit trail to capture field changes.
- B . Use a custom object and trigger to capture changes.
- C . Use Event Monitoring to capture these changes.
- D . Use a third-party AppExchange app to capture changes.
Correct Answer: C
C
Explanation:
Event Monitoring is a feature that allows you to track user actions, such as logins, logouts, downloads, etc., in your Salesforce org. You can use Event Monitoring to monitor performance, usage, security, and compliance
C
Explanation:
Event Monitoring is a feature that allows you to track user actions, such as logins, logouts, downloads, etc., in your Salesforce org. You can use Event Monitoring to monitor performance, usage, security, and compliance
Question #98
A large telecommunication provider that provides internet services to both residence and business has the following attributes:
A customer who purchases its services for their home will be created as an Account in Salesforce.
Individuals within the same house address will be created as Contact in Salesforce.
Businesses are created as Accounts in Salesforce.
Some of the customers have both services at their home and business.
What should a data architect recommend for a single view of these customers without creating multiple customer records?
- A . Customers are created as Contacts and related to Business and Residential Accounts using the Account Contact Relationships.
- B . Customers are created as Person Accounts and related to Business and Residential Accounts using the Account Contact relationship.
- C . Customer are created as individual objects and relate with Accounts for Business and Residence accounts.
- D . Costumers are created as Accounts for Residence Account and use Parent Account to relate Business Account.
Correct Answer: B
B
Explanation:
Creating customers as Contacts and relating them to Business and Residential Accounts using the Account Contact Relationships (option A) is the best option to recommend for a single view of these customers without creating multiple customer records, as it allows the data architect to model complex relationships between customers and accounts using native Salesforce features and tools. Creating customers as Person Accounts and relating them to Business and Residential Accounts using the Account Contact relationship (option B) is not a good option, as it may create data redundancy and inconsistency, and it does not leverage the existing Contact object. Creating customers as individual objects and relating them with Accounts for Business and Residence accounts (option C) is also not a good option, as it may require more customization and maintenance effort, and it does not leverage the existing Account and Contact objects. Creating customers as Accounts for Residence Account and using Parent Account to relate Business Account (option D) is also not a good option, as it may create confusion and complexity with the account hierarchy, and it does not leverage the existing Contact object.
B
Explanation:
Creating customers as Contacts and relating them to Business and Residential Accounts using the Account Contact Relationships (option A) is the best option to recommend for a single view of these customers without creating multiple customer records, as it allows the data architect to model complex relationships between customers and accounts using native Salesforce features and tools. Creating customers as Person Accounts and relating them to Business and Residential Accounts using the Account Contact relationship (option B) is not a good option, as it may create data redundancy and inconsistency, and it does not leverage the existing Contact object. Creating customers as individual objects and relating them with Accounts for Business and Residence accounts (option C) is also not a good option, as it may require more customization and maintenance effort, and it does not leverage the existing Account and Contact objects. Creating customers as Accounts for Residence Account and using Parent Account to relate Business Account (option D) is also not a good option, as it may create confusion and complexity with the account hierarchy, and it does not leverage the existing Contact object.
Question #99
Managers must see total hours volunteered while viewing the Project__ c record.
Which data relationship should the data architect use to support this requirement when creating the custom VTOTime__c object?
- A . Lookup Field on Project_c to VTOTime_c displaying a list of VTOTime__c in a related list.
- B . Lookup field on VTOTime_c to Project_c with formula filed on Project__ c showing Sum of hours from VTOTime__c records.
- C . Master Detail Field on VTOTime_ c to Project_c with rollup summary field on Project __c showing
sum of hours from VTOTime_c records. - D . Master Detail field on Project _c to VTOTime _c showing a list of VTOTime_c Records in a related list.
Correct Answer: C
C
Explanation:
A master-detail field on VTOTime__c to Project__c is the data relationship that the data architect should use to support the requirement when creating the custom VTOTime__c object. A master-detail relationship creates a parent-child relationship between two objects, where the master record controls certain behaviors of the detail record, such as security, ownership, deletion, and roll-up summary fields. By using a master-detail field on VTOTime__c to Project__c, you can ensure that the ability to view or edit the VTOTime__c object is the same as the Project__c record, and that managers can see the total hours volunteered while viewing the Project__c record using a roll-up summary field.
C
Explanation:
A master-detail field on VTOTime__c to Project__c is the data relationship that the data architect should use to support the requirement when creating the custom VTOTime__c object. A master-detail relationship creates a parent-child relationship between two objects, where the master record controls certain behaviors of the detail record, such as security, ownership, deletion, and roll-up summary fields. By using a master-detail field on VTOTime__c to Project__c, you can ensure that the ability to view or edit the VTOTime__c object is the same as the Project__c record, and that managers can see the total hours volunteered while viewing the Project__c record using a roll-up summary field.