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

Question : Master Detail Relationship can contain a standard object on the detail side.

1. True
2. False

Ans : 1
Exp : Master Detail relationship is the Parent child relationship. In which Master represents Parent and detail represents Child. If Parent is deleted then Child also gets deleted. Rollup summary fields can only be created on Master records which will calculate the SUM, AVG, MIN of the Child records.
Up to 2 allowed to object.
Parent field on child is required.
Access to parent determines access to children.
Deleting parent automatically deletes child.
A child of one master detail relationship cannot be the parent of another.
Lookup field on page layout is required.

" Master-Detail (1:n) - A parent-child relationship in which the master object controls certain behaviors of the detail object:
o When a record of the master object is deleted, its related detail records are also deleted.
o The Owner field on the detail object is not available and is automatically set to the owner of its associated master record. Custom objects on the detail side of a master-detail relationship cannot have sharing rules, manual sharing, or queues, as these require the Owner field.
o The detail record inherits the sharing and security settings of its master record.
o The master-detail relationship field is required on the page layout of the detail record.
o By default, records can't be reparented in master-detail relationships. Administrators can, however, allow child records in master-detail relationships on custom objects to be reparented to different parent records by selecting the Allow reparenting option in the master-detail relationship definition.
You can define master-detail relationships between custom objects or between a custom object and a standard object. However, the standard object cannot be on the detail side of a relationship with a custom object. In addition, you cannot create a master-detail relationship in which the User or Lead objects are the master.
When you define a master-detail relationship, the custom object on which you are working is the detail side. Its data can appear as a custom related list on page layouts for the other object.

Question : In a Master-Detail Relationship, ownership and access to the child record are determined by the parent record

1. True
2. False
Ans : 1
Exp : If it is master-detail relationship, you cannot specify an owner on the child record at all; the owner of the parent is automatically the owner of the children.
The first master-detail relationship you create on your junction object becomes the primary relationship. This affects the following for the junction object records:
1. Look and feel: The junction object's detail and edit pages use the color and any associated icon of the primary master object.
2. Record ownership: The junction object records inherit the value of the Owner field from their associated primary master record. Because objects on the detail side of a relationship do not have a visible Owner field, this is only relevant if you later delete both master-detail relationships on your junction object.
Division: If your organization uses divisions to segment data, the junction object records inherit their division from their associated primary master record. Similar to the record ownership, this is only relevant if you later delete both master-detail relationships.

Question : Master-Detail Relationship, the parent field on the child record can be optional.

1. True
2. False
Ans : 2
Exp : Record level access is determined by the parent, Mandatory on child for reference of parent, cascade delete (if you delete the parent, it can cascade delete the child).
Master Detail relationship is the Parent child relationship. In which Master represents Parent and detail represents Child. If Parent is deleted then Child also gets deleted. Rollup summary fields can only be created on Master records which will calculate the SUM, AVG, MIN of the Child records.
Up to 2 allowed to object.
Parent field on child is required.
Access to parent determines access to children.
Deleting parent automatically deletes child.
A child of one master detail relationship cannot be the parent of another.
Lookup field on page layout is required.

Question : What is the maximum allowed master-detail relationships per object?

1. 1
2. 2
3. Access Mostly Uused Products by 50000+ Subscribers
4. 4
Ans : 2
Exp : Master Detail relationship is the Parent child relationship. In which Master represents Parent and detail represents Child. If Parent is deleted then Child also gets deleted. Rollup summary fields can only be created on Master records which will calculate the SUM, AVG, MIN of the Child records.
Up to 2 allowed to object.
Parent field on child is required.
Access to parent determines access to children.
Deleting parent automatically deletes child.
A child of one master detail relationship cannot be the parent of another.
Lookup field on page layout is required.

Question : In a Lookup relationship, cross-object field updates and roll-up summary fields can be done.

1. True
2. False

Ans : 2
Exp : Lookup Relationship"
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.
That's correct. When you create a lookup from A to B you are creating 1:M model or Parent-Child model, which means that object A (Child) can only reference only 1 record of object B (Parent), but record from object B can be referenced from many object A records - parent can have many children.
If you were to create a formula field on the object B (Parent), how would you know which record from the object A (Child) to reference in your formula field when there might be more than 1 children? At this stage the formula fields don't have the functionality to work with children. In order to do that you might need to write an apex code (trigger or class) that will retrieve specific children records (by executing SOQL Query) and then write your own custom logic and work with the records
" Cross-object formulas that reference currency fields convert the value to the currency of the record that contains the formula. If the referenced currency field is from a custom setting, the field value isn't converted to the record's currency.
" Salesforce allows a maximum of 10 unique relationships per object in cross-object formulas. The limit is cumulative across all formula fields, rules, and lookup filters. For example, if two different formulas on opportunities reference two different fields of an associated account, only one unique relationship exists (from opportunities to accounts).
" You can't reference cross-object formulas in roll-up summary fields.
In cross-object formulas, you can't reference merge fields for objects related to activities. For example, merge fields for contacts and accounts aren't available in task and event formulas.

Question : Reports can only display child object at a time.

