Salesforce Developer Certifications Questions and Answers (Dumps and Practice Questions)
Question : Which are the ways to mass delete records?
1. Using Apex Data Loader
2. from Setup -> Data Management -> Mass Delete Records
3. Access Mostly Uused Products by 50000+ Subscribers
4. Not available
Correct Answer : Get Lastest Questions and Answer :
Exp: Apex data loader
The Apex data loader is a .net utility used to upload data to the organization. We
can load any object that has API_Access. Unlike other tools, the data loader is not a
cloud-based tool, but a desktop utility built for systems running on windows. Some
features of the data loader are:
o The Apex data loader is available in unlimited edition, enterprise edition,
and developer edition orgs
o It supports the CSV (Comma Separated Value) format to load data and
export data
o It is a useful tool to backup and archive your office data
o The data loader also runs on command line
Some salient features of the data loader are listed as follows:
o The Apex data loader is an API-based tool used to load Salesforce data
o We can load more than 50,000 records using it and also schedule data loads
o Data can be exported and mass deleted
o The Apex data loader can run from the command line
o There is no limit for 50,000 records
o We can export data for backup and mass-delete
o We can also schedule the data loading at regular intervals
o Data can be imported and exported using CSV and JDBC
Mass delete record and delete all data
Some of the other data operations include cleaning the organization database using
the mass delete wizard and deleting all data.
Warning: Delete all data has no undo option, it formats the organization.
The mass delete wizard helps to clean the data from the organization
Question : Which are the Standard profiles?
A. System Administrator B. Contract Manager C. Solution Manager D. Marketing User E. Standard User F.Read Only
1. A,B,C,D
2. A,C,D,E
3. Access Mostly Uused Products by 50000+ Subscribers
4. A,B,C,D,E
5. A,B,C,D,E,F
Correct Answer : Get Lastest Questions and Answer :
Exp: Every organization includes standard profiles. In Enterprise, Unlimited, Performance, and Developer Edition, you can use standard profiles or create, edit, and delete custom profiles. In organizations where you can't create custom profiles (such as Contact Manager, Group, and Professional Edition), you can assign standard profiles to your users, but you can't view or edit them. The following table lists the most-commonly used permissions in standard profiles. To view all the enabled user permissions in a standard profile: 1. From Setup, click Manage Users | Profiles. 2. Select a standard profile. 3. Depending on your profile user interface, do one of the following: " Enhanced profile user interface: From the Profile Overview page, click App Permissions. After viewing the app permissions, click the down arrow next to the App Permissions name and select System Permissions. " Original profile user interface: Scroll to the Administrative Permissions and General User Permissions lists.
Profile Name Available Permissions
System Administrator : Can configure and customize the application. Has access to all functionality that does not require an additional license. For example, administrators cannot manage campaigns unless they also have a Marketing User license. Can manage price books and products. Can edit any quota, override forecasts, and view any forecast. Standard Platform User : Can use custom Force.com AppExchange apps developed in your organization or installed from AppExchange. In addition, can use core platform functionality such as accounts, contacts, reports, dashboards, and custom tabs. Standard Platform One App User : Can use one custom AppExchange app developed in your organization or installed from AppExchange. The custom app is limited to five tabs. In addition, can use core platform functionality such as accounts, contacts, reports, dashboards, and custom tabs. Standard User : Can create and edit most major types of records, run reports, and view the organization's setup. Can view, but not manage, campaigns. Can create, but not review, solutions. Can edit personal quota and override forecasts. Partner User : Can only log in via a partner portal. High Volume Customer Portal and Authenticated Website Both user licenses arehigh-volume portal users : Can only log in via a Customer Portal. Customer Portal User : Can only log in via a Customer Portal. Can view and edit data they directly own or data owned by or shared with users below them in the Customer Portal role hierarchy; and they can view and edit cases where they are listed in theContact Name field.
Customer Portal Manager : Can only log in via a Customer Portal. Can view and edit data they directly own or data owned by or shared with users below them in the Customer Portal role hierarchy; and they can view and edit cases where they are listed in theContact Name field. Solution Manager Can review and publish solutions. Also has access to the same functionality as the Standard User. Marketing User Can manage campaigns, import leads, create letterheads, create HTML email templates, manage public documents, and update campaign history via the import wizards. Also has access to the same functionality as the Standard User. Contract Manager : Can create, edit, activate, and approve contracts. This profile can also delete contracts as long as they are not activated. Can edit personal quota and override forecasts. Read Only : Can view the organization's setup, run and export reports, and view, but not edit, other records. Chatter OnlyUser Can only log in to Chatter. Can access all standard Chatter people, profiles, groups, and files. Additionally, they can: " View Salesforce accounts and contacts " Use Salesforce CRM Content, Ideas, and Answers " Access dashboards and reports " Use and approve workflows " Use the calendar to create and track activities " Modify up to ten custom objects Note : You must expose the tabs for the standard Salesforce objects that the Chatter Only user profile can access, as they are hidden by default for these users. Professional Edition organizations must have Profiles enabled to perform these tasks. Contact yoursalesforce.com representative for more information. Only available with the Chatter Only user license. Chatter FreeUser Can only log in to Chatter. Can access all standard Chatter people, profiles, groups, and files. Only available with the Chatter Free user license. Chatter ExternalUser Can only log into Chatter and access groups they've been invited to and interact with members of those groups. Only available with the Chatter External user license. ChatterModerator User Can only log in to Chatter. Can access all standard Chatter people, profiles, groups, and files. Additionally, this user can: " Activate and deactivate other Chatter Free users and moderators " Grant and revoke moderator privileges " Delete posts and comments that they can see Note : Changing a user's profile from Chatter Moderator User to Chatter Free User removes moderator privileges in Chatter. Only available with the Chatter Free user license. Site.com Only User Can only log in to the Site.com app. Each Site.com Only user also needs a Site.com Publisher feature license to create and publish sites, or a Site.com Contributor feature license to edit the site's content.. Additionally, this user can: " Use one custom app with up to 20 custom objects " Access the Content app, but not the Accounts and Contacts objects " Create unlimited custom tabs Only available with the Site.com Only user license.
Question : Out of the custom field types auto-number is not available during data loading using Apex Data Loader?
1. True
2. False
Correct Answer : Get Lastest Questions and Answer :
Exp: An auto-number is a unique number assigned automatically. If the
data type is auto-number, it is a read-only field
Related 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
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
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
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
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
Question : custom Application : Helps you store objects in logical and easy to access location
1. True
2. False