Examen IV

Roll up summary field and Cross object formula field can be created only for master detail
relationship.

Sharing rules can be more restrictive than the Organization Wide Default.

'Status' is a picklist of the Account object having value 'Open' or 'Closed'. It is possible to create a
sharing rule to share only those Accounts whose 'Status' is 'Open'.

Organization wide default (OWD) is the first check used for determining access to records a user
does not own

Time-based workflow is NOT applicable every time a record is created or edited

Is used for tracking changes to configuration of Salesforce CRM Setup Audit Trail

Checkbox can be controlling field only and not a dependant field.

Multi select picklist can be dependant field only and not a controlling field

External id can be created for field of type text, number or email.

In Developer Edition, Validation rule for the 'Account Site' field (field of type text) of Account object
is, ISCHANGED( Site ) && OwnerId < > $User.Id to make sure that if the 'Account Site' field has
been modified and the user is not the owner of the Account record, then an error message would
be shown. The System Administrator has Read All, Modify All permission for the Account record.
So the System Administrator will be able to modify the 'Account Site' field of the

have all a lifecycle:
Opportunities have Stage picklist and Sales Processes based on the values in this Stage picklist.
Leads have Lead Status picklist and Lead Processes based on the values in this Lead Status
picklist. Cases have Status picklist and Support Processes based on the values in this Status
picklist. Solutions have Status picklist and Solution Processes based on the values in this Status
picklist. Quotes, Contracts have Status picklist but no processes associated to limit a

OWD of Account is private then OWD of Opportunity can be private or public read-only or public
read/write.

Apex sharing reasons are available for standard and custom objects.

Since Apex sharing reasons are not available for standard objects, so sharing individual records of
standard objects is not possible.

OWD of Associate must be public read/write. So sharing is not required for any Associate
record. So the Sharing button does not show up.

The OWD of the related opportunities, cases or contacts could be private or public readonly.
So there is scope for sharing the account.

If a record of Associate custom object has been shared using an Apex Sharing Reason, then that
Apex Sharing Reason cannot be deleted until the sharing of that record is changed to use some
other Apex Sharing Reason.

Until an Apex Sharing Reason is created, a record of a custom object cannot be shared manually
on a one-off basis

Once a sharing rule has been created based on owner, then it can be modified to make it a
sharing rule based on criteria.

Automatic case escalation can be disabled.

Escalation Rules and Auto-Response Rules are available only for cases.

OWD of child is always determined by OWD of parent

When upserting record using Apex Data Loader for an object that has an external id field, if the
value for this external id field is not provided in the csv file or while mapping fields from the csv file
to the Salesforce object fields, then the upsert will always fail as the external id is a required field

The statement 'OWD or sharing rule can make access level lesser restrictive but not more
restrictive' is valid only if the user has Edit permission at the profile level for that object.
Edit permission at profile level means that the user can edit records created by him of that object.

'Modify all' if checked at the profile level, always overrides the OWD setting.

'View All' has been checked at the profile level for a custom object Position. OWD is private of the
Position object. A user will be able to view Position records owned by other users