Veeva Vault & CRM Certifications Practice Quiz

Question 1

Why does Vault have lifecycle states carry a state type as well as a name?

Accepted Answer

So that platform behaviour can key off a state's standard meaning rather than off a name each customer chooses freely

Question 2

Where are the roles that a lifecycle grants permissions to defined?

Accepted Answer

On the lifecycle itself, which is what allows its states to grant permissions to them

Question 3

An entry action is configured to start a workflow. When does that workflow begin?

Accepted Answer

When the item enters the state, as a consequence of the transition having happened

Question 4

Two document types in a Vault need identical state handling. What is the appropriate configuration?

Accepted Answer

Use one lifecycle for both, since a lifecycle is not tied to a single document type

Question 5

A state grants edit to one role and view to another. A user holds both roles on the same document. What is the practical result?

Accepted Answer

They can edit it, since holding the role that grants edit is what the state requires

Veeva Vault & CRM Certifications Group Discussion