Project Management Qualification (PMQ) Quiz 75

Correct: Professional ethics and integrity in project management require honesty and fair dealing. By disclosing the error, the project manager maintains a sustainable relationship with the supplier and mitigates the risk of project failure caused by the supplier’s inability to deliver at an unsustainable price. This aligns with the principle of seeking a win-win outcome and ensuring long-term project success. Incorrect: Accepting the bid immediately exploits a mistake and violates the principle of integrity. While it may provide short-term financial gains, it introduces significant risks regarding quality and supplier stability. Incorrect: Using the error as leverage for further discounts is predatory and unethical, damaging the trust required for a successful project partnership. Incorrect: Reporting the supplier for incompetence without allowing them to rectify a clerical error is a disproportionate response that ignores the collaborative nature of professional negotiations. Key Takeaway: Ethical negotiation involves transparency and the pursuit of agreements that are fair and viable for all parties involved, as this reduces long-term project risk.

Correct: Influencing senior stakeholders and sponsors requires framing the discussion in terms of value and strategic outcomes. By demonstrating how stakeholder engagement directly supports benefit realization and ROI, the project manager aligns the project’s activities with the sponsor’s primary interests. This approach shows that the expenditure is an investment in success rather than an overhead cost. Incorrect: Submitting a formal change request to the PMO to mandate the budget is an escalatory move that can damage the relationship with the sponsor and does not address the underlying disagreement through influence. Providing a detailed technical breakdown of costs focuses on the inputs rather than the outputs; senior stakeholders are generally more concerned with the value generated than the granular cost components. Agreeing to reduce the budget while documenting the risk is a passive approach that fails to influence the sponsor effectively and puts the project’s ultimate success at significant risk. Key Takeaway: To influence senior stakeholders, project managers must communicate using the language of business value, focusing on how project activities protect and enable the achievement of strategic objectives.

Correct: Building alliances and coalitions relies on finding common ground and demonstrating how the project success contributes to the individual goals of the stakeholders involved. By aligning the project value proposition with the performance targets of the Operations and Sales departments, the project manager fosters genuine commitment rather than forced compliance. Incorrect: Escalating to the sponsor and requesting a mandate relies on legitimate power and authority, which often results in resistance or minimal compliance rather than a supportive coalition. Incorrect: Focusing only on the supportive Finance department ignores the critical need to engage and win over the skeptical departments who are essential to the project overall success. Incorrect: Offering financial incentives is a transactional approach that does not address the underlying concerns of the departments and is often unsustainable or outside the project manager direct control. Key Takeaway: Effective coalition building in project management involves stakeholder analysis to identify mutual gains and using influence to align diverse interests toward a common project goal.

Correct: The next logical step after documenting a change request is to perform a thorough impact assessment. This involves evaluating how the proposed change will affect the project’s triple constraints—time, cost, and quality—as well as risks and resources. This information is vital for the decision-makers to understand the trade-offs involved. Incorrect: Submitting the request to the Change Control Board without an impact assessment is premature because the board lacks the necessary data to make an informed decision. Updating the project management plan and baseline is incorrect because these actions only occur after a change has been formally approved. Implementing the change immediately is a violation of change control procedures and leads to scope creep, as changes must be evaluated and authorized before any work begins. Key Takeaway: Change control is a systematic process designed to ensure that no changes are made to the project baseline without a full understanding of their impact and formal authorization.

Correct: The primary purpose of change control is to manage changes to the project’s scope, schedule, and cost baselines in a controlled manner. By evaluating the impact on all project constraints before approval, the project manager ensures that the baselines remain realistic and that the project’s performance can be accurately measured against a valid plan. Incorrect: Providing a rigid framework that prevents any deviations is incorrect because change control is meant to manage and facilitate necessary changes, not to block them entirely if they add value. Allowing the project manager to quickly update baseline documents without approval is incorrect because baselines are formal agreements that typically require a governance body, such as a Change Control Board, to authorize modifications. Ensuring the team can implement changes immediately while deferring analysis is incorrect because the impact analysis must occur before implementation to prevent scope creep and budget overruns. Key Takeaway: Change control maintains the integrity of project baselines by ensuring every change is evaluated, authorized, and documented, preventing unauthorized changes from undermining project performance measurement.

