DreamHouse Realty wants to make sure an Opportunity has a field
Expected_Close_Date_c populated before it is allowed to enter the qualified stage.
How should an app builder solution this request?
A.
Record Type
B.
Validation Rule
C.
Activity History
D.
Page Layout
Correct Answer: B
Explanation:
A validation rule is a formula that evaluates the data in one or more fields and returns a value of
“True” or “False”. Validation rules verify that the data a user enters in a record meets the standards
you specify before the user can save the record. In this case, a validation rule can be used to check if
the Expected_Close_Date_c field is populated before the Opportunity stage is set to qualified
Question #2 (Topic: demo questions)
An app builder notices several Accounts converted from Leads are missing information they
expected to be caught via Account validation rules. What could be the source of this issue?
A.
The lead settings are unchecked to require validation for converted leads.
B.
Account validation rules fail to validate on records converted from a lead.
C.
The lead settings are allowing users to intentionally bypass validation rules.
D.
Lead validation rules fail to validate on records when they are being converted.
Correct Answer: A
Explanation:
The lead settings have an option to require validation for converted leads. If this option is unchecked,
then the Account validation rules will not be enforced when a lead is converted to an Account. This
could result in missing or incorrect information on the Account records.
Question #3 (Topic: demo questions)
An App Builder at UVC would like to prevent users from creating new records on an Account related
list by overriding standard buttons. Which two should the App Builder consider before overriding
standard buttons?
A.
Standard buttons can be changed on lookup dialogs, list views, and search result layouts
B.
Standard buttons can be overridden with a Visualforce page
C.
Standard buttons that are not available for overrides can still be hidden on page layouts
D.
Standard buttons can be overridden, relocated on the detail page, and relabeled
Correct Answer: B, C
Explanation:
Standard buttons can be overridden with a Visualforce page to provide custom functionality or user
interface. For example, you can override the New button on an object to display a custom Visualforce
page instead of the standard page layout3. Standard buttons that are not available for overrides can
still be hidden on page layouts to prevent users from accessing them. For example, you can hide the
Delete button on an object to prevent users from deleting records.
Question #4 (Topic: demo questions)
The Service Manager provided the app builder with color code requirements for case age on open
cases.
New cases populate a green circle
Day-old cases populate a yellow circle
Three-day-old cases populate a red circle
How should an app builder implement this requirement?
A.
Formula Field
B.
Quick Action
C.
Custom Button
D.
Lightning Web Component
Correct Answer: A
Explanation:
A formula field is a read-only field that derives its value from a formula expression you define. The
formula field is updated when any of the source fields change. You can use formula fields to display images based on certain conditions. In this case, a formula field can be used to display a green,
yellow, or red circle image based on the case age.
Question #5 (Topic: demo questions)
At Universal Containers, the Account object has a Master-Detail relationship with an Invoice custom
object. The App Builder would like to change to a lookup field, but is not able to do so. What could be
causing this?
A.
The invoice must have at least one Master-Detail field for reporting.
B.
The Account record includes Invoice roll-up summary fields.
C.
The Invoice records have existing values in the Account.
D.
The Account is included in the workflow on the Invoice object.
The Account record includes Invoice roll-up summary fields. This is correct because roll-up summary
fields are only available on the master object in a master-detail relationship, and changing the field
type to lookup would delete the roll-up summary fields