上QQ阅读APP看书,第一时间看更新
Quiz
- What are the capabilities of cross-object formula fields? (choose two options)
- Formula fields can expose a user to data, to which they do not have access on a record itself
- Formula fields can reference fields from a collection of child records
- Formula fields can reference fields from objects that are up to 10 relationships away
- Formula fields can be used in up to three roll-up summary fields per object
- Using only standard object relationships, on which standard objects could you create a custom roll-up summary field? (choose three options)
- On the Opportunity object rolling up Opportunity Product records
- On the Account object rolling up Case records
- On the Campaign object rolling up Campaign Member records
- On the Account object rolling up Opportunity records
- Which of the following scenarios can you not achieve with formula fields?
- Display a clickable link using the HYPERLINK function to a specific record in a legacy system.
- Display the previous value for a field using the PRIORVALUE function to the user.
- Calculate whether the value from a datetime field is in the past using the NOW function.
- Determine which of three different images to display using the IF function.
- Who can edit a record after it has been submitted for approval and has been locked? (choose two options)
- A user who is assigned as a current approver
- Any user who approved the record previously
- Any user higher in the role hierarchy that the current approver
- An administrator
- How can a developer enforce the fact that a reviewer is required to provide a reason in a specific field only when a review has a rating lower than three?
- By creating a formula field
- Creating a reason field and marking it as required
- Creating a validation rule
- This can't be done declaratively
- A developer needs to create an application that tracks machines and their parts. Individual parts can be related to different machine types. How should the developer set up their data model to keep track of this data and prevent unrelated parts?
- Create a lookup relationship to relate Parts to their parent Machine.
- Create a junction object to relate many Machines to multiple Parts through a master-detail relationship.
- Create a master-detail relationship to represent the one-to-many data model of Parts to Machines.
- Create a junction object to relate many Machines to many Parts through a lookup relationship.
- A developer needs to update a picklist field on related contact records when a modification to the associated account is detected. How could a developer provide a solution?
- Create a workflow rule that performs a field update
- Create a Visual Workflow on Account that updates the contact records
- Create a process with Process Builder on Account that updates the contact records
- This requirement cannot be solved declaratively
- Which of the following statements is true?
- A roll-up summary field can be created on any object that is on the master side of a master-detail relationship
- A roll-up summary field can be created on any object that is on the parent side of a lookup relationship
- A roll-up summary field can be created on any object that is on the detail side of a master-detail relationship
- A roll-up summary field can be created on any object that is on the child side of a lookup relationship
- Object X has a lookup to Object Y. Which of the following statements is true? (choose two options)
- Fields of object X can be accessed from object Y
- Fields of object Y can be accessed from object X
- Fields of both X and Y are accessible from object Y
- Fields of both Y and X are accessible from object X
- The business asks a developer to make sure that when a record of object X gets deleted, all records with the same name pertaining to another unrelated object Z also get deleted. How would a developer solve this request?
- Create a Process Builder that invokes a Visual Flow when a record of object X gets deleted. The Visual Flow then queries for records of object Z with the same name and deletes them.
- Replace the Delete button on object X with a custom Delete button that calls a Visual Flow. This Visual Flow first queries all records of object Z with the same name as the record where the button was clicked, then deletes that X record, and also deletes all Z records it found.
- Create a Process Builder that deletes all records of object Z with the same name when record X gets deleted.
- There is no way to meet this requirement declaratively.