Correct: In the formal change control process, once a change request is logged, the project manager must perform a detailed impact assessment. This step is crucial because it provides the decision-makers, such as the Change Control Board (CCB), with the necessary data regarding how the change will affect the project’s triple constraints (scope, time, and cost) and quality. Without this assessment, an informed decision cannot be made. Incorrect: Updating the project management plan and schedule baseline before the change is approved is a violation of configuration management principles; baselines should only be updated after formal approval. Incorrect: Directing the team to stop work or start new designs is premature and can lead to unnecessary costs and schedule slippage if the change is ultimately rejected. Incorrect: Submitting the request for immediate approval without an impact assessment is incorrect because the sponsor or CCB requires the results of the impact analysis to understand the trade-offs involved before granting authorization. Key Takeaway: The change control process follows a logical sequence: Log, Assess Impact, Review/Recommend, Decide, Implement, and Close. Impact assessment is the vital bridge between receiving a request and making a decision.

Correct: An impact assessment must look at the project holistically. Because project constraints are linked in what is often called the Iron Triangle, a change in quality requirements will almost certainly require more time or more money. Analyzing these interdependencies allows the project manager to provide the Change Control Board with a complete picture of the trade-offs required to implement the change. Incorrect: Prioritizing cost impact alone is insufficient because it ignores potential delays to the schedule or technical risks that could jeopardize the project’s success. Updating the project management plan and baselines immediately is incorrect because changes should only be baselined after they have been formally approved by the Change Control Board; doing so prematurely bypasses the governance process. Consulting only technical experts for quality ignores the integrated nature of project management, where the project manager must also account for the logistical and financial ramifications of technical decisions. Key Takeaway: A robust impact assessment evaluates how a change in one constraint (scope, quality, time, or cost) ripples through the others to ensure informed decision-making.

Correct: The primary role of the Change Control Board (CCB) is to provide governance by reviewing formal change requests and making an informed decision based on the impact assessment and the project’s overall objectives. They assess how the change affects the business case and decide the appropriate course of action. Incorrect: The responsibility for updating project documentation like the schedule and budget lies with the project manager and the project team, not the CCB itself. Incorrect: The CCB is a decision-making body, not a technical execution team; the project team is responsible for the actual implementation of approved changes. Incorrect: While the CCB handles changes to baselines, minor adjustments that do not affect the project’s scope, cost, or schedule baselines are often managed by the project manager through a delegated authority level to maintain efficiency. Key Takeaway: The CCB is a formal governance entity responsible for reviewing, evaluating, and deciding on changes to project baselines to ensure the project remains viable and aligned with its goals.

Correct: Configuration management is concerned with the functional and physical characteristics of the product. It provides the necessary information about which items (Configuration Items) are affected by a proposed change, ensuring version control and technical integrity. Change control is the process of identifying, documenting, approving, or rejecting changes to the project baselines such as scope, time, and cost. Integration occurs when configuration management identifies the specific components impacted, which then informs the change control board’s decision on whether the change is feasible within project constraints. Incorrect: The suggestion that change control manages technical specifications while configuration management handles budget is a reversal of their primary functions; change control focuses on the impact on project constraints like budget. Incorrect: Configuration management does not replace change control; both processes run in parallel throughout the project lifecycle to ensure that changes are both authorized and technically documented. Incorrect: Limiting configuration management to the end of the project for archiving ignores its vital role in version control and status accounting during the development and execution phases. Key Takeaway: Configuration management provides the technical identification of affected components, while change control provides the administrative authorization for the impact on the project plan.

Correct: Once a change request is formally approved by the Change Control Board, the project manager must update the project management plan and all affected baselines. This ensures that future performance measurement and reporting are conducted against the new, approved targets. Communication is also essential to ensure all stakeholders are aware of the revised expectations. Incorrect: Creating a new project charter is unnecessary because the charter is a high-level authorization document that typically remains static unless the project’s fundamental purpose or existence changes. Incorrect: Keeping original baselines intact to measure total variance is incorrect because baselines must reflect the current approved scope to provide meaningful performance data; variances should be measured against the most recent authorized version to be useful for day-to-day management. Incorrect: Instructing the team to work without updating documentation first risks misalignment and poor control, as the project would be operating under outdated plans and reporting metrics. Key Takeaway: Approved changes must be integrated into the project management plan and baselines immediately to maintain a valid performance measurement baseline.

