Data Modeling
Showing posts with label Data Modeling. Show all posts
Showing posts with label Data Modeling. Show all posts

Where do I access the Schema Builder?

Where do I access the Schema Builder?



A. App Setup-->Develop-->Schema Builder
B. App Setup-->Develop-->Tools-->Schema Builder
C. App Setup-->Schema Builder


Answer: C. App Setup-->Schema Builder

What can be used to limit the records return when users utilize a lookup?

What can be used to limit the records return when users utilize a lookup?


A. Lookup Filters
B. Workflow Rules
C. Sharing Rules
D. Security Profiles
E. None of these


Answer: A. Lookup Filters


Lookup filters are administrator settings that restrict the valid values and lookup dialog results for lookup, master-detail, and hierarchical relationship fields. Administrators specify the restrictions by configuring filter criteria that compare fields and values on:
- The current record (source)
- The lookup object (target)
- The user's record, permissions, and role
- Records directly related to the target object

Describe a Junction object.

Describe a Junction object.




Answer: An object that is on the detail side of a master-detail relationship with two different objects, thereby creating a many-to-many relationship between the two master objects.

What happens to the object linked by a lookup field when the parent object is deleted?

What happens to the object linked by a lookup field when the parent object is deleted?



A. Orphaned
B. Reparented to another account
C. Flagged by workflow rule
D. Sent to a queue for reassociation


Answer: A. Orphaned
Note: This depends on whether or not you choose the "Don't allow deletion of the lookup record that's part of a lookup relationship" when you define the relationship.

What is a self relationship?

What is a self relationship?



A. A relationship of account to opportunity owned by same owner
B. A lookup to global search
C. A lookup field to the same object


Answer: C. A lookup field to the same object

What is the maximum number of standard (non-master/detail) lookup relationships allowable per object?

What is the maximum number of standard (non-master/detail) lookup relationships allowable per object?



A. 5
B. 10
C. 25
D. 50
E. 100



Answer: C. 25


Even though some Salesforce documentation says that you can have as many standard (non-master/detail) relationships as you want as long as the custom field limit is not reached, the Winter '13 "Salesforce Limits Quick Reference Guide" clearly states that the max on Lookup fields is 25 per object for ALL Salesforce Editions.

An Owner field exists on a detail object in a master-detail relationship. True or False?

An Owner field exists on a detail object in a master-detail relationship.
True or False?



Answer: False
The Owner field on the detail and sub-detail records is NOT available and is automatically set to the owner of the master record.
Custom objects on the "detail" side of a master-detail relationship can't have sharing rules, manual sharing, or queues, as these require the Owner field.

What are some limitations for encrypted fields?

What are some limitations for encrypted fields?



A. Cannot be unique
B. Cannot be longer than 16 characters
C. Cannot be an external ID
D. Cannot have a default value
E. None of these

Answer:

A. Cannot be unique
C. Cannot be an external ID
D. Cannot have a default value
Some more info about Encrypted fields.
- Encrypted custom fields cannot be unique, an external ID, or have default values.
- While other text fields can contain up to 255 characters, encrypted text fields are limited to 175 characters due to the encryption algorithm.
- Encrypted fields are not available for use in filters such as list views, reports, roll-up summary fields, and rule filters.
- Encrypted fields cannot be used to define report criteria but they can be included in report results.
- Encrypted fields are not searchable but they can be included in search results.

With dependent picklists, what can Standard fields be used for?

With dependent picklists, what can Standard fields be used for?



A. Controlling Fields
B. Dependent Fields
C. Standard fields can not be used in picklists


Answer: A. Controlling fields
Standard fields can only be used as Controlling fields because their functions cannot be altered in a way where other fields can influence them.

What is the maximum number of external IDs an object may have?

What is the maximum number of external IDs an object may have?



A. 1
B. 2
C. 3
D. 4
E. 5


Answer: C. 3


For each object that can have custom fields, you can set up to THREE custom text, number, or email fields as external IDs. An external ID field contains record identifiers from a system outside of Salesforce.
You can use an external ID field to update or upsert records using the API. When using the API or import wizards for custom objects and solutions, you can use this field to prevent duplicates by also marking the field as Unique.
Note: Custom fields marked as Unique count against an object's limit of three External ID fields. Custom indexing that occurs automatically in the background by Salesforce does not count against External ID limits.

Which of the following are true regarding an autonumber field?

Which of the following are true regarding an autonumber field?



A. The data in any auto-number field remains unchanged if you change to a text field
B. Data contained in a text field will not be deleted when you change it to auto number
C. All records created while the field was an auto number field will be deleted
D. None of the above


Answer:

A. The data in any auto-number field remains unchanged if you change to a text field
B. Data contained in a text field will not be deleted when you change it to auto number


The data in any auto-number field remains unchanged if you convert it into a text field. Also, you can safely convert a text custom field into an auto-number field without losing your data.
Converting an auto-number field into any other data type results in data loss. Auto-number fields can contain a maximum of 30 characters. Before converting a text custom field into an auto-number field, change any records that contain more than 30 characters in that field.

Subscribe to: Posts (Atom)