Have an account?
Global Insurance has created a custom object to gather feedback from employees about working at the company. The feedback should be private so that employees cannot see each other's feedback. Only the CEO should be able to view the feedback from all the employees. How should the application be configured to meet this requirement?
This is not possible as sharing settings cannot be configured for custom objects
Change the organization-wide default setting for the Feedback object to 'Private', enable 'Grant Access Using Hierarchies' for the object, and create a sharing rule for the CEO user
Change the organization-wide default setting for the Feedback object to 'Private', disable 'Grant Access Using Hierarchies' for the object, and create a sharing rule for the CEO role
Change the organization-wide default setting for the Feedback object to 'Public Restricted' and set a sharing exception for the CEO user
How would a Salesforce Administrator ensure that records of a particular standard object are visible only to the record owner, to his manager, and the executives?
Set the organization-wide default setting for the object to 'Private'
Enable the 'Grant Access Using Hierarchies' checkbox for the object
Define a Profile List
Define a Role Hierarchy
Star Enterprises would like their Salesforce instance to be configured so that any account record which has the 'Type' field set to 'Internal' is visible to all users. The OWD setting for the account object is set to Private. The associated contracts and opportunities also need to be visible to everyone. How many sharing rules would be needed for this requirement?
A developer wants to specify the objects that an individual or group of users can access. Which of the following security settings can help him achieve his goal?
A custom application is used to record staff details. The 'Date of Birth' custom field on the 'Staff' object is considered private and should only be visible to HR users. What can be used to prevent a non-HR user from accessing this data?
The Organization-Wide Default setting for the Contact object is set to 'Public Read/Write'. Sam is asked to ensure that sales representatives should not be able to edit Contact records. What should Sam do here?
Grant only 'Read' access to Contact in the profile of sales representatives
Grant only 'Read' access to Contact in the role of sales representatives
Create a Contact sharing rule
Change the existing Organization-Wide Default setting for Contact to 'Public Read Only'
Sam is in the process of designing the Salesforce data model for Pacific Travels. He needs to be able to associate multiple 'Booking Detail' records to a single Contact record. In addition, the 'Booking Detail' records are of legal importance, which is why they should not be deleted, even if the associated Contact is deleted. How should Sam design the data model for this requirement?
Define a lookup relationship field on the 'Contact' object that references the 'Booking Detail' object
Define a lookup relationship field on the 'Booking Detail' object that references the 'Contact' object
Define a master-detail relationship field on the 'Booking Detail' object that references the 'Contact' object
Define a master-detail relationship field on the 'Contact' object that references the 'Booking Detail' object
The Sales team at Global Containers has created a list of opportunities which need to be imported to Salesforce. There are about 200 records in the import file. Which of the following solutions should be used for the import?
Use Data Loader
Manually enter the records
Use Data Import Wizard
Use an AppExchange solution
John, the Salesforce administrator at Global Consulting, is required to design the data model for project and employee data. A project can have many employees working on it, and an employee can work on multiple projects. What design should John propose?
Create a lookup relationship from Project object to Employee object
Create a many-to-many relationship by creating a new junction object between Project and Employee objects
Create a master-detail relationship from Project object to Employee object
Create a lookup relationship from Employee object to Project object
Worldwide Containers would like to create quotes related to opportunities. What would be the recommended data model to meet this requirement?
Create a Quote custom object and link it to the Opportunity standard object
Install an AppExchange product to add custom Quote objects
Use the standard Opportunity and Quote objects.
Extend the Opportunity object by including custom fields for Quotes