Correct: Effective communication of change outcomes requires a targeted approach. By translating outcomes into specific benefits for different stakeholder groups, the project manager addresses the ‘What is in it for me’ factor, which is critical for reducing resistance and ensuring the realization of benefits. Incorrect: Distributing a single report to everyone lacks the necessary focus on individual stakeholder needs and may lead to information overload or irrelevance for certain groups. Relying only on senior management endorsement ignores the importance of engaging the people actually performing the work, which is essential for long-term adoption. Providing only technical manuals is a passive approach that fails to address the emotional and cultural aspects of change management, often leading to poor engagement. Key Takeaway: Communication regarding change outcomes must be purposeful, tailored to the audience, and focused on the transition from the current state to the desired future state to ensure stakeholder buy-in.

Correct: In a formal change control process, every request must be tracked through its entire lifecycle. When a request is rejected, the project manager must update the change log with the decision and the rationale provided by the Change Control Board. This maintains a complete audit trail and ensures transparency. Formally communicating the decision to the requester is essential for stakeholder management and prevents the same request from being submitted again without modification. Incorrect: Removing the request from the change log is incorrect because it destroys the project’s audit trail and historical record of decisions. Incorrect: Archiving the request without proactive communication is poor practice, as stakeholders should be informed of decisions promptly to manage expectations and maintain trust. Incorrect: Implementing a partial or scaled-back version of a rejected change without formal approval constitutes scope creep and bypasses the established governance framework. Key Takeaway: All change requests, whether approved, rejected, or deferred, must be documented in the change log with their associated rationale and communicated to relevant stakeholders.

Correct: In project management, emergency change procedures are established to handle urgent situations where waiting for a standard review cycle would result in significant negative impacts, such as safety risks or major delays. The correct approach is to follow the pre-defined emergency protocol which allows for immediate action, provided that the change is documented and formally reviewed retrospectively to ensure the project baseline and records remain accurate. Incorrect: Waiting for the scheduled Change Control Board meeting is inappropriate in this scenario because the delay would lead to a total work stoppage and potentially compromise site safety. Incorrect: Bypassing the change control process entirely is a violation of project governance; even in emergencies, changes must eventually be integrated into the project’s configuration management system to prevent scope creep and maintain an audit trail. Incorrect: Relying solely on verbal approval from a sponsor without subsequent documentation or following the emergency protocol undermines the integrity of the change management plan and leaves the project without a formal record of the modification. Key Takeaway: Emergency change procedures provide a structured way to balance the need for rapid response with the necessity of formal governance and impact assessment.

Correct: The change log is a vital project document used to track the lifecycle of every change request. For audit purposes, it provides a clear trail of what was proposed, the analysis performed, the final decision by the change control board, and the reasoning behind that decision. This ensures accountability and transparency in project governance. Incorrect: Using the change log as a primary financial ledger is incorrect because while changes may have cost implications, financial tracking is typically managed through a separate cost management system or budget tracker. Incorrect: The change log does not replace a configuration management plan; the configuration management plan defines how items are identified and controlled, whereas the change log records the actual changes requested. Incorrect: A change log is a record-keeping tool, not a voting portal or a substitute for the formal review and approval process defined in the change management plan. Key Takeaway: A well-maintained change log is the definitive source for tracking the history of project modifications and is essential for demonstrating compliance during internal or external audits.

Correct: The addition of the robotic arm is a change to the project’s outputs or deliverables, which constitutes a project scope change. This must be managed through a formal change control process to assess impacts on time, cost, and quality. In contrast, the worker resistance is an organizational change issue. Organizational change management focuses on the people side of change, ensuring that the workforce adopts the new ways of working so that the intended benefits of the project can be realized. Incorrect: Managing both through integrated change control is incorrect because while the robotic arm fits this process, worker resistance involves cultural and behavioral shifts that fall outside the standard scope, schedule, and cost baseline management. Incorrect: Defining the robotic arm as an organizational change and worker resistance as a scope change is a fundamental misunderstanding of the terms; scope refers to the work to produce deliverables, while organizational change refers to the transition of the business. Incorrect: While worker resistance could be identified as a risk, it is primarily an organizational change management challenge; furthermore, the robotic arm is a definitive change request to the scope, not a probabilistic risk event. Key Takeaway: Project scope change focuses on the ‘what’ (the deliverables), whereas organizational change focuses on the ‘who’ and ‘how’ (the people and the adoption of new processes).

