a. Formula
b. Lookup
c. E-mail
d. URL
a. Encrypted text fields can be an external ID and can have default values
b. Encrypted fields are not searchable and cannot be used to define report criteria
c. Encrypted fields can be included in search results, and report results
d. They are not available for use in filters such as list views, reports, roll-up summary fields, and rule filters
e. Encrypted fields are not available in lead conversion, workflow rule criteria or formulas, formula fields, outbound messages, default values, and Web-to-Lead and Web-to-Case forms
a. The field will not appear in the edit layout
b. The user will see only masked characters, but can enter a new value and save it.
c. It will throw an error on changing that field and when he saves
d. He can see the original value and he can save it
a. They are available in Validation Rules or Apex Scripts even if the user is not having the permission "View Encrypted Data"
b. Encrypted fields can be converted to other field types.
c. A custom field can be converted to a encrypted field
d. In Email Templates, if an encrypted field needs to be displayed without the mask character, the User who receives the e-mail, should have "View Encrypted Data" permission.
a. A text field that is unique
b. A text field that is required
c. A text field that is encrypted
d. Date
e. E-mail
f. Phone
a. Master-Detail
b. Lookup
c.Hierarchical
d. Many-Many
e. Self
a. 1
b. 2
c. 3
d. 4
e. 5
a. 10
b. 20
c. 15
d. 25
a. True
b. False
a. Junction object (custom object) having a Master-Detail to the other two objects
b. Create a lookup on the first object for the other and lookup on the second for the first