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 this requirement?

Use Programmatic Sharing to share the Account with the appropriate field office.

Use Manual Sharing to share the Account with the appropriate field office.

Use Account Teams to share the Account with the appropriate field office.

Use Programmatic Sharing to share the Account with the appropriate field office.

Use Criteria-Based Sharing to share the Account with the appropriate field office.

For the Universal Containers Commercial and Consumer support departments, having access to Activities for Contacts with which they interact is important. Commercial support users should not see Consumer Accounts/Contacts and Consumer support users should not see Commercial Accounts/Contacts. Assuming the Organization-Wide Default for Activities is set to 'Controlled by Parent' what is the minimum level of Sharing access a support user would need to Accounts/Contacts to view associated Activities?

Private Account/Contact Sharing Default with a Sharing Rule for each department set to Public Read only access to Accounts/Contacts.

Private Account/Contact Sharing Default with a Sharing Rule for each department set to Public Read/Write access to Accounts/Contacts.

Private Account/Contact Sharing Default with a Sharing Rule for each department set to Private access to Accounts/Contacts.

The users need no access to Accounts/Contacts with the proper Activity Sharing Rules and Profile Permissions for the Accounts Tab.

Private Account/Contact Sharing Default with a Sharing Rule for each department set to Public Read only access to Accounts/Contacts.

Universal Containers wants to create a way to store sensitive Invoice Data in Salesforce. A User who owns an Account should not see every Invoice, but only invoices that they or their subordinates own. Which two features should be considered during this solution implementation?Choose 2 answers.

Deploy the Relationship between Accounts and the Invoices Object as Master-Detail.

Ensure that the Organization-Wide Default sharing for Invoices is set to Private.

Deploy the Relationship between Accounts and the Invoices Object as Master-Detail.

Ensure that the Organization-Wide Default sharing for Invoices is set to Private.

Create a Workflow that populates the Invoice sharing object upon Insert.

Deploy the Relationship between Accounts and the Invoices Object as Lookup.

Universal Containers has a strict security model enforced through object, field, and row-based security mechanisms. The Architect would like to ensure the security model is being thoroughly tested using Apex automated tests. Which three considerations should be made when using the runAs() method to design Apex until tests?

runAs() does not enforce user permissions or field-level permissions in test classes

runAs() can be used inside of test classes to validate record-level security

runAs () counts towards total DML statements issued within transaction

runAs() does not enforce user permissions or field-level permissions in test classes

runAs() can be used inside of test classes to validate record-level security

runAs() can be used inside of test classes to validate field-level permissions

runAs() can be used outside of test classes to bypass record-level security

runAs () counts towards total DML statements issued within transaction

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

Custom Object data, to ensure that no Account has more than 10,000 Custom Objects that look up to it.

Opportunity data, to ensure that no Account has more than 10,000 Opportunity records that are related to it.

Record ownership, to ensure that no user owns more than 10,000 Object records in the system.

Custom Object data, to ensure that no Account has more than 10,000 Custom Objects that look up to it.

Opportunity data, to ensure that no Account has more than 10,000 Opportunity records that are related to it.

Record ownership, to ensure that no user owns more than 10,000 Object records in the system.

Apex Managed Sharing triggers, to ensure that no trigger is querying more that 10,000 Object records.

Which three capabilities are available with Enterprise Territory Management? Choose 3 answers

Integration with Collaborative Forecasting

Assignment of Territory on Opportunities

Create a public group with Territory

Share a report or dashboard folder with a Territory

Integration with Collaborative Forecasting

Assignment of Territory on Opportunities

Which are two valid use cases for programmatic sharing?Choose 2 answers.

An external system manages user record access.

Native sharing functionality does not meet requirements.

An external system manages user record access.

Frequent user ownership changes based on re-alignments.

Native sharing functionality does not meet requirements.

Setting user ownership for standard and custom objects.