Correct: The primary mechanism for preventing unauthorized changes and maintaining scope stability is a formal change control process. This process ensures that every requested change is documented, evaluated for its impact on the project’s constraints (time, cost, and quality), and either approved or rejected by the appropriate authority. By enforcing this, the Project Manager protects the project from scope creep. Incorrect: Updating the scope baseline immediately without a formal review process is a failure of governance and essentially validates scope creep, which can lead to budget overruns and delays. Incorrect: Instructing the team to stop all communication is an extreme measure that can damage stakeholder relationships and hinder collaboration; the problem is the lack of a formal process, not the communication itself. Incorrect: Requesting additional funding after the work has been done addresses the symptom but not the root cause, and it sets a poor precedent that unauthorized work will be funded retroactively. Key Takeaway: Scope stability is maintained through a robust change control system that requires formal submission, evaluation, and approval of all modifications to the project baseline.

Correct: Version control and configuration management are essential parts of information management that ensure all project participants are working from the most current and approved versions of documents. By establishing a clear process for identifying, tracking, and controlling changes to project assets, the project manager ensures data integrity and prevents the use of obsolete information. Incorrect: Information dissemination and distribution focuses on the methods and timing of sharing information with stakeholders, but without version control, even a well-distributed document could be the wrong version. Incorrect: Data collection and storage refers to the gathering of raw data and the physical or digital location where it is kept, which does not inherently solve the problem of multiple conflicting versions. Incorrect: Information archiving and disposal relates to the end-of-life process for project data, ensuring that records are kept for compliance or destroyed securely, which is not relevant to the active use of incorrect design documents during the project execution. Key Takeaway: Robust information management requires a single source of truth maintained through rigorous versioning and configuration control to avoid costly rework and stakeholder misalignment.

Correct: Knowledge is the ability to use information, experience, and insight to make decisions or take action. In this scenario, identifying the root cause (licensing fees) and formulating a strategy (negotiating discounts) demonstrates the application of knowledge to solve a project issue. Incorrect: Recording the specific figure of 50,000 GBP represents data, which consists of raw facts and figures without context. Incorrect: Calculating the CPI of 0.9 represents information, which is data that has been processed and organized to provide meaning or context. Incorrect: Presenting the report to the Sponsor is a communication activity that shares information but does not inherently represent the cognitive process of applying knowledge to a problem. Key Takeaway: The hierarchy moves from data (raw facts) to information (processed data) to knowledge (applied information and experience for decision-making).

Correct: The information management life cycle requires a structured approach to the final stages, specifically disposal and archiving. By reviewing the information management plan, the project manager ensures that data is handled according to pre-defined legal, regulatory, and organizational requirements. This distinguishes between what needs to be kept for long-term records and what should be removed to mitigate risk. Incorrect: Transferring sensitive data to a personal cloud storage is a major security violation and does not follow formal information management protocols regarding secure storage and access control. Incorrect: Deleting all logs and drafts without review ignores the archiving requirement of the life cycle. Many documents are legally required to be kept for a specific period, and immediate deletion might destroy evidence needed for future audits. Incorrect: The project manager is responsible for the project’s information management until closure. Shifting the responsibility of determining retention schedules to the operations team at the very end is inefficient and risks non-compliance, as the project team has the context needed to categorize the information correctly. Key Takeaway: The information management life cycle ensures that data is managed systematically from its creation to its eventual destruction or permanent storage, balancing accessibility with security and legal compliance.

Correct: Establishing a formal document management system with unique identifiers and approval gates is the standard for document control. It ensures that only Approved or Published versions are accessible for operational use, while Draft versions are clearly marked and restricted. This creates a single source of truth and prevents the use of unauthorized or outdated information. Incorrect: Storing documents on individual laptops and sharing via email links creates silos and version confusion, as there is no central control over which version is the current master. Incorrect: Relying on the Project Manager to manually review every change and send weekly summaries is inefficient, prone to human error, and creates a bottleneck that does not provide real-time version certainty. Incorrect: Providing full edit access to all team members on a shared drive without versioning controls or approval workflows leads to unauthorized changes and the loss of a stable project baseline. Key Takeaway: Effective document control requires a combination of unique identification, status tracking, and formal approval processes to ensure project integrity and consistency across all workstreams.

