- Email support@dumps4free.com
Topic 1: Exam Pool A
To reduce the case time resolution and improve customer satisfaction, Universal Containers (UC) wants to allow specialized marketing consultants to have edit access to Case records of VIP customers. These casts should be visible only to the support rep who owns the case and the marketing consultants. Which recommendation should a Salesforce architect give to allow this scenario?
A. Case organization-wide default Private and Account Team with Read/Edit permission.
B. Case organization-wide default Public Read Only and Case Team with Read permission.
C. Case organization-wide default Private, role hierarchy, and Read Only ownership-based sharing rule.
D. Case organization wide default Private and Case Team with Read/Edit permission.
Explanation: Setting the case organization-wide default to Private and adding the specialized marketing consultants to the account team with Read/Edit permission are the best recommendations to allow this scenario. This way, only the support rep who owns the case and the marketing consultants who are related to the account can see and edit the case records of VIP customers. Option B is incorrect, since setting the case organization wide default to Public Read Only would give access to all cases to all users. Option C is incorrect, since using a role hierarchy and a read-only ownership-based sharing rule would not give edit access to the marketing consultants. Option D is incorrect, since adding the marketing consultants to the case team would require manual configuration and maintenance.
Universal Containers (UC) sales managers are complaining that they cannot access their teams' Shipment records (a custom object). Initially, the admin suggested that this it happening due to misconfigured role hierarchy (Shipment OWD is Private). Alter investigation, they determined the. role hierarchy for these users is correct. What can be the reason why Universal Containers sales managers are not able to see Shipment records?
A. The Grant Access Using hierarchies’ option on Shipment Sharing Settings was incorrectly disabled by the Salesforce admin.
B. Role hierarchy Implicit sharing was Incorrectly disabled by the Salesforce adman.
C. Ownership-based sharing rule for Shipment was Incorrectly disabled by the Salesforce admin.
D. Sales managers have only the Read permission on the 5hipment object and should not be able to edit their team records.
Explanation: The Grant Access Using Hierarchies option on Shipment Sharing Settings allows users above the owner in the role hierarchy to have the same level of access as the owner. If this option is disabled, the role hierarchy will not grant access to the Shipment records, even if it is configured correctly. Therefore, the answer A is correct and the other options are incorrect
Universal Containers (UC) has created a custom Invoice object. Standard sales users at UC can see the records in search layout, but when they click to view the detail, only record name, created date, and last modified date are shown. When the system admin accesses it, he or she sees the full record detail with many more data fields. What is the likely cause of this issue?
A. Sales users profile does not have access to the remaining fields.
B. Page layout assigned to sales user profile has only read-only access to the fields.
C. Org-wide sharing settings have been set to Private and need to be adjusted to Public Read/Write.
D. A role-based sharing is missing and should be added for the sales user's role to grant access to the fields.
Explanation: The likely cause of this issue is that sales users profile does not have access to the remaining fields. Profile permissions determine what users can do with records, such as create, read, edit, or delete. If sales users profile does not have read permission for certain fields on the Invoice object, they will not be able to see those fields on the record detail page3. Page layout assigned to sales user profile, org-wide sharing settings, and role-based sharing are not likely causes of this issue.
Which two objects support creating queues? Choose 2 answers.
A. Account.
B. Opportunity.
C. Lead.
D. Case.
Explanation: Lead and Case are two objects that support creating queues. Queues are used to route records to a group of users who share workloads. Queues are available for standard objects such as Lead and Case, and custom objects that have a queue-supported lookup field. Option A is incorrect, since Account does not support creating queues. Option B is incorrect, since Opportunity does not support creating queues.
Universal Containers (UC) has 200 distributors that use Partner Community licenses. Partners cannot see each other's data, but UC is also trying to give more visibility to data for certain individuals at a distributor. HOW can an Architect give users in the partner user role access to all Case and Container records owned by any user, regardless of role, at the same distributor?
A. Create an ownership-based sharing rule.
B. Create sharing sets.
C. Create a Permission Set granting "View All" permission to Case and Container records.
D. Give super user permission to the individual partner users.
Explanation: To give users in the partner user role access to all Case and Container records owned by any user at the same distributor, an Architect can give super user permission to the individual partner users. Super user permission allows partner users to access data owned by other partner users belonging to the same account or below them in the role hierarchy. Creating an ownership-based sharing rule will not work, as it will share records based on the owner’s role or territory, not their account. Creating sharing sets will not work, as they are only available for Customer Community licenses, not Partner Community licenses. Creating a Permission Set granting “View All” permission to Case and Container records will not work, as it will give access to all records in those objects, regardless of their owner or account.
| Page 10 out of 48 Pages |
| Previous |