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

Question : List the types of resources available to use in a flow
A. Variable
B. Constant
C. Formula
D. Text
E. Template
F. Choice
G. Dynamic Choice

1. A,B,C,D
2. B,C,D,E
3. C,D,E,F
4. D,E,F,G
5. A,B,C,D,E,F,G

Correct Answer : 5
Explanation: In the Cloud Flow Designer, the Explorer tab displays the resources that you added to the flow. You can create some types of resources from the Resources tab by double-clicking them. Other resources, such as global constants and system variables, are automatically provided by the system. Which resources are available depend on the specific field you're setting, and oftentimes you can create new resources from within that field by expanding the CREATE NEW section of its drop-down list. Flow Resource Choice : Represents an individual value that can be used in choice screen fields. You can create a choice from the Resources tab or while defining screen choice fields.
Collection Variable : Represents a collection of values with a single data type. Use a collection variable as a container in the flow to store and reference multiple values at once. You can create a collection variable from the Resources tab.
Constant : Stores a fixed value. You can create a constant from the Resources tab.
Dynamic Choice : Looks up data from an object's records and dynamically generates a set of choices for screen fields at runtime. When referenced as a resource, a dynamic choice's value is determined by the most recent user selection of a choice within the generated set. You can create a dynamic choice from the Resources tab or while defining screen choice fields. Element: Any element that you add to the flow is available as a Resource with the was visited operator in outcome criteria. An element is considered visited if the element has already been executed in the flow interview.
Any element that you add to the flow that supports a fault connector is available as a Boolean resource. If the element has already been successfully executed in the flow interview, the resource's value is True. If the element wasn't executed or was executed and resulted in an error, the resource's value is False.
Formula : Calculates a value from other resources in the flow. You can create a formula from the Resources tab.
Global Constant : Fixed, system-provided values, such as EmptyString, True, and False, that can be assigned as the values of flow resources.
Outcome : If you add a Decision element to the flow, its outcomes are available as Boolean resources. If an outcome path has already been executed in the flow interview, the resource's value is True. Picklist Values System-provided values that are available as resources only in Assignment and Decision elements when selecting values for-or to compare against-picklist fields in sObject variables. Screen Field : Any screen field that you add to the flow is available as a resource. The resource value depends on the type of screen field. The value for a screen input field is what the user enters. The value for a screen choice field is the stored value of the choice that the user selects. The value for a screen output field is the text that's displayed to the user.
SObject Collection Variable : Represents a collection of records for a specified object. Use an sObject collection variable as a container in the flow to store and reference field values for multiple records. You can create an sObject collection variable from the Resources tab. SObject Variable : Represents a record for a specified object. Use an sObject variable as a container in the flow to store, update, and reference field values for a record. You can create an sObject variable from the Resources tab. System Variable : System-provided values that can be referenced as resources, such as {!$Flow.CurrentDate}, {!$Flow.CurrentDateTime}, and {!$Flow.FaultMessage}. Text Template : Stores formatted text with merge fields that reference flow resources. You can create a text template from the Resources tab.
Variable : Stores a value that can be updated as the flow executes. The variable can be referenced throughout the flow and can be used as the value of a field in a Salesforce record. You can create a variable from the Resources tab. Wait Event : If you add a Wait element to the flow, its events are available as Boolean resources. If an event's waiting conditions are met, the resource's value is True. If the event has no waiting conditions set, the resource's value is always True.

Question : List the types of Data Element available to use in a flow
A. Record Create
B. Record Update
C. Record Lookup
D. Record Delete

1. A,B,C
2. B,C,D
3. A,B,D
4. A,B,C,D