1. True
2. False

Ans 1

Question : A Junction object is a custom object on the detail side of TWO relationships and is used to connect objects you want to relate together and is sometimes called a "Many to Many" relationship.

1. True
2. False
Ans : 1
Exp : Lookup and Master detail relationships are one to many relationships. We can create many - to - Many relationship by using junction object. Junction object is a custom object with two master detail relationships.

Question : Which of the following statements are true about a lookup relationship?
A. A maximum of 2 relationships are allowed per object
B. A lookup relationship can span to multiple layers
C. A parent record is required for each child
D. A lookup field is not a required field
E. Access to parent determines access to children

1. A,B
2. C,D
3. Access Mostly Uused Products by 50000+ Subscribers
4. B,C
Ans :3
Exp : 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 : You cannot relate records from the same object via a relationship field.

1. True
2. False

Correct Answer : Get Lastest Questions and Answer :

Explanation: Relationships link two different objects with each other. For example, a library user
can also be a library card holder. To represent this relationship we need to assign a
customer record to a user record, this is achieved using a relationship.
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
Master-Detail relationships have the following properties.
o When two objects are in Master-Detail relationship (also called master-child
relationship) the detail/child follows the master.
o The ownership of the child record is given to the master objects owner. The
child does not have separate owner.
o The detail inherits the sharing, security settings as well as the look and feel
of the master.
o A master record is always required for storing the child record.
If the master record is deleted, the child record is also deleted.
o In a Master-Detail relationship between a standard object and custom object,
the custom object will always be the detail record.
While creating a Master-Detail relationship, there must be absolutely
no record of the object. If there are some records, create a lookup
instead. Fill the lookup fields of all the records and then convert it
into a Master-Detail.
An object can maximum of two master objects. In cases of multiple objects,
both the masters are required. If one master is deleted, the child object gets
deleted immediately.
o A Master-Detail can be multiple level deep, parent-child-grand-children.
If the master is standard object: two multiple level deep.
If the master is child object: three multiple level deep.

Question : What are the types of custom tabs?

1. Custom object tab
2. Web tab
3. Access Mostly Uused Products by 50000+ Subscribers
4. 1 and 2 only
5. 1,2 and 3

Correct Answer : Get Lastest Questions and Answer :

Explanation: Display custom object data or other Web content using custom tabs in Salesforce.
Custom Object Tabs and Web Tabs available in: Contact Manager, Group, Professional, Enterprise, Performance, Unlimited, andDeveloper Editions
Visualforce Tabs available in: Contact Manager, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions
Flexible Page Tabs available in: All Editions except Database.com

You can create any of these types of custom tabs.
" Custom Object tabs (available only at an app level and not on subtab apps) display the data of your custom object in a user interface tab. Custom object tabs look and function just like standard tabs.
" Custom Web tabs display any external Web-based application or Web page in a Salesforce tab. You can design Web tabs to include the sidebar or span across the entire page without the sidebar.
" Visualforce tabs display data from a Visualforce page. Visualforce tabs look and function just like standard tabs.
" Flexible Page tabs let you add Flexible Pages to the Salesforce1 navigation menu.
Flexible Page tabs don't work like other custom tabs in Salesforce. Once created, they don't show up on the All Tabs page when you click the plus icon ( ) that appears to the right of your current tabs. Flexible Page tabs also don't show up in the Available Tabs list when you customize the tabs for your apps.

Question : custom Application : Helps you store objects in logical and easy to access location

1. True
2. False

Correct Answer : Get Lastest Questions and Answer :
Explanation:
Explanation: The following permissions are enabled automatically when the Customize Application profile permission is enabled.
" Customize Application (Permission):
" Customize the organization using App Setup menu options.
" Edit messages and custom links;
" Modify standard picklist values;
" Create, edit, and delete custom fields;
" Create, edit, and delete page layouts (also requires the "Edit" permission for the record, for example, "Edit" on accounts);
" Set field-level security;
" Create, edit, and delete custom links;
" Edit the Lead Settings;
" Activate big deal alerts;
" Create record types;
" Set up Web-to-Case and email response rules;
" Set up Web-to-Lead and email response rules;
" Set up assignment and escalation rules;
" Set up business hours;
" Set up Email-to-Case or On-Demand Email-to-Case;
" Edit Self-Service page layouts and portal color theme (also requires the "Manage Self-Service Portal" permission to set up and maintain Self-Service settings and delete your organization's Self-Closed Case Status value);
" Set up and enable multilingual solutions;
" Set up team selling;
" Set up account teams;
" Map custom lead fields;
" Manage queues;
" Create, edit, and delete workflow rules, tasks, field updates, outbound messages, and alerts;
" Create, edit, and delete custom s-controls, custom objects, and custom tabs;
" Rename tabs;
" Manage custom apps and Service Cloud console apps;
" Create and edit public calendars and resources;
" Set up the console;
" Enable, set up, and modify the Salesforce Customer Portal;
" Set up and schedule analytic snapshots to run;
" Create communities for ideas and answers;
" Create Visualforce email templates

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

Related Questions