The Collections department at Universal Containers uses Salesforce to track its efforts. All Invoices and Invoice Line Items are stored in Salesforce. Invoice Line Item object details, such as Quantity and Extended Amount, should be summarized at the Invoice Object level, and all users who can see a given invoice should always see all invoice line items. Without leveraging Apex code, how should an Architect create the relationship between the Invoice object and the Invoice Line Item Object?

The Invoice Line Item Object should have a Master-Detail to the Invoice Object

The Invoice object should have a Master-Detail to the Invoice Line Item Object

The Invoice Line Item Object should have a Lookup to the Invoice Object

The Invoice Object should have an inner joint to the Invoice Line Item Object

The Invoice Line Item Object should have a Master-Detail to the Invoice Object

Universal Containers wants to store Payment Term Details on the Account object, but the fields should only be visible on certain record types and for certain user profiles.How can a System Administrator quickly determine which user profiles, page layouts, and record types include certain fields?

Use the Field Accessibility Viewer for the fields in question

Log in as each user profile and view the Account Page Layouts.

Use the Field Accessibility Viewer for the fields in question

Universally require the field at the field level.

Click the Field-Level Security for the field on each Profile.

A sales representative at Universal Containers needs assistance from specific product managers when selling certain deals. Product managers do not have access to opportunities they don't own, as the sharing model is Private, but need to gain access when they are assisting with a specific deal. How can an Architect accomplish the requirement?

Enable opportunity teams and allow users to add the product manager.

Create a sharing rule to allow the product manager to access the opportunity.

Enable opportunity teams and allow users to add the product manager.

Enable account team and allow users to add the product manager.

Use similar opportunities to share opportunities related to the product manager.

Universal Container has a set of Account management users that should only see accounts once the account becomes a customer. The type field on the Account identifies whether the account is a prospect, customer, partner, or other. Which two methods could an Architect use to enable this sharing requirement, assuming a private sharing model for accounts? Choose two:

Institute a business process that calls for the account manager to be added to the account team once the account becomes a customer

Create a criteria-based sharing rule that shares the account to the account management group when the type is customer

Create a public list view, where accounts of type customer are included and share the list view with account management public group

Institute a business process that calls for the account manager to be added to the account team once the account becomes a customer

Create an account sharing rule that shares all accounts owned by sales to be shared with account management roles and subordinates

Create a criteria-based sharing rule that shares the account to the account management group when the type is customer

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?

Remove the 'Opportunity Delete' Permission from the Sales Team's User Profile in the Object Permissions.

Remove the Delete button from the Opportunity Page Layout and Record Type settings.

Create a Validation Rule that checks the User's Profile before allowing the Is Deleted flag to be set to True.

Override the Standard button with a Visualforce Page that warns them that they do not have permission to delete.

Remove the 'Opportunity Delete' Permission from the Sales Team's User Profile in the Object Permissions.

Universal Containers has created a custom object to store highly confidential client relationship data with Private sharing settings. Which two options would an Architect choose to ensure access only to the record owner and the administrator?Choose 2 answers.

Disable 'Grant Access Using Hierarchies.'

Disable the 'View All' permission on all other profiles.

Disable 'Grant Access Using Hierarchies.'

Disable the 'Create' permission on all other profiles.

Disable the 'Read' permission on all other profiles.

Disable the 'View All' permission on all other profiles.

A user at Universal Containers would like to give access to a Report folder to someone else in the organization.Which two access permissions should the user have to support this requirement?Choose 2 answers.

The 'Manage Reports in Public Folders' Profile permission.

The 'Manager' Report folder permission.

The 'Viewer' Report folder permission

The 'Editor' Report folder permission.

The 'Manage Reports in Public Folders' Profile permission.

The 'Manager' Report folder permission.

Which users have access to Opportunity records owned by an external user, assuming no other changes to the sharing model have been implemented?

The record owner and any user above the external user in the role hierarchy.

The record owner and any user below the external user in the role hierarchy.

The record owner and all internal users.

