Universal Containers is implementing a new lead status process and wants to be able to do the following:
* Track leads through five different status values.
* Run reports showing the duration a lead spends in each status.
* Run full Lifetime reports of a lead from creation to conversion.
* Prevent leads from skipping a lead status.
How can these requirements be met?

• A.Use field history tracking on the lead status field to track the duration of each status. Use validation rules to prevent status skipping.
• B.Use an Apex trigger to populate custom date fields for each status, and use custom formula fields for calculating duration of each status.
• C.Use custom date fields and workflow rules for each status, and use custom formula fields for calculating duration of a status. Use validation rules to prevent status skipping.
• D.Use lead history reporting to track changes in the lead status field, and use custom reporting fields to calculate status duration. Use validation rules to prevent status skipping.

Comment: *

Name: *

Email: *

Verification: *

Which of the following is NOT a valid OOTB problem view?

• A.Root Cause Analysis View
• B.Assess Dialog Form View
• C.Accept Risk Dialog Form View
• D.Mobile

Comment: *

Name: *

Email: *

Verification: *

Which of the following roles can delete a problem task? (Choose all that apply.)

• A.itil
• B.admin
• C.problem_task_analyst
• D.problem_admin
• E.problem_manager

Comment: *

Name: *

Email: *

Verification: *

Which of the following functions is NOT enabled by the Change advisory board (CAB) workbench?

• A.View a calendar of planned changes
• B.Document meeting notes and share with attendees
• C.Define a schedule and related logistics for CAB meetings
• D.Provide video and chat capabilities during CAB meetings

Comment: *

Name: *

Email: *

Verification: *

Which role is required to edit the Type field on a Change

• A.change_manager
• B.admin
• C.itil
• D.nobody

Comment: *

Name: *

Email: *

Verification: *