ITIL4-CDS Create, Deliver and Support Practice Question
Exhibit
JSON Policy Rule: {
"Action": "ALLOW",
"Condition": "User Role: DEVELOPER",
"Environment": "STAGING",
"Approval_Required": "FALSE"
}Refer to the exhibit. A developer attempts to push code directly to the PRODUCTION environment. Based on the provided policy, what is the expected outcome and why?
⚠ Common exam trap
Candidates often assume that permission is implied if it is not explicitly denied, failing to realize that ITIL 4 governance requires explicit authorization for sensitive production environment changes.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The push will be blocked because the policy only authorizes actions in STAGING.
The policy explicitly grants permissions for the STAGING environment without approval but remains silent on PRODUCTION access. In a strict ITIL 4 CDS governance framework, implicit denial is the standard for security and risk management. Therefore, the action is blocked because the policy does not explicitly permit deployments to PRODUCTION, ensuring that all production changes undergo necessary risk assessment and approval protocols before execution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The push will succeed because the policy does not explicitly deny production access.
Why it's wrong here
Relying on the absence of a denial is a security vulnerability. ITIL 4 service management requires explicit authorization for changes in production environments to maintain stability. Assuming success without positive permission contradicts the principle of 'keep it simple and practical' balanced with necessary security and risk controls.
- ✓
The push will be blocked because the policy only authorizes actions in STAGING.
Why this is correct
The policy defines specific access scopes. Since the rule is constrained to the STAGING environment, any attempt to perform actions outside this scope is automatically rejected by the system. This ensures that production environments remain protected from unauthorized changes, adhering to the principle of least privilege and strict governance.
- ✗
The push will succeed because 'DEVELOPER' role is authorized for all environments.
Why it's wrong here
Role-based access control (RBAC) must be applied contextually. The provided JSON includes an 'Environment' attribute, which acts as a filter. Even if a user has the 'DEVELOPER' role, the condition explicitly limits their authorized environment to 'STAGING,' making any attempt to push to PRODUCTION a policy violation.
- ✗
The push will succeed but require manual approval by an administrator.
Why it's wrong here
The policy specifies 'Approval_Required: FALSE' only for the STAGING environment. There is no fallback logic defined for production. Assuming a manual approval process exists when it is not explicitly configured in the policy violates the logic of automated governance, which requires clear, programmed paths for all transactions.
About these practice questions
This ITIL4-CDS question is part of Courseiva's 155-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PeopleCert/AXELOS exam blueprint
This ITIL4-CDS practice question is part of Courseiva's free PeopleCert/AXELOS certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ITIL4-CDS exam.