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

Question : Identify the correct statements about dependent picklists
A. Standard picklists can be controlling fields but not dependent fields
B. The maximum number of values allowed in a controlling field is 400
C. Before defining a dependency, you should ensure that your picklist has at least 1 value
D. A custom multi-select picklist can be set at the controlling field for a dependent field
E. If a field represents both a controlling field

1. A,B,C
2. C,D,E
3. Access Mostly Uused Products by 50000+ Subscribers

4. B,D,E
5. A,C,E



Correct Answer : Get Lastest Questions and Answer :

Exp: Use dependent picklists to help your users enter accurate and consistent data. A dependent picklist is a custom or multi-select picklist for which the valid values depend on the value of another field, called the controlling field. Controlling fields can be any picklist (with at least one and fewer than 300 values) or checkbox field on the same record.
For example, you can define a Reason custom picklist on opportunities and make its valid values depend on the value of the Stage picklist as follows:
" If Stage is Closed Won, the valid values for Reason are Superior features or Lower price.
If Stage is Closed Lost, the valid values for Reason are Inferior features, Higher price, or Company viability.

Consider the following when using dependent picklists in Visualforce pages:
" You can mix controlling and dependent fields across various field types, such as picklists, multi-picklists, radio buttons, and checkboxes.
" There's a limit of 10 dependent picklist pairs per page. This is totalled across all objects. Thus, you could have five dependent picklists on Account, and five on Contact, but no more. This is hard limit and cannot be increased. However, you can repeat the same pair of dependent picklists, such as in an iterative tag like apex:repeat, without counting more than once against your limit.
" If the user viewing the page has read-only access to the controlling field, a dependent picklist might not behave as expected. In this case, the dependent picklist shows all possible values for the picklist, instead of being filtered on the read-only value. This is a known limitation in Visualforce.
" Pages must include the controlling field for a dependent picklist. Failing to include the controlling field on the page causes a runtime error when the page displays.








Question : What is the maximum number of lookup fields you can have in a single object?


1. 10
2. 25
3. Access Mostly Uused Products by 50000+ Subscribers
4. 1000
5. No limit


Correct Answer : Get Lastest Questions and Answer :

Explanation: Lookup relationships are loosely coupled relationships. For example, a card of
a member can have multiple penalties (fines) on it. The penalties on the card are
shown at the bottom of the card in a list.
Lookup relationships have the following properties:
o The two objects records have no relationship dependencies on each other
o The lookup field value is optional
o Updating and deleting the child record has no effect on the parent
Both objects have their own owners and sharing rules
o A record can have 25 lookup fields with 25 different objects
This type of relationship links two objects together,
Up to 25 allowed for object
Parent is not a required field.
No impact on a security and access.
No impact on deletion.
Can be multiple layers deep.
Lookup field is not required.





Question : If a lookup field is optional, what actions can you define for the field if someone deletes a referenced lookup record? (Select all that apply)
A. Clear the value of this field
B. Delete all records which contain this reference
C. Don't allow deletion of the lookup record that's part of a lookup relationship
D. Delete this record also


1. A,B,C
2. C,D,E
3. Access Mostly Uused Products by 50000+ Subscribers

4. B,D,E
5. A,C,D




Correct Answer : Get Lastest Questions and Answer :


Explanation: Delete or Deactivate Lookup Filters
Available in: All Editions except for Database.com.

User Permissions Needed
To define lookup filters: "Customize Application"
1. Navigate to the object that contains the relationship field.
o For standard objects, from Setup, click Customize, select the appropriate object, and click Fields.
o For custom objects, from Setup, click Create | Objects, and select one of the custom objects in the list.
2. Scroll to the Custom Fields and Relationships related list.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Click Edit.
5. To deactivate the lookup filter, deselect Enable this filter, then click Save.
Deactivating a lookup filter preserves the lookup filter configuration but:
o Prevents it from applying to the relationship field
o Prevents it from impacting the cross-object references limit
o Removes it as a dependency for fields referenced in the lookup filter criteria
6. To delete the lookup filter, click Clear Filter Criteria, then click Save.
Deleting a lookup filter permanently removes it. You can't recover deleted lookup filters.

Related Questions

---

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

1. True
2. False


Question : Which of the following are the record access levels?


1. Read only
2. Read/write
3. Full access
4. 1 and 3
5. All 1,2 and 3



Question : Which of the following values are for Organization wide defaults?

1. Public read only
2. Public read/write
3. Private
4. Only 2 and 3
5. All 1,2 and 3


Question : Apex sharing reason can be used for

1. Manual sharing of records or one-off sharing which is done on a record basis
2. General sharing rule
3. Both of above



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

1. True
2. False



Question : Organization wide default (OWD) and sharing rules are applied at the


1. profile level
2. object level
3. record level
4. 1 and 2
5. 2 and 3