Question 40
The virtual desktop rollout team has a specific outstanding requirement: send attributable written updates and attachments without requiring simultaneous attendance. At the delivery review, which action or practice is the most appropriate response?
- Telephone call
- Enterprise social platform
- Video conference
- Email
Explanation
Correct Answer
D:Email fits the virtual desktop rollout requirement to send attributable written updates and attachments without requiring simultaneous attendance; functional evidence: Email supports durable asynchronous correspondence to a defined audience; qualification to consider: High urgency may require a more immediate escalation channel.
Incorrect Answers
A:Telephone call is intended to clarify a critical ambiguous issue immediately with a remote stakeholder using audio, not to meet the virtual desktop rollout requirement to send attributable written updates and attachments without requiring simultaneous attendance; functional evidence: A call provides synchronous verbal interaction without requiring video; qualification to consider: A follow-up record may be needed for formal decisions.
B:Enterprise social platform is intended to broadcast project community updates and maintain discussion for a broad internal audience, not to meet the virtual desktop rollout requirement to send attributable written updates and attachments without requiring simultaneous attendance; operational mechanism: Enterprise social tools reach organizational networks and encourage open updates; specific limitation: Confidential approvals still need controlled audiences.
C:Video conference is intended to discuss a design visually with dispersed staff who need live interaction, not to meet the virtual desktop rollout requirement to send attributable written updates and attachments without requiring simultaneous attendance; functional evidence: Video meetings provide real-time conversation and shared visual context; qualification to consider: Time zones and connectivity can limit attendance.
Question 41
The smart-building control upgrade team has a specific outstanding requirement: record future uncertainties with probability, impact, owner, and planned response. At the delivery review, which action or practice is the most appropriate response?
- Project dashboard
- Project status report
- Requirements traceability matrix
- Risk register
Explanation
Correct Answer
D:Risk register fits the smart-building control upgrade requirement to record future uncertainties with probability, impact, owner, and planned response; functional evidence: The risk register tracks exposure before a potential event occurs; qualification to consider: Actual current problems belong in issue tracking.
Incorrect Answers
A:Project dashboard is intended to present a compact set of current indicators and exceptions across project workstreams, not to meet the smart-building control upgrade requirement to record future uncertainties with probability, impact, owner, and planned response; operational mechanism: A dashboard consolidates metrics for quick monitoring; specific limitation: A narrative status report can supply more context behind the numbers.
B:Project status report is intended to explain progress, variance, major risks, decisions needed, and next actions to stakeholders, not to meet the smart-building control upgrade requirement to record future uncertainties with probability, impact, owner, and planned response; functional evidence: A status report provides narrative context around delivery conditions; qualification to consider: It is not normally a live system of record for individual code revisions.
C:Requirements traceability matrix is intended to connect each requirement to design elements, test cases, and acceptance evidence, not to meet the smart-building control upgrade requirement to record future uncertainties with probability, impact, owner, and planned response; the practical reason is: Traceability makes it possible to verify that defined requirements were addressed; important boundary: A task board alone does not show end-to-end requirement evidence.
Question 42
In the regulated-document archive, the team proposes the practice Informed (I) to notify an impacted executive of a completed decision without asking them to perform the task. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?
- Reviewing inherited artifacts prevents accidental conflict with previous commitments.
- Accountable ownership establishes final answerability for an outcome.
- Informed roles receive relevant one-way status and decisions.
- The charter establishes project legitimacy and overarching direction.
Explanation
Correct Answer
C:This is observable evidence of Informed (I) for the regulated-document archive purpose to notify an impacted executive of a completed decision without asking them to perform the task; the practical reason is: Informed roles receive relevant one-way status and decisions; important boundary: They do not carry task execution responsibility by virtue of being notified.
Incorrect Answers
A:This behavior would demonstrate Review inherited project artifacts for identify existing contracts, requirements, and constraints before re-planning a handed-over project, rather than Informed (I) for notify an impacted executive of a completed decision without asking them to perform the task in the regulated-document archive; functional evidence: Reviewing inherited artifacts prevents accidental conflict with previous commitments; qualification to consider: A new team should not treat prior approvals as nonexistent.
B:This behavior would demonstrate Accountable (A) for name the one person answerable for the completion and approval of a deliverable, rather than Informed (I) for notify an impacted executive of a completed decision without asking them to perform the task in the regulated-document archive; operational mechanism: Accountable ownership establishes final answerability for an outcome; specific limitation: A well-designed RACI normally assigns one accountable owner per activity.
D:This behavior would demonstrate Project charter for formally authorize a project with objectives, high-level scope, and a named leader, rather than Informed (I) for notify an impacted executive of a completed decision without asking them to perform the task in the regulated-document archive; the practical reason is: The charter establishes project legitimacy and overarching direction; important boundary: Detailed work packages and full schedules are developed subsequently.
Question 43
During the network equipment lifecycle program, the service transition manager has two distinct obligations: (1) specify which audiences get which messages through what channel and frequency; (2) estimate and baseline expected costs by activity, resource, or period. Which TWO complementary practices satisfy the two different obligations? Choose TWO.
- Detailed scope statement
- Communications management plan
- Project schedule
- Quality assurance plan
- Prioritized product backlog
- Project budget
Explanation
Correct Answers
B:A communication plan maps stakeholders to information needs and timing; in the network equipment lifecycle program, this fulfills requirement (1) to specify which audiences get which messages through what channel and frequency. For the network equipment lifecycle program, it should include escalation and confidentiality where relevant.
F:The budget provides a cost reference for authorizing and tracking expenditure; in the network equipment lifecycle program, this fulfills requirement (2) to estimate and baseline expected costs by activity, resource, or period. For the network equipment lifecycle program, it must reflect procurement and contingency assumptions where appropriate.
Incorrect Answers
A:A detailed scope statement makes proposed work sufficiently clear to control additions; this differs from the listed needs for the network equipment lifecycle program, which are specify which audiences get which messages through what channel and frequency and estimate and baseline expected costs by activity, resource, or period. In the network equipment lifecycle program, it supports decomposition and acceptance criteria.
C:A project schedule shows when planned work should happen and in what order; this differs from the listed needs for the network equipment lifecycle program, which are specify which audiences get which messages through what channel and frequency and estimate and baseline expected costs by activity, resource, or period. In the network equipment lifecycle program, budget alone cannot reveal logical task constraints.
D:A QA plan specifies how quality will be managed before defects are found; this differs from the listed needs for the network equipment lifecycle program, which are specify which audiences get which messages through what channel and frequency and estimate and baseline expected costs by activity, resource, or period. In the network equipment lifecycle program, it complements rather than replaces actual product testing.
E:The backlog captures work candidates and their relative product priority; this differs from the listed needs for the network equipment lifecycle program, which are specify which audiences get which messages through what channel and frequency and estimate and baseline expected costs by activity, resource, or period. In the network equipment lifecycle program, not every item is a committed sprint deliverable.
Question 44
The customer loyalty application team has a specific outstanding requirement: enable an experienced team that coordinates independently and consistently meets goals. At the planning review, which action or practice is the most appropriate response?
- Product owner
- Performing
- Storming
- Software end-of-life transition
Explanation
Correct Answer
B:Performing fits the customer loyalty application requirement to enable an experienced team that coordinates independently and consistently meets goals; operational mechanism: Performing describes mature collaboration and reliable execution; specific limitation: Micromanagement can reduce the autonomy that drives its results.
Incorrect Answers
A:Product owner is intended to order the product backlog and clarify the value of proposed features, not to meet the customer loyalty application requirement to enable an experienced team that coordinates independently and consistently meets goals; functional evidence: A product owner represents product priorities and accepts responsibility for backlog ordering; qualification to consider: They need not manage all project contracts or staff assignments.
C:Storming is intended to support a team in which members openly disagree about authority and working approaches, not to meet the customer loyalty application requirement to enable an experienced team that coordinates independently and consistently meets goals; operational mechanism: Storming involves role conflict and competing working preferences as members test boundaries; specific limitation: Facilitation is more suitable than assuming the team is already fully aligned.
D:Software end-of-life transition is intended to replace an unsupported software dependency before vendor support terminates, not to meet the customer loyalty application requirement to enable an experienced team that coordinates independently and consistently meets goals; 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.
Question 45
The multisite wireless upgrade team has a specific outstanding requirement: screen a request for completeness, duplication, and obvious policy conflicts before detailed analysis. At the planning review, which action or practice is the most appropriate response?
- Perform change impact analysis
- Conduct a preliminary change review
- Update the approved project plan
- Communicate a change decision
Explanation
Correct Answer
B:Conduct a preliminary change review fits the multisite wireless upgrade requirement to screen a request for completeness, duplication, and obvious policy conflicts before detailed analysis; operational mechanism: Preliminary review identifies invalid or incomplete requests early in the workflow; specific limitation: It does not itself grant final approval for a material baseline change.
Incorrect Answers
A:Perform change impact analysis is intended to quantify effects on delivery date, cost, scope, quality, and risk before approval, not to meet the multisite wireless upgrade requirement to screen a request for completeness, duplication, and obvious policy conflicts before detailed analysis; functional evidence: Impact analysis gives authorized reviewers evidence about trade-offs of a proposed change; qualification to consider: Implementing first would bypass the information needed for a sound decision.
C:Update the approved project plan is intended to reflect an authorized change in schedules, budget, and scope baselines as required, not to meet the multisite wireless upgrade requirement to screen a request for completeness, duplication, and obvious policy conflicts before detailed analysis; the practical reason is: Plan updates make an approved decision operational for subsequent tracking; important boundary: They should follow authorization rather than silently legitimize unauthorized work.
D:Communicate a change decision is intended to tell affected stakeholders whether a requested scope amendment was authorized, not to meet the multisite wireless upgrade requirement to screen a request for completeness, duplication, and obvious policy conflicts before detailed analysis; functional evidence: Decision communication aligns delivery teams and requesters on approved direction; qualification to consider: A private log entry does not ensure that implementers know the outcome.
Question 46
The branch-network refresh team has a specific outstanding requirement: compare current performance with an agreed target and quantify the remaining difference. At the delivery review, which action or practice is the most appropriate response?
- Hold project status updates
- Publish updated knowledge articles
- Train impacted employees
- Record meeting action owners
- Execute gap analysis
Explanation
Correct Answer
E:Execute gap analysis fits the branch-network refresh requirement to compare current performance with an agreed target and quantify the remaining difference; operational mechanism: Gap analysis identifies missing capabilities or performance against a defined target state; specific limitation: A routine status note may describe progress without measuring that difference.
Incorrect Answers
A:Hold project status updates is intended to share agreed progress and blockers with stakeholders at the scheduled cadence, not to meet the branch-network refresh requirement to compare current performance with an agreed target and quantify the remaining difference; functional evidence: Regular status meetings expose current delivery health and near-term decisions; qualification to consider: They should be supported by traceable actions rather than vague optimism.
B:Publish updated knowledge articles is intended to provide operational users with instructions matching the new application workflow, not to meet the branch-network refresh requirement to compare current performance with an agreed target and quantify the remaining difference; the practical reason is: Knowledge bases turn rollout learning into repeatable accessible procedures; important boundary: Old instructions can misdirect staff after process changes.
C:Train impacted employees is intended to prepare users whose daily processes will change after a new IT rollout, not to meet the branch-network refresh requirement to compare current performance with an agreed target and quantify the remaining difference; functional evidence: Organizational change training enables staff to perform future workflows; qualification to consider: Technical deployment alone does not guarantee adoption.
D:Record meeting action owners is intended to assign named participants and deadlines to decisions from a delivery coordination meeting, not to meet the branch-network refresh requirement to compare current performance with an agreed target and quantify the remaining difference; operational mechanism: Action ownership makes execution follow-up possible after the conversation ends; specific limitation: Meeting attendance by itself does not ensure actions are completed.
Question 47
The customer-support application release team has a specific outstanding requirement: show estimated work remaining across a sprint or release. At the delivery review, which action or practice is the most appropriate response?
- Burndown chart
- Fishbone diagram
- Run chart
- Histogram
Explanation
Correct Answer
A:Burndown chart fits the customer-support application release requirement to show estimated work remaining across a sprint or release; functional evidence: Burndown charts trend remaining work against time and a target trajectory; qualification to consider: They can conceal added scope unless the backlog changes are also reviewed.
Incorrect Answers
B:Fishbone diagram is intended to organize hypotheses about underlying causes of recurrent service defects, not to meet the customer-support application release requirement to show estimated work remaining across a sprint or release; functional evidence: Fishbone diagrams group possible causes into categories for investigation; qualification to consider: They show possible mechanisms rather than measured causal proof.
C:Run chart is intended to plot an operational metric over time to spot patterns or trends, not to meet the customer-support application release requirement to show estimated work remaining across a sprint or release; the practical reason is: Run charts display observations in chronological order; important boundary: Without control limits they do not establish formal statistical control.
D:Histogram is intended to group defect counts into numeric ranges to inspect their frequency distribution, not to meet the customer-support application release requirement to show estimated work remaining across a sprint or release; operational mechanism: A histogram shows how observations are distributed among measured intervals; specific limitation: It does not depict the time order of individual measurements.
Question 48
The cloud analytics platform team has a specific outstanding requirement: state testable software behavior before developers begin implementing a change. At the governance checkpoint, which action or practice is the most appropriate response?
- Cloud-provider change coordination
- Requirements definition
- Manual exploratory testing
- Continuous deployment
- Staging environment
- Continuous integration
Explanation
Correct Answer
B:Requirements definition fits the cloud analytics platform requirement to state testable software behavior before developers begin implementing a change; the practical reason is: Requirements definition clarifies intended outcomes and acceptance criteria; important boundary: Coding without clear criteria increases rework and ambiguity.
Incorrect Answers
A:Cloud-provider change coordination is intended to account for shared-responsibility boundaries when changing managed cloud services, not to meet the cloud analytics platform requirement to state testable software behavior before developers begin implementing a change; functional evidence: Cloud change planning distinguishes customer-controlled settings from provider-operated infrastructure; qualification to consider: Traditional on-site maintenance responsibilities may differ.
C:Manual exploratory testing is intended to investigate unexpected user journeys not fully captured by scripted test cases, not to meet the cloud analytics platform requirement to state testable software behavior before developers begin implementing a change; functional evidence: Manual testing applies human judgment to edge cases and usability; qualification to consider: It should not be the only control for highly repetitive regression suites.
D:Continuous deployment is intended to release each qualifying change automatically into production after required automated gates, not to meet the cloud analytics platform requirement to state testable software behavior before developers begin implementing a change; operational mechanism: Continuous deployment automates promotion of accepted changes to live service; specific limitation: It requires careful safeguards and differs from manual release approval.
E:Staging environment is intended to test a release in a production-like environment before exposing customers, not to meet the cloud analytics platform requirement to state testable software behavior before developers begin implementing a change; operational mechanism: Staging reduces deployment surprises by approximating real integrations and settings; specific limitation: It is not the live system serving normal users.
F:Continuous integration is intended to merge changes frequently and run automatic builds and tests to detect conflicts early, not to meet the cloud analytics platform requirement to state testable software behavior before developers begin implementing a change; operational mechanism: Continuous integration validates combined source updates through a shared pipeline; specific limitation: It does not necessarily deploy every successful build into production.
Question 49
The regional help-desk rollout team has a specific outstanding requirement: prepare deployment, business handoff, training, cutover, and stabilization activities. At the planning review, which action or practice is the most appropriate response?
- Transition and release plan
- Work breakdown structure (WBS)
- Detailed scope statement
- Project schedule
Explanation
Correct Answer
A:Transition and release plan fits the regional help-desk rollout requirement to prepare deployment, business handoff, training, cutover, and stabilization activities; functional evidence: A transition plan describes how delivered capabilities will become supported operations; qualification to consider: A technically complete product still needs readiness for real use.
Incorrect Answers
B:Work breakdown structure (WBS) is intended to decompose a fixed delivery scope into manageable work packages for estimating, not to meet the regional help-desk rollout requirement to prepare deployment, business handoff, training, cutover, and stabilization activities; the practical reason is: A WBS organizes the complete project work into smaller deliverable-oriented components; important boundary: It is not the same as a chronological milestone calendar.
C:Detailed scope statement is intended to specify boundaries, major deliverables, assumptions, and exclusions for project execution, not to meet the regional help-desk rollout requirement to prepare deployment, business handoff, training, cutover, and stabilization activities; functional evidence: A detailed scope statement makes proposed work sufficiently clear to control additions; qualification to consider: It supports decomposition and acceptance criteria.
D:Project schedule is intended to map activity dependencies, expected durations, resources, and milestones, not to meet the regional help-desk rollout requirement to prepare deployment, business handoff, training, cutover, and stabilization activities; the practical reason is: A project schedule shows when planned work should happen and in what order; important boundary: Budget alone cannot reveal logical task constraints.
Question 50
The cross-border reporting service team has a specific outstanding requirement: embed security controls and scanning throughout an automated delivery pipeline. At the planning review, which action or practice is the most appropriate response?
- Scaled Agile Framework (SAFe)
- Scrum
- DevSecOps
- Kanban
Explanation
Correct Answer
C:DevSecOps fits the cross-border reporting service requirement to embed security controls and scanning throughout an automated delivery pipeline; the practical reason is: DevSecOps integrates security practices into development and operations workflows; important boundary: It shifts security checks earlier instead of postponing them until after release.
Incorrect Answers
A:Scaled Agile Framework (SAFe) is intended to coordinate several agile teams working on a shared large solution, not to meet the cross-border reporting service requirement to embed security controls and scanning throughout an automated delivery pipeline; the practical reason is: SAFe provides planning and coordination patterns for agile delivery across multiple teams; important boundary: Single-team Scrum alone does not define all enterprise-level synchronization needs.
B:Scrum is intended to deliver complex software incrementally with a product backlog and short timeboxed iterations, not to meet the cross-border reporting service requirement to embed security controls and scanning throughout an automated delivery pipeline; 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.
D:Kanban is intended to visualize incoming tickets and limit work in progress to improve continuous flow, not to meet the cross-border reporting service requirement to embed security controls and scanning throughout an automated delivery pipeline; operational mechanism: Kanban uses a visible workflow and work-in-progress limits to expose queues and bottlenecks; specific limitation: It does not require fixed-length iterations or a prescribed sprint role set.