Salesforce SHARING-AND-VISIBILITY-DESIGNER Online Practice Questions and Exam Preparation

Salesforce SHARING-AND-VISIBILITY-DESIGNER Online Questions & Answers

• Question 201:

  Universal Containers does not want the Users in the Custom Sales Department Profile to be able to delete Opportunities. How would the Architect prevent a certain set of users from deleting Opportunities?

  A. Remove the Delete button from the Opportunity Page Layout and Record Type settings.
  B. Create a Validation Rule that checks the User's Profile before allowing the Is Deleted flag to be set to True.
  C. Override the Standard button with a Visualforce Page that warns them that they do not have permission to delete.
  D. Remove the "Opportunity Delete" Permission from the Sales Team's User Profile in the Object Permissions.
  D. Remove the "Opportunity Delete" Permission from the Sales Team's User Profile in the Object Permissions.

• Question 202:

  Universal Containers has successfully implemented a large Service Cloud rollout for their national call center 3 months ago. One of their largest customer accounts, United Automotive, has over 15,000 open cases. Agents are now having trouble opening new cases for United Automotive. When they try to create a case, the following Error messages appear for them UNABLE_TO_LOCK_ROW They notice that this only occurs for the United Automotive account. If they try to save the case again it will usually work, but the problem seems to be happening more and more often. What option should the Architect recommend?

  A. Review the Account structure to split the United Automotive account into multiple branch accounts.
  B. Review the Customer Service Profile to ensure that they have Read/Write access to the appropriate Case and Account Fields.
  C. Review all Case Sharing Rules and consolidate where appropriate to reduce the total number of sharing rules.
  D. Review all Account sharing rules to ensure that the Customer Service team has Read/Write access to the United Automotive Account.
  A. Review the Account structure to split the United Automotive account into multiple branch accounts.

• Question 203:

  Get Cloudy Consulting has an Opportunity object with Public Read Only sharing settings on it.

  A user is adding account team members to the Account.

  Which Opportunity access options can the user see?

  A. Private and Read Only
  B. Private
  C. Read Only and Read/Write
  D. Read Only
  C. Read Only and Read/Write

• Question 204:

  What is required to implement Filter-Based Opportunity Territory Assignment?

  A. Define an account assignment with a filter criteria rule for Filter-Based Opportunity Territory Assignment.
  B. Define a Territory assignment rule with filter criteria for Filter-Based Opportunity Territory Assignment.
  C. Define a custom Apex class for Filter-Based Opportunity Territory Assignment in the system.
  D. Define an Opportunity assignment rule with filter criteria for Filter-Based Opportunity Territory Assignment.
  C. Define a custom Apex class for Filter-Based Opportunity Territory Assignment in the system.

• Question 205:

  What feature in Salesforce is needed to restrict access to a custom object that has Public Read/Write access?

  A. Role Hierarchy
  B. Record Type
  C. Page Layout
  D. Profile
  D. Profile

• Question 206:

  Universal Containers (UC) wants to reduce the amount of redundant leads entered into the system. UC also wants to ensure that leads are only edited/reassigned by the lead owner. What organization wide default (OWD) approach should be recommended to help UC implement these requirements?

  A. Implement a Public Read Only OWD on Lead.
  B. Implement a Private OWD on Lead.
  C. Implement a Public Read Only/Transfer OWD on Lead.
  D. Implement a Public Read/Write OWD on Lead.
  A. Implement a Public Read Only OWD on Lead.

• Question 207:

  Universal Containers has a requirement to share Accounts automatically to the users at a field office. They currently have the following setup in their environment:

  Accounts are set to Private in the Org-Wide Default.

  The field office is specified by a lookup in the account object.

  There are 400 field offices.

  The users in each field office are managed using public groups.

  Based upon a lookup relationship field on the Account, how should the Architect meet their requirement?

  A. Use Account Teams to share the Account with the appropriate field office.
  B. Use Manual Sharing to share the Account with the appropriate field office.
  C. Use Criteria-Based Sharing to share the Account with the appropriate field office.
  D. Use Programmatic Sharing to share the Account with the appropriate field office.
  C. Use Criteria-Based Sharing to share the Account with the appropriate field office.

• Question 208:

  Universal Containers has the following requirements:

  *

  The Commercial Account and Consumer Account support departments should not collaborate.

  *

  The Commercial and Consumer sales users roll up to the same VP of Sales, but there should be no collaboration between sales departments.

  *

  The Commercial sales department should share its customers with the Commercial support department.

  *

  The Consumer sales department shares its customers with the Consumer support department.

  *

  The Commercial and Consumer support departments roll up to the same Support Director.

  *

  The sales departments will remain the Account Owner for the Accounts that they sell to.

  What is the recommended Org-Wide Sharing Default for Accounts, and how would the Architect enable proper Commercial and Consumer Sales to Support Account Sharing for this scenario?

  A. Private Account Sharing with Sharing Rules from Commercial Sales Role(s) to Consumer Support Role(s) and Consumer Sales Role(s) to Commercial Support Role(s).
  B. Private Account Sharing with Sharing Rules from Commercial support Role(s) to Commercial Support Role(s) and Consumer Sales Role(s) to Consumer Support Role(s).
  C. Read-Only Account Sharing with Sharing Rules from Commercial Sales Role(s) to Consumer Support Group(s) and Consumer Sales Role(s) to Commercial Support Groups(s).
  D. Private Account Sharing with Sharing Rules from Commercial Sales Group(s) to Commercial Support Groups(s) and Consumer Sales Group(s) to Consumer Support Group(s).
  D. Private Account Sharing with Sharing Rules from Commercial Sales Group(s) to Commercial Support Groups(s) and Consumer Sales Group(s) to Consumer Support Group(s).

• Question 209:

  Universal Health is planning to store patient notes in Salesforce. Patient notes consist of long text notes taken by a use to document phone calls with a patient.A date audit has identified that these notes can contain Personally Identifiable Information (PII) and Personal Health Information (PHI). The regulatory requirements state that this data must be encrypted at rest as well as in transit.What should the Architect do in order to make sure Universal Health stays compliant?

  A. No action is required; all Salesforce data is encrypted at rest as part of Salesforce's standard trust measures.
  B. Enable Salesforce Shield Platform Data Encryption and mark the patient notes field as encrypted.
  C. Create a new Custom Field of type "Text (Encrypted)" and move the patient notes data into the new field.
  D. Use an Apex trigger and the Apex Crypto class to encrypt patient notes as soon as they are saved to Salesforce.
  D. Use an Apex trigger and the Apex Crypto class to encrypt patient notes as soon as they are saved to Salesforce.

• Question 210:

  Which three areas should the Architect review in order to increase performance of "Record Access" and "Sharing" calculations? Choose 3 answers.

  A. Custom Object data, to ensure that no Account has more than 10,000 Custom Objects that look up to it.
  B. Opportunity data, to ensure that no Account has more than 10,000 Opportunity records that are related to it.
  C. Record ownership, to ensure that no user owns more than 10,000 Object records in the system.
  D. Apex Managed Sharing triggers, to ensure that no trigger is querying more that 10,000 Object records.
  A. Custom Object data, to ensure that no Account has more than 10,000 Custom Objects that look up to it.
  B. Opportunity data, to ensure that no Account has more than 10,000 Opportunity records that are related to it.
  C. Record ownership, to ensure that no user owns more than 10,000 Object records in the system.