Correct: Conducting a Data Protection Impact Assessment (DPIA) is a core requirement under GDPR for projects involving high-risk processing of personal data. It allows the project team to identify potential privacy risks early and implement mitigation strategies, aligning with the principle of Privacy by Design. Incorrect: Retaining data indefinitely violates the storage limitation principle, which requires that personal data be kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed. Incorrect: While a vendor may act as a data processor, the organization (the data controller) retains ultimate accountability for GDPR compliance and cannot contractually transfer this legal responsibility away. Incorrect: Waiting until the testing phase violates the principle of Privacy by Design and Default, which mandates that data protection measures are integrated into the project from the very beginning of the design process. Key Takeaway: GDPR compliance in project management requires a proactive approach through Privacy by Design, specifically utilizing tools like the DPIA to manage risks from the outset.

Correct: Tacit knowledge is personal, context-specific, and difficult to formalize. It is best captured and transferred through social interactions such as mentoring, storytelling, and communities of practice, which allow the expert to share the ‘why’ and ‘how’ behind their actions in a way that documentation cannot. Incorrect: Creating a technical manual or troubleshooting guide focuses on explicit knowledge, which is information that can be easily codified and written down but often lacks the intuitive depth or ‘know-how’ of tacit knowledge. Performing a final project audit is a quality and compliance activity that does not facilitate the transfer of individual expertise or experience. Archiving correspondence and logs preserves data and information, but it does not capture the underlying wisdom or the cognitive processes used by the expert to solve complex problems. Key Takeaway: Tacit knowledge is effectively managed through people-based techniques that emphasize dialogue and shared experience rather than just documentation.

Correct: The primary function of a Project Management Information System (PMIS) is to provide a centralized framework that collects, integrates, and disseminates project information. In a complex environment, this ensures that all stakeholders are working from the same data, which improves the accuracy of status reports and supports evidence-based decision-making. Incorrect: Automating stakeholder management to eliminate direct communication is incorrect because a PMIS is a tool to support communication, not a replacement for the interpersonal skills and relationship management required of a project manager. Incorrect: Using artificial intelligence to automatically approve change requests is incorrect because change control requires professional judgment and governance by a Change Control Board or the project manager; a PMIS facilitates the process but does not replace the decision-making authority. Incorrect: Ensuring the project remains within the original budget by preventing deviations is incorrect because a PMIS is a monitoring and control tool that provides visibility into deviations; it does not physically prevent them or lock the project into an unrealistic plan. Key Takeaway: A PMIS serves as a vital decision-support tool that integrates various project management processes to provide visibility, consistency, and control over project data.

Correct: RAG (Red, Amber, Green) indicators are the industry standard for providing immediate visual cues regarding project health. S-curves are highly effective for steering committees as they show cumulative progress against the baseline, making it easy to see trends in cost and schedule variance over time. A probability-impact heatmap allows executives to quickly identify which risks are most critical and require their intervention. Incorrect: Detailed Gantt charts and daily resource graphs provide too much granular detail for a steering committee, which can lead to information overload and distract from strategic decision-making. Incorrect: Burndown charts are primarily used by delivery teams in agile environments for short-term tracking, and individual expense tables lack the synthesis required for high-level financial oversight. Incorrect: Fishbone diagrams and historical histograms are diagnostic or planning tools used for deep-dive analysis rather than standard status reporting for executive stakeholders. Key Takeaway: Reporting dashboards must be tailored to the audience; executives require high-level, synthesized visual data like RAG statuses and S-curves to facilitate rapid oversight and decision-making.

Correct: The most critical action involves ensuring both legal and procedural safeguards are in place. A Non-Disclosure Agreement (NDA) provides a legal framework for confidentiality, while the information management plan outlines the protocols for data classification and access control, ensuring the auditor only sees what is necessary and authorized. Incorrect: Granting full administrative access based on a verbal pledge is a major security risk as it lacks legal enforceability and violates the principle of least privilege. Using a password-protected USB drive might bypass network security but introduces physical security risks and does not address the underlying authorization or legal requirements. Providing only a summary report might prevent the auditor from fulfilling their contractual duties if they require detailed technical data to perform a valid audit, and it does not address how the sensitive data should be handled if it eventually must be shared. Key Takeaway: Security and confidentiality are managed through a combination of legal agreements, clear information management policies, and the application of data classification levels.

