Which is the easiest and best way to relate a parent object with its multiple children detail objects?
A lookup field from child to parent object
A lookup field from parent to child object
A master–detail field from child to parent object
A master–detail field from parent to child object
Can you create a master–detail relation with a standard object as a parent?
Yes
No
Can you create a master–detail relation with a standard object as a child?
No
Yes
By setting the Sharing setting to Read/Write on a master–detail relation, you are:
Allowing all users who have at least read access on the parent to CRUD a child record
Allowing all users who have read/write read access on the parent to CRUD a child record
Allowing all users who have at least read access on the parent to delete a child record
Allowing all users who have at least read/write access on the parent to delete or create a child record
You can filter master records on master–detail or lookup relationship fields on the current user's profile/role:
False
True, but only if the user is a system administrator
True
Roll-up fields are created on:
The master object of a lookup relationship
The child object of a master–detail relationship
The child object of a lookup relationship
The master object of a master–detail relationship
Which are the avaible roll-up field types?
Filter, Count, Max, Sum
Sum, Subtract, Multiply, Divide
Count, Sum, Min, Max
Sum, Min, Max
You need to model a multiple relation between the Interview object and the Interview Question object so that you can have different questions for a given interview, given that the same question can be related to more than one interview. Which is the recommended solution?
User 2 lookup fields on the Interview Question object.
User 2 master–detail fields on the Interview Question object.
Create a new junction object with two master-detail fields relating to Interview and Interview Question.
Create a new junction object with two lookup fields relating to Interview Question and Interview.
Given a lookup relationship field, you can prevent child deletion by selecting the Don't allow deletion of the lookup record that's part of a lookup relationship checkbox under the What to do if the lookup record is deleted? option:
True
False; it is related to the parent record deletion
False; this option is not available on a lookup field
You can use a hierarchical relationship to:
Relate users to profiles
Relate users to roles
Relate users to users below their hierarchical level
Relate users to users above their hierarchical level
Validation rules trigger:
When conditions evaluate to true
When conditions evaluate to false
To create a validation rule that looks up to another object's record set, you use the following function:
REGEX
VLOOKUP
PRIORVALUE
You need to implement a custom validation in the ZIP code format for the country of India, so you use the following function:
REGEX
VLOOKUP
PRIORVALUE
When dealing with the PRIORVALUE function on a validation rule and a picklist field, which other function should you use to get the picklist field's value?
PREV
ISPICKVAL
VAL
VALUEOF
It is possible to set up a value on a picklist field that is not available on its defined value:
True
True, unless it is a restricted picklist
False
You can use a global value set to:
Validate picklist values
Define user access on picklist fields
Define picklist values across fields in different objects
A dependent picklist field depends on :
A master picklist or checkbox field on the same object
A master picklist or checkbox field on the parent object