Question 490
Each of 4 delivery resource plan engineers provides 30 productive hours in each of 5 weeks, but must reserve 8 total hours for project training. What team delivery capacity remains after training?
- 592 hours
- 440 hours
- 600 hours
- 568 hours
Explanation
Correct Answer
D:Nominal productive capacity 600 − 4×8 training hours = 568. These stated figures yield 568 hours for the requested net delivery capacity in the delivery resource plan case.
Incorrect Answers
A:Only one engineer’s training has been removed. The resulting 592 hours does not match the requested net delivery capacity for the delivery resource plan: the governing arithmetic is Nominal productive capacity 600 − 4×8 training hours = 568, yielding 568 hours.
B:This incorrectly repeats a one-time training cost every week. The resulting 440 hours does not match the requested net delivery capacity for the delivery resource plan: the governing arithmetic is Nominal productive capacity 600 − 4×8 training hours = 568, yielding 568 hours.
C:This forgets mandatory training. The resulting 600 hours does not match the requested net delivery capacity for the delivery resource plan: the governing arithmetic is Nominal productive capacity 600 − 4×8 training hours = 568, yielding 568 hours.
Question 491
For a university learning portal threat, a planned response reduces chance from 25% to 5% with potential impact $45,000. What is the maximum annual price of that response that still breaks even in expected-loss terms?
- $45,000
- $11,250
- $9,000
- $2,250
Explanation
Correct Answer
C:At break-even, treatment cost equals the reduction in exposure: $45,000 × (25% − 5%) = $9,000. These stated figures yield $9,000 for the requested maximum break-even control price in the university learning portal case.
Incorrect Answers
A:Full event impact overstates the benefit from reducing its likelihood. The resulting $45,000 does not match the requested maximum break-even control price for the university learning portal: the governing arithmetic is At break-even, treatment cost equals the reduction in exposure: $45,000 × (25% − 5%) = $9,000, yielding $9,000.
B:Pre-control exposure is not the amount of benefit created by the change. The resulting $11,250 does not match the requested maximum break-even control price for the university learning portal: the governing arithmetic is At break-even, treatment cost equals the reduction in exposure: $45,000 × (25% − 5%) = $9,000, yielding $9,000.
D:Residual risk is not the maximum rational control cost. The resulting $2,250 does not match the requested maximum break-even control price for the university learning portal: the governing arithmetic is At break-even, treatment cost equals the reduction in exposure: $45,000 × (25% − 5%) = $9,000, yielding $9,000.
Question 492
The identity-access migration activity network has independent branches totaling 9 and 6 workdays. With a common start and finish and no other constraints, how much total float does the shorter branch possess?
- 6 days
- 0 days
- 3 days
- 9 days
Explanation
Correct Answer
C:Float on the shorter branch = 9 − 6 = 3 days. These stated figures yield 3 days for the requested short-path float in the identity-access migration case.
Incorrect Answers
A:The shorter branch duration is not its slack. The resulting 6 days does not match the requested short-path float for the identity-access migration: the governing arithmetic is Float on the shorter branch = 9 − 6 = 3 days, yielding 3 days.
B:A shorter independent branch is not critical under the given constraints. The resulting 0 days does not match the requested short-path float for the identity-access migration: the governing arithmetic is Float on the shorter branch = 9 − 6 = 3 days, yielding 3 days.
D:This is the critical path length, not float. The resulting 9 days does not match the requested short-path float for the identity-access migration: the governing arithmetic is Float on the shorter branch = 9 − 6 = 3 days, yielding 3 days.
Question 493
In the partner API integration, the team proposes the practice Reinforce the new behavior to measure use of a new process and coach teams after initial rollout. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?
- Adoption reinforcement sustains behavioral change after first training.
- Action ownership makes execution follow-up possible after the conversation ends.
- Ad hoc reporting responds to an exceptional information need outside routine cadence.
- Regular status meetings expose current delivery health and near-term decisions.
Explanation
Correct Answer
A:This is observable evidence of Reinforce the new behavior for the partner API integration purpose to measure use of a new process and coach teams after initial rollout; operational mechanism: Adoption reinforcement sustains behavioral change after first training; specific limitation: One kickoff workshop does not prove lasting uptake.
Incorrect Answers
B:This behavior would demonstrate Record meeting action owners for assign named participants and deadlines to decisions from a delivery coordination meeting, rather than Reinforce the new behavior for measure use of a new process and coach teams after initial rollout in the partner API integration; functional evidence: Action ownership makes execution follow-up possible after the conversation ends; qualification to consider: Meeting attendance by itself does not ensure actions are completed.
C:This behavior would demonstrate Provide a targeted ad hoc report for answer a newly raised executive question about a specific delivery issue, rather than Reinforce the new behavior for measure use of a new process and coach teams after initial rollout in the partner API integration; the practical reason is: Ad hoc reporting responds to an exceptional information need outside routine cadence; important boundary: It need not replace the normal reporting process.
D:This behavior would demonstrate Hold project status updates for share agreed progress and blockers with stakeholders at the scheduled cadence, rather than Reinforce the new behavior for measure use of a new process and coach teams after initial rollout in the partner API integration; the practical reason is: Regular status meetings expose current delivery health and near-term decisions; important boundary: They should be supported by traceable actions rather than vague optimism.
Question 494
The identity governance implementation team has a specific outstanding requirement: deliver a tightly specified integration using planned sequential phase approvals. At the planning review, which action or practice is the most appropriate response?
- Scrum
- Scaled Agile Framework (SAFe)
- Waterfall
- Extreme programming (XP)
Explanation
Correct Answer
C:Waterfall fits the identity governance implementation requirement to deliver a tightly specified integration using planned sequential phase approvals; functional evidence: Waterfall commonly completes planned stages in sequence with formal stage outputs; qualification to consider: It is less accommodating of major late requirement changes than iterative approaches.
Incorrect Answers
A:Scrum is intended to deliver complex software incrementally with a product backlog and short timeboxed iterations, not to meet the identity governance implementation requirement to deliver a tightly specified integration using planned sequential phase approvals; functional evidence: Scrum organizes work into sprints with specific accountabilities, events, and artifacts; qualification to consider: It relies on empirical inspection rather than finalizing every requirement at the outset.
B:Scaled Agile Framework (SAFe) is intended to coordinate several agile teams working on a shared large solution, not to meet the identity governance implementation requirement to deliver a tightly specified integration using planned sequential phase approvals; functional evidence: SAFe provides planning and coordination patterns for agile delivery across multiple teams; qualification to consider: Single-team Scrum alone does not define all enterprise-level synchronization needs.
D:Extreme programming (XP) is intended to improve code quality with pair programming, continuous integration, and test-first engineering, not to meet the identity governance implementation requirement to deliver a tightly specified integration using planned sequential phase approvals; operational mechanism: Extreme programming applies disciplined engineering practices and rapid developer feedback; specific limitation: It is a software development practice set, not an enterprise portfolio framework.
Question 495
The regulated-document archive team already uses Project dashboard to present a compact set of current indicators and exceptions across project workstreams. A new workstream must also trace proposed changes, approvals, status, and implementation references. Which additional practice should be paired with the existing one to address the second, distinct need?
- Project dashboard
- Version control system
- Change log
- Risk register
Explanation
Correct Answer
C:Adding Change log addresses the new regulated-document archive need to trace proposed changes, approvals, status, and implementation references; Project dashboard already serves the separate need to present a compact set of current indicators and exceptions across project workstreams; operational mechanism: A change log preserves the history of controlled alterations; specific limitation: It cannot substitute for a risk response register.
Incorrect Answers
A:Project dashboard is already present in the regulated-document archive to present a compact set of current indicators and exceptions across project workstreams; repeating it does not fulfill the distinct requirement to trace proposed changes, approvals, status, and implementation references; operational mechanism: A dashboard consolidates metrics for quick monitoring; specific limitation: A narrative status report can supply more context behind the numbers.
B:Version control system would instead address track who changed source artifacts and allow review or restoration of earlier revisions; the regulated-document archive still needs to trace proposed changes, approvals, status, and implementation references, in addition to its existing Project dashboard; functional evidence: Version control maintains a history of changes to files and code; qualification to consider: It does not itself prioritize project risk or resource allocations.
D:Risk register would instead address record future uncertainties with probability, impact, owner, and planned response; the regulated-document archive still needs to trace proposed changes, approvals, status, and implementation references, in addition to its existing Project dashboard; functional evidence: The risk register tracks exposure before a potential event occurs; qualification to consider: Actual current problems belong in issue tracking.
Question 496
The cross-border reporting service team has a specific outstanding requirement: compare the team's technical capabilities with those the planned solution requires. At the planning review, which action or practice is the most appropriate response?
- Resource needs assessment
- Preventive maintenance
- Software end-of-life transition
- Skills gap analysis
- Hardware decommissioning
Explanation
Correct Answer
D:Skills gap analysis fits the cross-border reporting service requirement to compare the team's technical capabilities with those the planned solution requires; operational mechanism: Skills gap analysis identifies training or recruitment needs from required competencies; specific limitation: Resource utilization alone does not prove the right skills exist.
Incorrect Answers
A:Resource needs assessment is intended to identify required skills and equipment before requesting purchases or assignments, not to meet the cross-border reporting service requirement to compare the team's technical capabilities with those the planned solution requires; the practical reason is: A needs assessment compares planned activities with actual capability and capacity; important boundary: Buying before establishing a gap can waste budget and create surplus.
B:Preventive maintenance is intended to keep project hardware operating by scheduling inspections and servicing, not to meet the cross-border reporting service requirement to compare the team's technical capabilities with those the planned solution requires; operational mechanism: Maintenance preserves availability and reduces foreseeable equipment failures; specific limitation: It is not equivalent to decommissioning assets after use.
C:Software end-of-life transition is intended to replace an unsupported software dependency before vendor support terminates, not to meet the cross-border reporting service requirement to compare the team's technical capabilities with those the planned solution requires; functional evidence: An end-of-life plan addresses support, security, compatibility, and migration risks; qualification to consider: A temporary license extension may not restore absent security updates.
E:Hardware decommissioning is intended to remove obsolete equipment securely after a data-center migration, not to meet the cross-border reporting service requirement to compare the team's technical capabilities with those the planned solution requires; functional evidence: Decommissioning retires assets with inventory, data sanitization, and disposal controls; qualification to consider: Powering off equipment alone may leave sensitive data exposed.
Question 497
The manufacturing sensor deployment team has a specific outstanding requirement: establish where project participants will exchange approvals and operational updates. At the planning review, which action or practice is the most appropriate response?
- Confirm high-level solution design
- Define access requirements
- Agree communication channels
- Review inherited project artifacts
Explanation
Correct Answer
C:Agree communication channels fits the manufacturing sensor deployment requirement to establish where project participants will exchange approvals and operational updates; functional evidence: Agreed channels reduce missed information and conflicting records; qualification to consider: Different audiences may require different cadence and confidentiality levels.
Incorrect Answers
A:Confirm high-level solution design is intended to select a feasible architecture direction that meets the charter's major constraints, not to meet the manufacturing sensor deployment requirement to establish where project participants will exchange approvals and operational updates; the practical reason is: Early solution design resolves critical technical assumptions for planning; important boundary: Detailed build specifications may still be refined later.
B:Define access requirements is intended to specify which participants require permissions to proposed environments and documents, not to meet the manufacturing sensor deployment requirement to establish where project participants will exchange approvals and operational updates; operational mechanism: Access requirements connect work roles with appropriate privileges; specific limitation: Permissions should be least-privilege and reviewed as membership changes.
D:Review inherited project artifacts is intended to identify existing contracts, requirements, and constraints before re-planning a handed-over project, not to meet the manufacturing sensor deployment requirement to establish where project participants will exchange approvals and operational updates; the practical reason is: Reviewing inherited artifacts prevents accidental conflict with previous commitments; important boundary: A new team should not treat prior approvals as nonexistent.
Question 498
The ERP integration program team has a specific outstanding requirement: activate a documented response when an anticipated disruption occurs. At the planning review, which action or practice is the most appropriate response?
- Document the resolution
- Log the issue
- Apply a workaround
- Execute the contingency response
- Perform root cause analysis
Explanation
Correct Answer
D:Execute the contingency response fits the ERP integration program requirement to activate a documented response when an anticipated disruption occurs; functional evidence: An approved contingency provides preplanned steps for a known trigger; qualification to consider: The plan may still require an issue owner and follow-up investigation.
Incorrect Answers
A:Document the resolution is intended to preserve the corrective action and evidence that a reported problem was resolved, not to meet the ERP integration program requirement to activate a documented response when an anticipated disruption occurs; the practical reason is: Resolution documentation enables audit, lessons learned, and repeat-issue prevention; important boundary: Closing without confirming the outcome risks recurrence and inaccurate status.
B:Log the issue is intended to record a currently occurring blocker with evidence, impact, priority, and ownership, not to meet the ERP integration program requirement to activate a documented response when an anticipated disruption occurs; operational mechanism: An issue log centralizes active problems and the progress of their resolution; specific limitation: A risk register is for uncertain events that have not necessarily happened.
C:Apply a workaround is intended to restore partial service quickly while a permanent correction is being developed, not to meet the ERP integration program requirement to activate a documented response when an anticipated disruption occurs; functional evidence: A workaround reduces immediate operational impact without necessarily removing the cause; qualification to consider: It requires tracking so a temporary bypass does not become an undocumented standard.
E:Perform root cause analysis is intended to identify why a recurring integration defect happens instead of treating only symptoms, not to meet the ERP integration program requirement to activate a documented response when an anticipated disruption occurs; functional evidence: Root cause analysis traces the underlying drivers that produce an observed failure; qualification to consider: It supports a durable correction beyond an immediate temporary workaround.
Question 499
In the partner API integration, the team proposes the practice Calendar scheduler to find common available times and distribute meeting invitations. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?
- E-signature workflows record signers, signing order, and completion evidence.
- Calendaring tools coordinate schedules, reminders, and invitees.
- Conferencing tools enable remote synchronous sessions.
- These techniques support numeric modeling, filtering, and comparisons.
Explanation
Correct Answer
B:This is observable evidence of Calendar scheduler for the partner API integration purpose to find common available times and distribute meeting invitations; operational mechanism: Calendaring tools coordinate schedules, reminders, and invitees; specific limitation: They do not by themselves run a meeting or capture decisions.
Incorrect Answers
A:This behavior would demonstrate Electronic-signature workflow for capture attributable approval signatures on a formal acceptance document, rather than Calendar scheduler for find common available times and distribute meeting invitations in the partner API integration; functional evidence: E-signature workflows record signers, signing order, and completion evidence; qualification to consider: An ordinary chat acknowledgment may not satisfy the signature process.
C:This behavior would demonstrate Conferencing platform for host distributed participants with audio, screen sharing, and meeting controls, rather than Calendar scheduler for find common available times and distribute meeting invitations in the partner API integration; the practical reason is: Conferencing tools enable remote synchronous sessions; important boundary: They need accessibility and connectivity planning for attendees.
D:This behavior would demonstrate Spreadsheet for perform tabular cost calculations and resource forecasts with transparent formulas, rather than Calendar scheduler for find common available times and distribute meeting invitations in the partner API integration; the practical reason is: Spreadsheets support numeric modeling, filtering, and comparisons; important boundary: They can introduce formula and version risks if poorly controlled.
Question 500
In the branch-network refresh, the team proposes the practice Update the approved project plan to reflect an authorized change in schedules, budget, and scope baselines as required. An independent reviewer wants observable evidence that the proposed mechanism is being used. Which behavior should the reviewer expect?
- Implementation puts the approved change into the actual product or project workflow.
- The change log captures proposed scope changes before decision and implementation.
- Plan updates make an approved decision operational for subsequent tracking.
- Current change records support traceability and prevent requests from being lost.
Explanation
Correct Answer
C:This is observable evidence of Update the approved project plan for the branch-network refresh purpose to reflect an authorized change in schedules, budget, and scope baselines as required; operational mechanism: Plan updates make an approved decision operational for subsequent tracking; specific limitation: They should follow authorization rather than silently legitimize unauthorized work.
Incorrect Answers
A:This behavior would demonstrate Implement the authorized change for carry out an approved solution adjustment using the agreed implementation plan, rather than Update the approved project plan for reflect an authorized change in schedules, budget, and scope baselines as required in the branch-network refresh; operational mechanism: Implementation puts the approved change into the actual product or project workflow; specific limitation: It follows assessment and authorization rather than replacing those controls.
B:This behavior would demonstrate Register a change request for create an auditable record when a stakeholder proposes unplanned functionality, rather than Update the approved project plan for reflect an authorized change in schedules, budget, and scope baselines as required in the branch-network refresh; operational mechanism: The change log captures proposed scope changes before decision and implementation; specific limitation: A verbal request alone cannot establish authorization or a decision trail.
D:This behavior would demonstrate Maintain change-log status for record the decision, owner, implementation status, and closure evidence of every request, rather than Update the approved project plan for reflect an authorized change in schedules, budget, and scope baselines as required in the branch-network refresh; operational mechanism: Current change records support traceability and prevent requests from being lost; specific limitation: They are broader than a list containing only the newly proposed features.