Salesforce Developer Certifications Questions and Answers (Dumps and Practice Questions)

Question : If there is a custom validation rule on a custom object Position for the custom text field Location to
make sure that this field is not left blank, then what are the various ways of bypassing this
validation rule?

A. Deactivate the validation rule.
B. Provide a value to this field in the before insert/update trigger on the Location object if this field has been left blank.


1. A
2. B
3. Access Mostly Uused Products by 50000+ Subscribers
4. None of A and B

Correct Answer : Get Lastest Questions and Answer :





Question : What are details of order of execution among validation rules, auto-response rules, assignment
rules, triggers, escalation rules, workflow rules etc.?

1. System validation rules are executed like data type checking of the field values. So error for text value in numeric field etc.
2. Before triggers execute.
3. Access Mostly Uused Products by 50000+ Subscribers
any such field which was left blank while creating the record & the custom validation rule won't give error then.




1. 1,2,3
2. 2,3,1
3. Access Mostly Uused Products by 50000+ Subscribers
4. 1,3,2



Correct Answer : Get Lastest Questions and Answer :





Question : For which objects quick create is available?

1. Lead
2. Account
3. Access Mostly Uused Products by 50000+ Subscribers
4. Forecast
5. Opportunity


1. 1,2,3
2. 2,3,4
3. Access Mostly Uused Products by 50000+ Subscribers
4. 2,3,4,5
5. 1,2,3,4,5

Correct Answer : Get Lastest Questions and Answer :

Related Questions

---

Question :

1. Opportunities have Stage picklist and Sales Processes based on the values in this Stage picklist.
2. Leads have Lead Status picklist and Lead Processes based on the values in this Lead Status picklist.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Solutions have Status picklist and Solution Processes based on the values in this Status picklist.
5. Quotes, Contracts have Status picklist but no processes associated to limit


1. 1,2,3,4
2. 2,3,4,5
3. Access Mostly Uused Products by 50000+ Subscribers
4. 1,2,3,4,5
Ans : 4
Exp :




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

1. True
2. False
Ans : 2
Exp :



Question : If OWD of Opportunity is set to private, then which all opportunities can a user view?

1. Opportunities owned by the user.
2. Opportunities shared with the user using Opportunity Sharing Rule.
3. Access Mostly Uused Products by 50000+ Subscribers
Access Using Hierarchies' is always checked for standard objects. It cannot be unchecked.
4. Opportunities on which this user has been added as an Opportunity Team member

1. 1,2,3
2. 2,3,4
3. Access Mostly Uused Products by 50000+ Subscribers
4. 1,2,3,4
Ans : 4
Exp : As OWD of Opportunity is set to private, so any user will be able to view only these
opportunities:
1. Opportunities owned by the user.
2. Opportunities shared with the user using Opportunity Sharing Rule.
3. Access Mostly Uused Products by 50000+ Subscribers
Access Using Hierarchies' is always checked for standard objects. It cannot be unchecked.
4. Opportunities on which this user has been added as an Opportunity Team member



Question : Once a sharing rule has been created to share Account records with Public Group A with
read/write access to the shared accounts, then this sharing rule can be modified to share the
Account records with Public Group B with read-only access.



1. True
2. False





Question : Apex sharing reasons are available for standard and custom objects.

1. True
2. False


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

1. True
2. False


Question : The 'Sharing' button has been added to the page layout of 'Associate' custom object. On any
Associate record, the Sharing button is not visible for sharing that record using an Apex Sharing
Reason.

1. True
2. False



Question : 'Sharing' button has been added to the page layout of the 'Account' object. OWD of account is
public read/write. On any Account record, the Sharing button is still visible for sharing that record
using an Apex Sharing Reason.



1. True
2. False





Question : 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.

1. True
2. False