Universal Containers has junction object called 'Job Production Facility', with 2 master-detail relationships to the Job and Production Facility custom objects. Both master records have a private sharing model.What statement is true if a user's profile allows access (Create/Read) to the Job, but no access to the Production Facility Object?

The user will not be able to see the junction object records or the field values.

The user will be granted read access to the Production Facility record

The user will see the junction object and the link to the Production Facility.

The user will see the junction object but not the link to the Production Facility.

The user will not be able to see the junction object records or the field values.

A dummy user at Universal Containers owns more that 10,000 lead records. The system assigned all these leads to a dummy user. This is causing performance issues whenever role hierarchy changes. Which two options should be recommended to improve performance?Choose 2 answers.

Assign ownership to a small number of users.

Do not assign a role to the dummy user.

Assign ownership to a small number of users.

Add the dummy user into a public group.

Add the dummy user to the bottom of the role hierarchy.

Do not assign a role to the dummy user.

Universal Containers has just deployed a change to its role hierarchy. A manager is reporting that their staff can now see Accounts that they do not own and should not have access to. How should the Architect troubleshoot?

While logged in as the one of the Staff members, navigate to a sample account and use the Sharing button to determine who has access.

While logged in as the System Administrator, use the Field Accessibility Viewer to view a matrix of who has access to Accounts.

While logged in as the one of the Staff members, navigate to a sample account and use the Sharing button to determine who has access.

While logged in as the one of the Staff members, navigate to their user record and inspect their profile and role membership.

While logged in as the System Administrator, use the Field Accessibility Viewer to view a matrix of who has access to Accounts.

Which two options can help mitigate the risks of import failures associated with large-volume bulk data loads?Choose 2 answers.

Group records by ParentID within a batch.

Universal Containers has a custom Job object with a private sharing model. Based on the size and location of the Job, different teams must have access to edit the specific Job record. To support this requirement, Apex Managed Sharing has been implemented to share records with the required users. Since the teams change frequently, managed sharing recalculations need to be manually run frequently. What can the Architect do to optimize this process?

Create public groups for each team, and share the jobs with the groups instead of users.

Change the sharing model on the Job object to Public Read/Write.

Create a scheduled job to automatically run the sharing recalculations on a nightly basis.

Create public groups for each team, and share the jobs with the groups instead of users.

Create a custom Visualforce page to edit the jobs and specify Without Sharing on the controller.

Which three advanced tools can Salesforce enable for large-scale role hierarchy realignments in organizations with large data volumes?Choose 3 answers.

Parallel Sharing Rule Recalculation

Universal Containers would like to create a custom team solution that can be used on a custom Loan object. The following requirements must be met:The Loan custom object should be set to Private in the Org-Wide Defaults.Any user added to the Custom Team object should have Read Only access to the corresponding Loan record. If the Custom Team record is marked as 'Primary' then the corresponding user should have Read/Edit access to the corresponding Loan record.Which two methods will allow the Architect to meet the requirements?Choose 2 answers.

Create a criteria-based sharing rule on the Loan object that will share the Loan record with the appropriate user in the Custom Team object.

Create an owner-based sharing rule on the Custom Team object that will share the Loan record to the owner of the Custom Team record.

Create a custom trigger on the Custom Team object that inserts or updates records in the Loan_share object.

Create a criteria-based sharing rule on the Loan object that will share the Loan record with the appropriate user in the Custom Team object.

Create Apex Sharing Reasons on the Loan object to identify the reason the Loan record was share.

Create an owner-based sharing rule on the Custom Team object that will share the Loan record to the owner of the Custom Team record.

Universal Containers created a custom object called Defect and would like to enable the Sharing button on the Defect page layout to share the records manually to other users in the organization. In which scenario will the Sharing button appear?

The Sharing model is either Private or Public Read only.

The Sharing button always appears.

The Sharing model is Public Read/Write.

The Sharing model is Public Read/Write/Transfer.

