Premium

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



Question : Building your Data Model limit on the number of custom fields per object depends on the Salesforce edition.
: Building your Data Model limit on the number of custom fields per object depends on the Salesforce edition.
1. True
2. False


Correct Answer : Get Lastest Questions and Answer :

Explanation: Create Custom Fields
Capture all your important business data and store it in fields you create
Available in: Personal, Group, Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions
Platform Connect external objects are available in: Developer Edition and for an additional cost in: Enterprise, Performance, and Unlimited Editions
Relationship fields aren't available in Personal Edition
Custom fields aren't available on Activities in Group Edition
Custom settings aren't available in Professional Edition
Layouts aren't available in Database.com






Question : Encrypted fields can be edited regardless of whether you have the "View Encrypted Data" permission.
: Encrypted fields can be edited regardless of whether you have the
1. True
2. False


Correct Answer : Get Lastest Questions and Answer :

Understanding Encrypted Custom Fields
Restrict other Salesforce users from seeing custom text fields you want to keep private. Only users with the permission "View Encrypted Data" can see data in encrypted custom text fields.
Available in: Developer, Enterprise, Performance, Unlimited, and Database.com Editions
Implementation Notes
" Encrypted fields are encrypted with 128-bit master keys and use the Advanced Encryption Standard (AES) algorithm. You can archive, delete, and import your master encryption key. To enable master encryption key management, contact salesforce.com.
" You can use encrypted fields in email templates but the value is always masked regardless of whether you have the "View Encrypted Data" permission.
" If you have created encrypted custom fields, make sure your organization has secure connections using SSL (Secure Sockets Layer) enabled.
" If you have the "View Encrypted Data" permission and you grant login access to another user, be aware that the other user will be able to see encrypted fields unmasked (in plain text).
" Only users with the "View Encrypted Data" permission can clone the value of an encrypted field when cloning that record.
" Only the apex:outputField component supports presenting encrypted fields in Visualforce pages.
Restrictions
Encrypted text fields:
" Cannot be unique, have an external ID, or have default values.
" For leads are not available for mapping to other objects.
" Are limited to 175 characters because of the encryption algorithm.
" Are not available for use in filters such as list views, reports, roll-up summary fields, and rule filters.
" Cannot be used to define report criteria, but they can be included in report results.
" Are not searchable, but they can be included in search results.
" Are not available for: Salesforce Classic, Connect Offline, Connect for Outlook, Salesforce for Outlook, lead conversion, workflow rule criteria or formulas, formula fields, outbound messages, default values, and Web-to-Lead and Web-to-Case forms.
Best Practices
" Encrypted fields are editable regardless of whether the user has the "View Encrypted Data" permission. Use validation rules, field-level security settings, or page layout settings to prevent users from editing encrypted fields.
" You can still validate the values of encrypted fields using validation rules or Apex. Both work regardless of whether the user has the "View Encrypted Data" permission. Data for encrypted fields in the debug log isn't masked because users who have access to the debug logs have access to all data in the organization.
" Existing custom fields cannot be converted into encrypted fields nor can encrypted fields be converted into another data type. To encrypt the values of an existing (unencrypted) field, export the data, create an encrypted custom field to store that data, and import that data into the new encrypted field.
" Mask Type is not an input mask that ensures the data matches the Mask Type. Use validation rules to ensure that the data entered matches the mask type selected.
Use encrypted custom fields only when government regulations require it because they involve additional processing and have search-related limitations.






Question : How can you prevent an encrypted field from being edited?
: How can you prevent an encrypted field from being edited?
1. Validation rules
2. Field level security
 3. Access Mostly Uused Products by 50000+ Subscribers
4. Not possible
5. All 1,2 and 3



Correct Answer : Get Lastest Questions and Answer :


Explanation: " Encrypted fields are editable regardless of whether the user has the "View Encrypted Data" permission. Use validation rules, field-level security settings, or page layout settings to prevent users from editing encrypted fields.
" You can still validate the values of encrypted fields using validation rules or Apex. Both work regardless of whether the user has the "View Encrypted Data" permission. Data for encrypted fields in the debug log isn't masked because users who have access to the debug logs have access to all data in the organization.
" Existing custom fields cannot be converted into encrypted fields nor can encrypted fields be converted into another data type. To encrypt the values of an existing (unencrypted) field, export the data, create an encrypted custom field to store that data, and import that data into the new encrypted field.
" Mask Type is not an input mask that ensures the data matches the Mask Type. Use validation rules to ensure that the data entered matches the mask type selected.
Use encrypted custom fields only when government regulations require it because they involve additional processing and have search-related limitations.




Related Questions

Question : Which statement is true about a custom tab?
: Which statement is true about a custom tab?
1. It can only be included in one application.
2. It can only be included in standard applications.
3. Access Mostly Uused Products by 50000+ Subscribers
4. It can only be included in custom applications.


Question : When would a developer use upsert and external IDs?

A. To integrate with an external system.
B. To migrate customizations from sandbox to production.
C. To load related records without knowing Salesforce record IDs.
D. To use the Web Services API to query for data.

 : When would a developer use upsert and external IDs?
1. A,B
2. B,D
 3. Access Mostly Uused Products by 50000+ Subscribers
4. C,D


Question : A group of executives has requested a convenient way to see daily metrics without having to log in to
Salesforce.
How would a developer accomplish this goal?

 : A group of executives has requested a convenient way to see daily metrics without having to log in to
1. Set the users home page layouts to include a dashboard.
2. Create a Workflow rule that sends a link to the dashboard in an email.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Create a series of daily recurring events providing the dashboard link.