PMI's AI management guidance explains that models deployed in dynamic domains-such as healthcare-are particularly vulnerable to data drift, where "the statistical properties of input data or underlying real-world processes change over time, leading to performance degradation if models are not monitored and updated." In the scenario, the cognitive diagnostic system is continuously exposed to new patient data and evolving medical knowledge from multiple databases. PMI notes that in such cases, "AI models that are not periodically retrained, recalibrated, or revalidated against current data will show reduced accuracy, reliability, and clinical usefulness over time." The final report states that the model's performance degraded over time, affecting reliability and effectiveness, which is the hallmark symptom of data drift rather than an initial validation issue. PMI-CPMAI content stresses setting up continuous monitoring, performance dashboards, and drift detection mechanisms specifically to track "the impact of data drift on model accuracy and business or clinical outcomes," triggering model refresh or redesign when thresholds are exceeded. Changes in business model requirements could affect alignment of outputs to objectives but would not, by themselves, explain gradual technical degradation in predictions. Therefore, the most appropriate cause, as framed in PMI's lifecycle and MLOps perspective, is the impact of data drift on model accuracy, requiring ongoing monitoring and retraining to restore performance.

For an AI virtual assistant that must integrate with existing CRM systems and support varied customer queries, PMI-CPMAI-aligned practices emphasize that the initial critical task is understanding and assessing the current data environment. This is best achieved by conducting a comprehensive data audit (option B). A data audit systematically examines what data exists in the CRM and surrounding systems, how it is structured, its quality, completeness, lineage, and how it flows across processes.
This step reveals whether the assistant can access necessary customer profiles, interaction histories, product details, and case records; identifies data gaps; and surfaces integration constraints (such as inconsistent IDs, missing timestamps, or poor-quality notes). The audit also supports decisions on privacy controls and consent management for customer data. Building a data lake (option A) is an architectural choice that should be based on audit findings, not a starting assumption. Designing a custom algorithm (option C) and procuring advanced NLP libraries (option D) are technical implementation activities that come after the project has confirmed that the available data and integrations can support the intended capabilities and compliance obligations.
Therefore, the necessary initial task for the project manager is to conduct a comprehensive data audit of the CRM-related landscape.

CPMAI explicitly frames AI and forecasting projects as iterative and incremental, not rigid, one-shot efforts.
The methodology allows teams to progress through phases with the understanding that they may loop back when new data or insights become available. In a forecasting project where not all desired historical user data is accessible yet, the recommended approach is to move forward with what is available, while planning and documenting assumptions about missing data and potential impacts.
PMI/CPMAI guidance stresses that waiting for "perfect" data can stall value delivery and increase project risk. Instead, early iterations using partial but representative data help validate the problem framing, test pipelines, and surface data-access issues early, while governance and data owners work on unlocking additional datasets. The key is to acknowledge explicitly that the project is iterative: you may return to earlier data understanding and preparation steps as new data becomes available. This is exactly what option B describes-moving forward while anticipating additional access and leveraging an iterative lifecycle to revisit earlier steps-rather than freezing the project (C) or blindly pressing ahead without a plan (A or D).

The PMI-CPMAI framework places strong emphasis on traceability, accountability, and documentation across the entire AI lifecycle-covering both cognitive (ML models, data pipelines) and non-cognitive components (traditional automation, rule engines, integration services). It explains that AI projects typically involve cross-functional roles-data scientists, ML engineers, domain experts, security, compliance, and operations-and that "clear accountability requires that decisions, changes, and artifacts be documented in a way that is shared, searchable, and version-controlled across the team." To achieve this, PMI-CPMAI recommends centralized documentation repositories (for example, a single documentation platform or system-of-record) where all contributors can log design decisions, assumptions, model versions, data lineage, approvals, and test results. Centralization reduces fragmentation, ensures a
"single source of truth," and supports audits, governance reviews, and handovers. Periodic reviews by the project manager improve quality but do not, by themselves, create systematic accountability. Splitting protocols for cognitive vs. non-cognitive parts can introduce silos and inconsistencies, and a separate documentation team may distance those doing the work from owning the records.
By contrast, using a centralized documentation system accessible to all team members aligns directly with PMI-CPMAI's call for integrated, lifecycle-wide documentation: every role remains responsible for its own artifacts, but all content lives in a shared, governed environment, enabling accurate, up-to-date accountability documentation.

Scalability in AI initiatives is defined within PMI-CPMAI as the solution's ability to maintain performance, reliability, and accuracy when subjected to increased data volume, user demand, or computational workload.
The PMI AI Management Framework emphasizes that an AI system must be architected to "expand capacity, data throughput, and model processing without degradation of service quality" (PMI-CPMAI Learning Path:
AI Solution Design and Implementation).
PMI further states that when assessing scalability, project managers must evaluate whether the AI system can
"adapt to higher-than-forecast usage levels, larger datasets, and future feature growth using modular and distributed architectures." The official guidance notes that scalable AI solutions often rely on elastic cloud environments, containerized deployments, and horizontally scalable compute layers. This is captured in PMI's explanation that "AI performance must remain stable as demand increases, requiring testing against progressively higher loads to validate computational capacity, latency thresholds, and throughput expectations" (PMI-CPMAI: AI Technical Foundations).
The project manager's responsibility includes verifying that the model pipelines, data ingestion systems, and inferencing services continue to operate effectively under expanded operational demand. PMI stresses that this factor-ability to handle increased loads-is the cornerstone of scalability evaluation, whereas regulatory compliance, human oversight, and integration concerns, while important, relate to governance, ethics, and interoperability rather than scalability.
Therefore, the correct factor that ensures AI scalability is the solution's ability to handle increased loads.