Universal Containers (UC) works with a dealer network to sell their products. There are approximately 5,000 dealers that do business with UC and UC has purchased a Partner Community to interact with each of their dealers on Opportunities. Each dealer is structured so that there are a group of managers who will oversee a larger team of agents. UC would like to set the Organization-Wide Defaults to Private for the Opportunity object, both internally and externally. Within each dealer, there are a few agents called Lead Agents who should be able to see the Opportunities for all of the other Agents at the dealer. What is the optimal solution for an Architect to recommend?

Grant Super User access to the Lead Agents as part of the Community user setup.

Add a Sharing Set that shares Opportunities to the Lead Agent based on the Lead Agents Account.

Build an Apex Managed Sharing rule that will assign specific Opportunities to Lead Agents.

Grant Super User access to the Lead Agents as part of the Community user setup.

Create a Sharing Rule to share opportunities to the owner's manager's role and below.

Universal Container is creating a custom VF page to allow user to edit contact records. The developer has used an apex:outputField for the Phone field on the contact obj. What is the expected behavior if a user without FLS accesses the VF page?

The field is automatically removed from the page

The user encounters an error while saving the record

The field is automatically removed from the page

The output field is visible to user

The user is able to enter a value into the phone field

Universal Containers has a private sharing model on Accounts. Apex Managed Sharing is required to share certain account records with all users who are assigned to a specific Role in the Role Hierarchy. What should be the recommended way for the Architect to implement this?

Create an AccountShare record associated to a public group containing the Users in the Role.

Create an AccountShare record associated to each user who is assigned to the Role.

Create an AccountShare record associated to the required Role.

Create an AccountShare record associated to a public group containing the Role.

Universal Containers is implementing a community of High-Volume Community users. Community users should be able to see records associated to their Account or Contact record. The Architect is planning to use a Sharing Set to provide access to the records. When setting up the Sharing Set, certain objects are not available in the list of Available Objects. Which two reasons explain why an object is excluded from the list of Available Objects in a Sharing Set?

The object's Organization-Wide sharing setting is set to Public Read/Write.

The custom object does not have a lookup to Accounts or Contacts.

The object is a custom object, and therefore not available for a sharing set.

The object's Organization-Wide sharing setting is set to Public Read/Write.

The object's Organization-Wide sharing setting is set to Private.

The custom object does not have a lookup to Accounts or Contacts.

What should the Architect do to ensure Field-Level Security is enforced on a custom Visualforce page using the Standard Lead Controller?

Nothing; Field-Level Security will automatically be enforced.

Use the 'With Sharing' keyword on the Standard Lead Controller.

Nothing; Field-Level Security will automatically be enforced.

Use the {!Schema.sObjectType.Lead.fields.isAccessible()} expression

Use the Schema.SObject.Lead.isAccessible() method.

In order to comply with regulatory requirements, Universal Health must encrypt all Personally Identifiable Information (PII), both while it is being transmitted over the network and while it is at rest. Universal Health has completed a data audit and has determined that 12 fields on the contact record can contain PII, including the contact name and several other standard fields. Universal Health would like the fields to remain accessible in Salesforce. Which two options does Universal Health have to maintain compliance?Choose 2 answers.

Update the field type of each of the 12 fields to 'Text (Encrypted)' so that they are encrypted at rest.

Enable Salesforce Platform Encryption and select the 12 contact fields to be encrypted.

Implement a custom Apex trigger to automatically encrypt the PII data using the Apex Crypto Class.

Update the field type of each of the 12 fields to 'Text (Encrypted)' so that they are encrypted at rest.

Enable Salesforce Platform Encryption and select the 12 contact fields to be encrypted.

Use an external, third party encryption service to encrypt PII before it enters Salesforce.

Salesforce Certified Sharing and Visibility Architect Practice Test 5

By Viewer Access you can see the data in a report or dashboard, but you can't make any changes, except by cloning it into a new report or dashboard.

Become a Premium Member for full access

Unlock Premium Member

Salesforce Certified Sharing and Visibility Architect Practice Test 5

Question

Salesforce Certified Sharing and Visibility Architect Practice Tests

Practice Tests