Question 10
The procurement automation rollout team has a specific outstanding requirement: reduce the likelihood or consequences of a possible supplier outage. At the planning review, which action or practice is the most appropriate response?
- Accept a threat
- Mitigate a threat
- Exploit an opportunity
- Enhance an opportunity
Explanation
Correct Answer
B:Mitigate a threat fits the procurement automation rollout requirement to reduce the likelihood or consequences of a possible supplier outage; the practical reason is: Threat mitigation adds safeguards that lower the chance or impact of adverse events; important boundary: Residual exposure can remain and should still have an owner.
Incorrect Answers
A:Accept a threat is intended to retain a low-exposure uncertainty deliberately because further treatment costs more than the likely loss, not to meet the procurement automation rollout requirement to reduce the likelihood or consequences of a possible supplier outage; the practical reason is: Risk acceptance documents a choice to tolerate exposure and monitor triggers; important boundary: It is a conscious response rather than failing to identify a risk.
C:Exploit an opportunity is intended to take action that makes an identified beneficial event virtually certain, not to meet the procurement automation rollout requirement to reduce the likelihood or consequences of a possible supplier outage; functional evidence: Opportunity exploitation deliberately changes work to secure the positive outcome; qualification to consider: It is stronger than enhancement, which merely raises the probability or value.
D:Enhance an opportunity is intended to increase the chance or payoff of a favorable vendor discount without guaranteeing it, not to meet the procurement automation rollout requirement to reduce the likelihood or consequences of a possible supplier outage; functional evidence: Opportunity enhancement improves the probability or impact of a positive event; qualification to consider: The gain is still uncertain after the response.
Question 11
The customer loyalty application team has a specific outstanding requirement: split a large feature initiative into smaller workable backlog items. At the planning review, which action or practice is the most appropriate response?
- Critical path analysis
- Story points
- Epic decomposition
- Publish the schedule update
Explanation
Correct Answer
C:Epic decomposition fits the customer loyalty application requirement to split a large feature initiative into smaller workable backlog items; the practical reason is: An epic groups substantial user value that typically needs decomposition into stories; important boundary: Its size is usually too broad to treat as one narrowly estimated task.
Incorrect Answers
A:Critical path analysis is intended to find the longest dependent task route that determines the earliest possible finish date, not to meet the customer loyalty application requirement to split a large feature initiative into smaller workable backlog items; operational mechanism: The critical path is the sequence of activities driving project duration with zero total float in the basic model; specific limitation: Delaying a critical activity delays completion unless the schedule is recovered.
B:Story points is intended to compare the relative effort and uncertainty of backlog items before iteration planning, not to meet the customer loyalty application requirement to split a large feature initiative into smaller workable backlog items; the practical reason is: Story points express relative complexity rather than guaranteed staff hours; important boundary: Teams calibrate their own scale using observed delivery capacity.
D:Publish the schedule update is intended to ensure project participants know the current forecast and affected milestone dates, not to meet the customer loyalty application requirement to split a large feature initiative into smaller workable backlog items; the practical reason is: Schedule publication distributes approved or current timing information to intended readers; important boundary: A private planning file cannot coordinate external dependencies.
Question 12
During the identity-access migration, the stakeholder liaison has two distinct obligations: (1) recalculate likely completion dates after task durations or dependencies change; (2) provide operational users with instructions matching the new application workflow. Which TWO complementary practices satisfy the two different obligations? Choose TWO.
- Record meeting action owners
- Provide a targeted ad hoc report
- Revise schedule forecast
- Train impacted employees
- Report a risk trigger
- Publish updated knowledge articles
Explanation
Correct Answers
C:Schedule forecast updates show probable outcomes from current progress; in the identity-access migration, this fulfills requirement (1) to recalculate likely completion dates after task durations or dependencies change. For the identity-access migration, they do not automatically authorize a new baseline.
F:Knowledge bases turn rollout learning into repeatable accessible procedures; in the identity-access migration, this fulfills requirement (2) to provide operational users with instructions matching the new application workflow. For the identity-access migration, old instructions can misdirect staff after process changes.
Incorrect Answers
A:Action ownership makes execution follow-up possible after the conversation ends; this differs from the listed needs for the identity-access migration, which are recalculate likely completion dates after task durations or dependencies change and provide operational users with instructions matching the new application workflow. In the identity-access migration, meeting attendance by itself does not ensure actions are completed.
B:Ad hoc reporting responds to an exceptional information need outside routine cadence; this differs from the listed needs for the identity-access migration, which are recalculate likely completion dates after task durations or dependencies change and provide operational users with instructions matching the new application workflow. In the identity-access migration, it need not replace the normal reporting process.
D:Organizational change training enables staff to perform future workflows; this differs from the listed needs for the identity-access migration, which are recalculate likely completion dates after task durations or dependencies change and provide operational users with instructions matching the new application workflow. In the identity-access migration, technical deployment alone does not guarantee adoption.
E:Risk reporting highlights evolving exposure and response triggers; this differs from the listed needs for the identity-access migration, which are recalculate likely completion dates after task durations or dependencies change and provide operational users with instructions matching the new application workflow. In the identity-access migration, it is forward-looking unless the event already became an active issue.
Question 13
The retail checkout replacement team has a specific outstanding requirement: explain progress, variance, major risks, decisions needed, and next actions to stakeholders. At the delivery review, which action or practice is the most appropriate response?
- Task board
- Change log
- Requirements traceability matrix
- Project status report
Explanation
Correct Answer
D:Project status report fits the retail checkout replacement requirement to explain progress, variance, major risks, decisions needed, and next actions to stakeholders; the practical reason is: A status report provides narrative context around delivery conditions; important boundary: It is not normally a live system of record for individual code revisions.
Incorrect Answers
A:Task board is intended to visualize current work moving through columns such as queued, in progress, and done, not to meet the retail checkout replacement requirement to explain progress, variance, major risks, decisions needed, and next actions to stakeholders; operational mechanism: A task board displays workflow state and ownership of current tasks; specific limitation: It usually gives less dependency detail than a project network diagram.
B:Change log is intended to trace proposed changes, approvals, status, and implementation references, not to meet the retail checkout replacement requirement to explain progress, variance, major risks, decisions needed, and next actions to stakeholders; functional evidence: A change log preserves the history of controlled alterations; qualification to consider: It cannot substitute for a risk response register.
C:Requirements traceability matrix is intended to connect each requirement to design elements, test cases, and acceptance evidence, not to meet the retail checkout replacement requirement to explain progress, variance, major risks, decisions needed, and next actions to stakeholders; operational mechanism: Traceability makes it possible to verify that defined requirements were addressed; specific limitation: A task board alone does not show end-to-end requirement evidence.
Question 14
The supplier onboarding portal team has a specific outstanding requirement: replace an unsupported software dependency before vendor support terminates. At the planning review, which action or practice is the most appropriate response?
- Software end-of-life transition
- Resource needs assessment
- Successor planning
- Hardware decommissioning
Explanation
Correct Answer
A:Software end-of-life transition fits the supplier onboarding portal requirement to replace an unsupported software dependency before vendor support terminates; the practical reason is: An end-of-life plan addresses support, security, compatibility, and migration risks; important boundary: A temporary license extension may not restore absent security updates.
Incorrect Answers
B:Resource needs assessment is intended to identify required skills and equipment before requesting purchases or assignments, not to meet the supplier onboarding portal requirement to replace an unsupported software dependency before vendor support terminates; operational mechanism: A needs assessment compares planned activities with actual capability and capacity; specific limitation: Buying before establishing a gap can waste budget and create surplus.
C:Successor planning is intended to identify and prepare a replacement when a critical project specialist leaves, not to meet the supplier onboarding portal requirement to replace an unsupported software dependency before vendor support terminates; operational mechanism: Succession planning preserves continuity through knowledge transfer and backup staffing; specific limitation: It is proactive instead of waiting for an unexpected vacancy.
D:Hardware decommissioning is intended to remove obsolete equipment securely after a data-center migration, not to meet the supplier onboarding portal requirement to replace an unsupported software dependency before vendor support terminates; the practical reason is: Decommissioning retires assets with inventory, data sanitization, and disposal controls; important boundary: Powering off equipment alone may leave sensitive data exposed.
Question 15
The backup retention migration team has a specific outstanding requirement: record the decision, owner, implementation status, and closure evidence of every request. At the planning review, which action or practice is the most appropriate response?
- Maintain change-log status
- Register a change request
- Perform change impact analysis
- Implement the authorized change
Explanation
Correct Answer
A:Maintain change-log status fits the backup retention migration requirement to record the decision, owner, implementation status, and closure evidence of every request; functional evidence: Current change records support traceability and prevent requests from being lost; qualification to consider: They are broader than a list containing only the newly proposed features.
Incorrect Answers
B:Register a change request is intended to create an auditable record when a stakeholder proposes unplanned functionality, not to meet the backup retention migration requirement to record the decision, owner, implementation status, and closure evidence of every request; functional evidence: The change log captures proposed scope changes before decision and implementation; qualification to consider: A verbal request alone cannot establish authorization or a decision trail.
C:Perform change impact analysis is intended to quantify effects on delivery date, cost, scope, quality, and risk before approval, not to meet the backup retention migration requirement to record the decision, owner, implementation status, and closure evidence of every request; operational mechanism: Impact analysis gives authorized reviewers evidence about trade-offs of a proposed change; specific limitation: Implementing first would bypass the information needed for a sound decision.
D:Implement the authorized change is intended to carry out an approved solution adjustment using the agreed implementation plan, not to meet the backup retention migration requirement to record the decision, owner, implementation status, and closure evidence of every request; functional evidence: Implementation puts the approved change into the actual product or project workflow; qualification to consider: It follows assessment and authorization rather than replacing those controls.
Question 16
The employee directory replacement team has a specific outstanding requirement: plan a disruptive infrastructure cutover during an approved low-impact period. At the governance checkpoint, which action or practice is the most appropriate response?
- Cloud shared-responsibility review
- Scheduled maintenance window
- Tested rollback plan
- Post-change validation checks
Explanation
Correct Answer
B:Scheduled maintenance window fits the employee directory replacement requirement to plan a disruptive infrastructure cutover during an approved low-impact period; functional evidence: A maintenance window aligns expected service interruption with operations constraints; qualification to consider: The window should be communicated and supported by recovery plans.
Incorrect Answers
A:Cloud shared-responsibility review is intended to identify which change tasks belong to the hosted provider versus the customer, not to meet the employee directory replacement requirement to plan a disruptive infrastructure cutover during an approved low-impact period; the practical reason is: Shared responsibility assigns control ownership according to the cloud service model; important boundary: Moving to hosted infrastructure does not erase customer access and configuration duties.
C:Tested rollback plan is intended to restore the prior known-good system state if release validation fails, not to meet the employee directory replacement requirement to plan a disruptive infrastructure cutover during an approved low-impact period; functional evidence: Rollback planning sets recovery steps, checkpoints, and activation criteria; qualification to consider: A backup without a tested restoration procedure is insufficient assurance.
D:Post-change validation checks is intended to confirm functionality and monitoring are healthy after an infrastructure modification, not to meet the employee directory replacement requirement to plan a disruptive infrastructure cutover during an approved low-impact period; the practical reason is: Post-change verification checks expected results before declaring success; important boundary: A green deployment command alone does not prove service health.
Question 17
The digital document workflow team has a specific outstanding requirement: compare required effort and skills with people and equipment actually available. At the planning review, which action or practice is the most appropriate response?
- Train the project team
- Perform procurement needs assessment
- Plan operational training
- Assess available resource capacity
Explanation
Correct Answer
D:Assess available resource capacity fits the digital document workflow requirement to compare required effort and skills with people and equipment actually available; functional evidence: Resource assessment exposes capacity constraints before assigning work; qualification to consider: It reduces commitments based on imaginary availability.
Incorrect Answers
A:Train the project team is intended to close tool or workflow knowledge gaps before work depends on new skills, not to meet the digital document workflow requirement to compare required effort and skills with people and equipment actually available; functional evidence: Training improves team readiness to use unfamiliar methods and platforms; qualification to consider: An untrained assignment creates quality and schedule risk.
B:Perform procurement needs assessment is intended to determine which capabilities must be sourced externally before contracting, not to meet the digital document workflow requirement to compare required effort and skills with people and equipment actually available; operational mechanism: Procurement assessment distinguishes internal supply from gaps requiring vendors; specific limitation: It precedes detailed sourcing commitments.
C:Plan operational training is intended to prepare support staff and users to operate the delivered system after release, not to meet the digital document workflow requirement to compare required effort and skills with people and equipment actually available; the practical reason is: Operational training closes adoption and support skill gaps before handoff; important boundary: Deployment without trained owners can leave an unusable service.
Question 18
The customer-support application release team has a specific outstanding requirement: deliver complex software incrementally with a product backlog and short timeboxed iterations. At the planning review, which action or practice is the most appropriate response?
- PRINCE2
- Extreme programming (XP)
- Waterfall
- Scrum
Explanation
Correct Answer
D:Scrum fits the customer-support application release requirement to deliver complex software incrementally with a product backlog and short timeboxed iterations; the practical reason is: Scrum organizes work into sprints with specific accountabilities, events, and artifacts; important boundary: It relies on empirical inspection rather than finalizing every requirement at the outset.
Incorrect Answers
A:PRINCE2 is intended to govern an initiative through defined management stages and business-case justification, not to meet the customer-support application release requirement to deliver complex software incrementally with a product backlog and short timeboxed iterations; functional evidence: PRINCE2 emphasizes continued business justification, roles, stage controls, and exceptions; qualification to consider: It is a governance-oriented project method rather than a source-code branching practice.
B:Extreme programming (XP) is intended to improve code quality with pair programming, continuous integration, and test-first engineering, not to meet the customer-support application release requirement to deliver complex software incrementally with a product backlog and short timeboxed iterations; functional evidence: Extreme programming applies disciplined engineering practices and rapid developer feedback; qualification to consider: It is a software development practice set, not an enterprise portfolio framework.
C:Waterfall is intended to deliver a tightly specified integration using planned sequential phase approvals, not to meet the customer-support application release requirement to deliver complex software incrementally with a product backlog and short timeboxed iterations; the practical reason is: Waterfall commonly completes planned stages in sequence with formal stage outputs; important boundary: It is less accommodating of major late requirement changes than iterative approaches.
Question 19
The patient-portal implementation team has a specific outstanding requirement: obtain business-user evidence that the delivered workflow meets agreed needs. At the planning review, which action or practice is the most appropriate response?
- Unit testing
- Regression testing
- Stress testing
- User acceptance testing
- Smoke testing
Explanation
Correct Answer
D:User acceptance testing fits the patient-portal implementation requirement to obtain business-user evidence that the delivered workflow meets agreed needs; operational mechanism: UAT validates a solution against the users' operational acceptance criteria; specific limitation: Passing technical unit tests alone cannot demonstrate business fitness.
Incorrect Answers
A:Unit testing is intended to check one isolated function or component against its expected behavior, not to meet the patient-portal implementation requirement to obtain business-user evidence that the delivered workflow meets agreed needs; operational mechanism: Unit tests verify small software units in isolation from the full solution; specific limitation: They do not establish end-to-end business acceptance.
B:Regression testing is intended to detect whether a code update broke functionality that previously worked, not to meet the patient-portal implementation requirement to obtain business-user evidence that the delivered workflow meets agreed needs; functional evidence: Regression testing repeats relevant existing checks after a change; qualification to consider: It is different from proving only that the new feature works.
C:Stress testing is intended to observe system behavior beyond normal expected load and identify failure points, not to meet the patient-portal implementation requirement to obtain business-user evidence that the delivered workflow meets agreed needs; operational mechanism: Stress testing pushes conditions to extremes to explore resilience and recovery; specific limitation: It is more aggressive than measuring normal workload performance.
E:Smoke testing is intended to perform a quick post-deployment check that core functions are operational, not to meet the patient-portal implementation requirement to obtain business-user evidence that the delivered workflow meets agreed needs; functional evidence: Smoke tests detect obvious failures before time-consuming deeper testing proceeds; qualification to consider: Passing them does not demonstrate every regression case or peak-load requirement.
Question 20
The inventory synchronization project team has a specific outstanding requirement: collect only personal fields required for the stated project purpose. At the governance checkpoint, which action or practice is the most appropriate response?
- Regional privacy-law review
- Data minimization
- Personally identifiable information (PII) handling
- Protected health information handling
Explanation
Correct Answer
B:Data minimization fits the inventory synchronization project requirement to collect only personal fields required for the stated project purpose; the practical reason is: Data minimization reduces privacy exposure by limiting unnecessary information; important boundary: A wide data extract can increase obligations without improving functionality.
Incorrect Answers
A:Regional privacy-law review is intended to check which jurisdiction's privacy rules apply to cross-border customer processing, not to meet the inventory synchronization project requirement to collect only personal fields required for the stated project purpose; the practical reason is: Jurisdictional review connects processing location and affected people to legal requirements; important boundary: A vendor's headquarters alone may not determine every applicable law.
C:Personally identifiable information (PII) handling is intended to protect customer records that can identify a particular person, not to meet the inventory synchronization project requirement to collect only personal fields required for the stated project purpose; functional evidence: PII controls govern collection, access, transfer, and retention of identifying data; qualification to consider: Not all operational metrics are individually identifiable.
D:Protected health information handling is intended to apply healthcare-specific controls to identified patient-related records, not to meet the inventory synchronization project requirement to collect only personal fields required for the stated project purpose; the practical reason is: Health data handling protects medical information linked to individuals under relevant law; important boundary: A general marketing-data policy may not satisfy healthcare requirements.