Correct Answer : 4
Flow Elements : Each element represents an action that the flow can execute, such as reading or writing Salesforce data, displaying information and collecting data from flow users, executing business logic, or manipulating data. Available in: Enterprise, Performance, Unlimited, and Developer Editions
In the Cloud Flow Designer, the canvas and Explorer tab display the elements that already exist in the flow, and the Palette tab displays the available element types that you can add to the flow by dragging them onto the canvas.
Apex Plug-in : Calls an Apex class that implements the Process.Plugin interface. If you used the Tag property in the PluginDescribeResult class, the Apex class appears under a customized section. Otherwise, it appears under the Apex Plug-ins section.
Assignment : Sets or changes values in variables, collection variables, sObject variables, and sObject collection variables.
Decision : Evaluates conditions to determine which flow path to take.
Email Alert : Sends an email by using a workflow email alert to specify the email template and recipients.
Fast Create : Creates Salesforce records using the field values from an sObject collection variable, or creates one Salesforce record using the field values from an sObject variable. : Fast Delete : Deletes Salesforce records using the ID values from an sObject collection variable, or deletes one Salesforce record using the ID value from an sObject variable. Fast Lookup : Queries Salesforce records to assign their field values to an sObject collection variable, or queries one Salesforce record to assign its field values to an sObject variable.
Fast Update : Updates Salesforce records using the field values from an sObject collection variable, or updates one Salesforce record using the field values from an sObject variable.Loop : Iterates through an sObject collection variable. For each item in this sObject collection variable, the Loop element:
1. Assigns the item's values to a loop-specific sObject variable.
2. Executes the loop-specific flow path, which contains elements that use the loop-specific sObject variable-for example, to manipulate its values and then assign the updated values to another sObject collection variable that can be referenced later in the flow.
Other Action : Calls an object-specific or global action.
Post to Chatter : Posts a message to the feed for a specific record, user, or Chatter group.
Record Create : Creates one Salesforce record using field values that you specify individually. You can assign these values from flow resources, such as variables and screen fields. Record Delete : Deletes Salesforce records that meet the filter criteria you specify.
Record Lookup : Queries one Salesforce record that meets the filter criteria you specify, and then assigns the record's field values to separate, individual flow variables or individual fields on sObject variables.
Record Update : Updates one Salesforce record using field values that you specify individually. You can assign these values from flow resources, such as variables and screen fields. Screen : Displays a screen to the user who is running the flow. The screen contains fields for user input or for displaying information to the user. Fields and choices that you create for the screen are available as resources that you can reference elsewhere in the flow.
Send Email : Sends an email by using the flow to specify the subject, body, and recipients.
Step : Serves as a temporary placeholder while you design a flow. You can convert Step elements into Screen elements.
Submit for Approval : Submits one Salesforce record for approval. Subflow : Calls another flow in the organization. Wait : Waits for one or more defined events to occur.

Question : Field History Tracking : It tracks modification to any standard or custom field, whose history is set to be tracked in the object's history related list

1. True
2. False

Correct Answers: 1

Explanation: Tracking Field History

You can select certain fields to track, and display the field history in the History related list of an object. You can track the field history of custom objects, as well as the history of the following standard objects:
" Accounts
" Cases
" Contacts
" Entitlements
" Service contracts
" Contract line items
" Contracts
" Leads
" Opportunities
" Articles
" Solutions
Modifying any of these fields adds a new entry to the History related list. All entries include the date, time, nature of the change, and who made the change. Note that not all field types are available for history tracking. Certain changes, such as case escalations, are always tracked.

Considerations
" Changes to fields with more than 255 characters are tracked as edited, and their old and new values are not recorded.
" Tracked field values are not automatically translated; they display in the language in which they were made. For example, if a field is changed from Green to Verde, Verde is displayed no matter what a user's language is, unless the field value has been translated into other languages via the Translation Workbench. This also applies to record types and picklist values.
" Changes to custom field labels that have been translated via the Translation Workbench are shown in the locale of the user viewing the History related list. For example, if a custom field label is Red and translated into Spanish as Rojo, then a user with a Spanish locale will see the custom field label as Rojo. Otherwise, the user will see the custom field label as Red.
" Changes to date fields, number fields, and standard fields are shown in the locale of the user viewing the History related list. For example, a date change to August, 5, 2012 shows as 8/5/2012 for a user with the English (United States) locale, and as 5/8/2012for a user with the English (United Kingdom) locale.

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

Related Questions