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

Question : Many-to-many relationship is created using?

1. Any number of master-detail relationships
2. One master-detail relationships
3. Two master-detail relationships
4. 1 and 2
5. All 1, 2 and 3

Correct Answer 3 :
Explanation: To create multilevel master-detail relationships, you need the "Customize Application" user permission.
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.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 reparentingoption in the master-detail relationship definition.You can have up to three custom detail levels.Standard objects can't be on the detail side of a custom object in a master-detail relationship.An object can appear once in multilevel master-detail relationships. For example, a subdetail object in one multilevel master-detail relationship can't also be the owner of the master object in another multilevel master-detail relationship. A subdetail object can't also be the master object of the subdetail object's detail object. Multilevel master-detail relationships do not support division transfers. You can't create a master-detail relationship if the custom object already contains data. You can, however, create the relationship as a lookup and then convert it to master-detail if the lookup field in all records contains a value. Converting relationships from lookup to master-detail, or from master-detail to lookup behaves the same as for two-object master-detail relationships. That is, the two linked objects in the detail-subdetail1, or subdetail1-subdetail2 relationship have the same conversion limits as the master-detail relationship.
Roll-up summary fields work as in two-object master-detail relationships. A master can roll up fields on detail records; however, it can't directly roll up fields on subdetail records. To achieve this, the detail record must have a roll-up summary field for the field on the subdetail record, allowing the master to roll up from the detail's roll-up summary field. You can use multilevel master-detail relationships in custom report types. The Allow Reports checkbox must be checked when you create the custom object. Custom report types created for multilevel master-detail relationships count towards the organizations custom report type limit and no reports are generated if this limit is exceeded. Custom junction objects can't have detail objects. That is, a custom junction object can't become the master object in a multilevel master-detail relationship. You can't delete a custom object if it is on the master side of a master-detail relationship. If you delete a custom object that is on the detail side of a master-detail relationship, the relationship is converted to a lookup relationship. Deleting a detail record moves it to the Recycle Bin and leaves the master record intact; deleting a master record also deletes related detail and subdetail records. Undeleting a detail record restores it, and undeleting a master record also undeletes related detail and subdetail records. However, if you delete a detail record and later, separately, delete its master record, you cannot undelete the detail record, as it no longer has a master record to relate to. As a best practice, don't exceed 10,000 child records for a master-detail relationship. Many-to-Many Relationships Junction object records are deleted when either associated master record is deleted and placed in the Recycle Bin. If both associated master records are deleted, the junction object record is deleted permanently and can't be restored. Sharing access to a junction object record is determined by a user's sharing access to both associated master records and theSharing Setting option on the relationship field. See Custom Object Security Overview. For example, if the sharing setting on both parents is Read/Write, then the user must have Read/Write access to both parents in order to have Read/Write access to the junction object. If, on the other hand, the sharing setting on both masters is Read-Only, a user with Read-Only rights on the master records would have Read/Write access to the junction object. In a many-to-many relationship, a user can't delete a parent record if there are more than 200 junction object records associated with it and if the junction object has a roll-up summary field that rolls up to the other parent. To delete this object, manually delete junction object records until the count is fewer than 200. The first master-detail relationship you create on your junction object becomes the primary relationship. This affects the following for the junction object records: " Look and feel: The junction object's detail and edit pages use the color and any associated icon of the primary master object. " 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. The second master-detail relationship you create on your junction object becomes the secondary relationship. If you delete the primary master-detail relationship or convert it to a lookup relationship, the secondary master object becomes primary. Roll-up summary fields that summarize data from the junction object can be created on both master objects. Formula fields and validation rules on the junction object can reference fields on both master objects. You can define Apex triggers on both master objects and the junction object. A junction object can't be on the master side of another master-detail relationship. You can't create a many-to-many self relationship, that is, the two master-detail relationships on the junction object can't have the same master object.

Question : The object used in many-to-many relationship is called as?

1. Joining object
2. Junction object
3. Joint object
4. Multi Joint object

Correct Answer 2 :

Explanation: A many-to-many relationship between two objects is a relationship in which an object A can have many child objects B, while object B can have multiple child objects A A real world example is the relationship between student and teacher. A student can be taught by multiple teachers while a teacher can teach multiple students. Normally lookup and master child relationships are 1:N, however, a small trick can create a many-to-many relationship on Force.com. The trick to create the master child object is as follows: o First create a junction object, which contains a link to two master-objects o Create the name field as auto-number in the junction object Some properties of the junction objects are as follows. o The junction object identifies the first master as the primary master.
It uses the look and feel of the primary master. o If any master record is deleted, the junction record is automatically deleted.

Master-Detail relationships are more tightly coupled relationships. For example, the relationship between the customer and the card in the library management will
be Master-Detail. Where the customer is the master and the card is the child in the relationship. 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. 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.

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. 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 : Which are the types of Custom Tabs?

1. Custom object tab
2. Web tab
3. Visualforce tab
4. Both 1 and 2
5. All 1 , 2 and 3

Correct Answer : 5

Explanation: A custom tab is used to display object data or other contents embedded in the
application. The custom tab has a unique tab style. We can choose the color and icon
for the tab.
We cannot create tabs for standard objects. The Standard Object Tabs can be
hidden/ shown and added to any custom application. There are three types of
custom tabs:
o Custom Object Tabs:
These tabs display the custom object data.
They provide the options to create, read, update, and delete
(also called CRUD rights) an object.
The plural name of the object is given to the tab by default.
The buttons of respective operations are visible depending on
the user rights of the object.

Web tabs:
We can display any external website using the web tab.
The web tab is useful if we want to show the external web-based
applications (for example, Google, Evernote) inside Salesforce.
o Visualforce tabs:
Tabs can also be made in rich UI and complex coding using
Visualforce and HTML.

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

Related Questions