Correct: In project management and legal contracting, it is vital to distinguish between background IP (intellectual property that existed before the project started) and foreground IP (intellectual property created during the project). The project manager must refer to the contract to ensure that the organization retains ownership of its pre-existing assets while granting the client the agreed-upon rights to the new deliverables. Incorrect: Transferring all rights for both pre-existing algorithms and new code is incorrect because it results in the organization losing its proprietary assets, which could be used in future projects. Incorrect: Requiring a new non-disclosure agreement is incorrect because while an NDA protects confidentiality, it does not define or transfer ownership or usage rights of the intellectual property itself. Incorrect: Advising that no transfer or licensing is required is incorrect because without a clear legal transfer or license, the client may not have the legal right to use, modify, or maintain the software they paid for, leading to significant legal risks for both parties. Key Takeaway: Effective IP management requires a clear distinction between background and foreground IP within the project contract to protect the interests of both the performing organization and the client.

Correct: Archiving project records is a critical part of the closing process because it ensures the organization meets its legal and statutory obligations regarding data retention. It also provides a definitive historical record that can be used as evidence in the event of future litigation, insurance claims, or financial audits. Incorrect: Providing the operations team with a live document set describes the handover of operational documentation, not the archiving of project management records; archives are typically static snapshots of the project at completion. Incorrect: Archiving records does not justify keeping a project budget open; financial closure should occur alongside administrative closure, and late invoices should be handled through standard accounting procedures rather than by keeping a project active. Incorrect: Personal performance appraisals and salary details are sensitive HR documents and are governed by data protection laws; they are managed by the Human Resources department rather than being stored in the general project archive. Key Takeaway: Project archiving serves as the organization’s memory and legal protection, ensuring that all decisions, contracts, and changes are documented and retrievable long after the project team has disbanded.

Correct: The primary purpose of a Common Data Environment or shared information space is to establish a single source of truth. In a complex, geographically dispersed project, this ensures that all team members, regardless of their location, access the same validated and up-to-date information, which significantly reduces the risk of errors, rework, and configuration issues. Incorrect: Providing a platform for informal chat does not replace the need for a formal communication management plan, which defines how, when, and to whom information is distributed. Incorrect: While modern collaborative tools can help identify clashes or conflicts through automated reporting, the actual resolution of technical or project-related conflicts requires human intervention, professional judgment, and collaborative decision-making. Incorrect: A collaborative working environment is intended to facilitate the flow of information among all authorized team members; restricting upload and modification rights solely to the project manager creates a bottleneck and defeats the purpose of collaborative data sharing and real-time updates. Key Takeaway: Shared information spaces are critical for maintaining data integrity and ensuring that all project participants are aligned with the latest approved information, thereby improving efficiency and reducing risk in complex environments.

Correct: A decision log linked to formal governance records like Project Board minutes and change control documentation provides a clear, chronological audit trail. This evidence demonstrates not only what was decided, but also the rationale, the evidence considered, and the formal authorization by the appropriate stakeholders. Incorrect: The original Project Initiation Documentation is a baseline document created at the start of the project; while it sets the strategy, it does not record specific decisions or changes made during the execution phase. Incorrect: Informal email threads are insufficient for an audit trail because they lack formal governance, may not include all decision-makers, and are difficult to track as official project records. Incorrect: The current Risk Register is a forward-looking tool used to manage uncertainty; it does not provide a historical record of why a specific decision was authorized in the past. Key Takeaway: Robust audit trails require formal documentation of the decision-making process, including the rationale and the authority involved, to ensure accountability and transparency.

Correct: Professionalism and ethics require the proactive identification and disclosure of any potential, actual, or perceived conflicts of interest. By formally disclosing the relationship to the sponsor and governance board, the project manager maintains transparency. Requesting that an independent party handle financial approvals is a standard mitigation strategy that protects both the project manager and the organization from allegations of bias or impropriety. Incorrect: Continuing to manage the subcontractor while using a junior team member for checks is insufficient because the project manager still holds the ultimate authority and influence, which does not resolve the conflict of interest. Incorrect: Keeping the information confidential is a breach of ethical standards, as professional codes of conduct require honesty and transparency regardless of the subcontractor’s performance. Incorrect: Resigning from the project is an extreme reaction that may be unnecessary and could harm the project’s continuity; ethical issues should first be addressed through disclosure and formal management processes. Key Takeaway: Ethical project management relies on the principle of transparency; when a conflict of interest arises, it must be disclosed immediately to the appropriate authorities so that a mitigation plan can be implemented.