Parks staff draft a 'product' plan describing how a reservation system will gain features over time, and a separate project management plan for the implementation. Which statement best contrasts their deliverable focus?

A product plan (or product management/direction artifact) steers product direction and feature evolution over time; the project management plan covers project governance, baselines, and change control for the implementation. Parks staff correctly keep those deliverable focuses separate for a reservation system. Saying the product plan owns the cost baseline while the project management plan only lists user stories fails by concept: cost baselines and project change control belong with project management planning. Saying the project management plan is optional if the product plan already names future modules fails because naming future modules does not establish project execution and control approaches. Saying both plans are interchangeable governance documents for approving contractor invoices fails because invoice and baseline control follow project management plan and contract processes, not interchangeable product wish lists. Exam caveat: CAPM items may juxtapose product and project plans—answer by matching artifact to purpose (evolution versus project governance). Operational check: use the product plan for feature roadmap decisions, use the project management plan for schedule/cost baselines and change control, and ensure contractor invoices reconcile to approved project baselines.