Multiple-Choice Question (MCQ)
A question with several answer options, only one correct.
Getting Started: How the Exam Works
Free knowledge base
CompTIA Project+ (PK0-005) — key terms, tricks & tips
Everything from the course in one searchable place: 230 entries. Use it to review before a practice test or look up a word you forgot.
230 results
Performance-Based Question (PBQ)
Tests practical skills in a simulated environment.
Getting Started: How the Exam Works
Scaled Score
Raw score converted to a standard scale for fairness.
Getting Started: How the Exam Works
Exam Domain
A major content area covered by the certification exam.
Getting Started: How the Exam Works
Domain Weighting
Indicates the relative importance of an exam domain.
Getting Started: How the Exam Works
Passing Score
Minimum score required to pass the certification exam.
Getting Started: How the Exam Works
PK0-005 Exam Format, Scoring, and Domains
To remember the exam details: '90 questions, 90 minutes, 710 to win it!'
Getting Started: How the Exam Works
PK0-005 Exam Format, Scoring, and Domains
The CompTIA Project+ (PK0-005) exam has a maximum of 90 questions and a time limit of 90 minutes. The passing score is 710 on a scale of 100-900. Remember these exact numbers.
Getting Started: How the Exam Works
PK0-005 Exam Format, Scoring, and Domains
Underestimating the time required for Performance-Based Questions (PBQs) and running out of time.
Getting Started: How the Exam Works
PK0-005 Exam Format, Scoring, and Domains
Not answering every question because there's no penalty for guessing.
Getting Started: How the Exam Works
PK0-005 Exam Format, Scoring, and Domains
Ignoring the domain weightings and studying all topics equally, rather than prioritizing.
Getting Started: How the Exam Works
Study Plan
A structured schedule outlining topics and time allocated for learning.
Getting Started: How the Exam Works
Practice Questions
Sample questions used to familiarize with exam format and content.
Getting Started: How the Exam Works
Test Anxiety
Feelings of apprehension or fear associated with taking an exam.
Getting Started: How the Exam Works
Time Management
Strategically allocating time during the exam to answer all questions.
Getting Started: How the Exam Works
Elimination Strategy
Process of removing incorrect answer choices to increase selection accuracy.
Getting Started: How the Exam Works
Exam Objectives
The specific topics and skills CompTIA expects candidates to know.
Getting Started: How the Exam Works
Simulation
An interactive exercise mimicking real-world scenarios to apply knowledge.
Getting Started: How the Exam Works
Study Strategy and Tips for Exam Day Success
To remember exam day success tips, think of 'PREPARE': **P**lan, **R**eview, **E**xercise, **P**ractice, **A**rrive early, **R**ead carefully, **E**liminate.
Getting Started: How the Exam Works
Study Strategy and Tips for Exam Day Success
The CompTIA Project+ (PK0-005) exam consists of a maximum of 90 questions and has a time limit of 90 minutes. This means you have approximately one minute per question.
Getting Started: How the Exam Works
Study Strategy and Tips for Exam Day Success
Cramming all material the night before the exam, leading to burnout and poor retention.
Getting Started: How the Exam Works
Study Strategy and Tips for Exam Day Success
Not doing enough practice questions, which means you're unfamiliar with the exam's question style.
Getting Started: How the Exam Works
Study Strategy and Tips for Exam Day Success
Ignoring the official exam objectives, leading to studying irrelevant topics or missing key ones.
Getting Started: How the Exam Works
Project
A temporary endeavor creating a unique product, service, or result.
Project Management Concepts
Operations
Ongoing, repetitive work that sustains the business.
Project Management Concepts
Temporary
Having a definite beginning and end.
Project Management Concepts
Unique
Distinct from other products, services, or results.
Project Management Concepts
Project Life Cycle
The series of phases a project passes through from start to finish.
Project Management Concepts
Business Case
A document justifying a project, outlining benefits, costs, and risks.
Project Management Concepts
Deliverable
A tangible or intangible output of a project or project phase.
Project Management Concepts
Project vs Operations and Key Terminology
P.U.T. - Projects are Unique and Temporary. This helps you remember the two core characteristics of any project.
Project Management Concepts
Project vs Operations and Key Terminology
The CompTIA Project+ exam frequently tests your ability to differentiate between projects and operations. Look for keywords like 'temporary,' 'unique,' 'definite start/end' for projects, and 'ongoing,' 'repetitive,' 'routine' for operations. Memorize the core definition of a project.
Project Management Concepts
Project vs Operations and Key Terminology
Confusing ongoing maintenance activities with projects.
Project Management Concepts
Project vs Operations and Key Terminology
Failing to recognize that even small, short-term efforts can be projects if they create a unique outcome.
Project Management Concepts
Project vs Operations and Key Terminology
Not understanding that projects can exist within an operational environment to improve operations.
Project Management Concepts
Project Manager (PM)
Responsible for planning, executing, and closing projects.
Project Management Concepts
Project Sponsor
Provides resources, authority, and strategic guidance.
Project Management Concepts
Project Team
Individuals who perform the project work and tasks.
Project Management Concepts
Stakeholder
Anyone affected by or influencing the project.
Project Management Concepts
Functional Manager
Manages personnel in a specific department.
Project Management Concepts
End-User
The ultimate consumer of the project's product or service.
Project Management Concepts
Project Roles and Responsibilities
SPoT: Sponsor provides Support, PM Plans, Team does Tasks. Remember 'SPoT' to quickly recall the main roles.
Project Management Concepts
Project Roles and Responsibilities
The exam often tests your ability to distinguish between the Project Manager's operational duties and the Project Sponsor's strategic oversight. Look for keywords like 'approves budget,' 'removes roadblocks' (Sponsor) vs. 'manages schedule,' 'assigns tasks' (PM).
Project Management Concepts
Project Roles and Responsibilities
Confusing the Project Manager's role with that of a functional manager; the PM has temporary authority over project tasks, not permanent HR duties.
Project Management Concepts
Project Roles and Responsibilities
Underestimating the importance of stakeholder engagement; ignoring even seemingly minor stakeholders can lead to major project issues.
Project Management Concepts
Project Roles and Responsibilities
Believing the Project Sponsor is involved in daily project tasks; their role is strategic, not tactical.
Project Management Concepts
Waterfall
Linear, sequential project management methodology.
Project Management Concepts
Agile
Iterative, flexible approach embracing change and collaboration.
Project Management Concepts
Scrum
Agile framework using time-boxed sprints and specific roles.
Project Management Concepts
Kanban
Agile method visualizing workflow and limiting work in progress.
Project Management Concepts
Sprint
A short, time-boxed iteration in Scrum (1-4 weeks).
Project Management Concepts
Product Backlog
Prioritized list of features for a product in Scrum.
Project Management Concepts
WIP Limit
Restriction on the number of tasks in progress at one time.
Project Management Concepts
Scrum Master
Facilitates Scrum process, removes impediments.
Project Management Concepts
Methodologies: Waterfall, Agile, Scrum, and Kanban
W.A.S.K. (Waterfall, Agile, Scrum, Kanban) – Remember WASK for the main methodologies. Or, think of a 'WASKet' of project tools!
Project Management Concepts
Methodologies: Waterfall, Agile, Scrum, and Kanban
The exam often tests your ability to match a project scenario to the most appropriate methodology. Look for keywords like 'fixed requirements' and 'sequential phases' for Waterfall, or 'evolving requirements,' 'iterative,' and 'customer feedback' for Agile/Scrum. 'Visual workflow' and 'limiting WIP' point to Kanban.
Project Management Concepts
Methodologies: Waterfall, Agile, Scrum, and Kanban
Confusing Scrum (a framework) with Agile (an umbrella philosophy). Scrum is a type of Agile, not a separate category.
Project Management Concepts
Methodologies: Waterfall, Agile, Scrum, and Kanban
Applying Waterfall to projects with highly uncertain or rapidly changing requirements, leading to expensive rework.
Project Management Concepts
Methodologies: Waterfall, Agile, Scrum, and Kanban
Believing that Agile means 'no planning'; it actually involves continuous planning and adaptation, just not all upfront.
Project Management Concepts
Change Control
Formal process to manage project modifications.
Project Management Concepts
Scope Creep
Uncontrolled expansion of project scope.
Project Management Concepts
Change Control Board (CCB)
Group that reviews and approves change requests.
Project Management Concepts
Project Risk
Uncertain event affecting project objectives.
Project Management Concepts
Risk Management
Systematic process for handling project risks.
Project Management Concepts
Risk Mitigation
Reducing risk probability or impact.
Project Management Concepts
Risk Transference
Shifting risk to a third party.
Project Management Concepts
Risk Acceptance
Acknowledging a risk without action.
Project Management Concepts
Change Control and Risk Management Basics
To remember the difference: 'R'isk is about 'R'eacting to the 'R'andom, while 'C'hange 'C'ontrol is about 'C'onsidering 'C'onscious 'C'hanges.
Project Management Concepts
Change Control and Risk Management Basics
The exam often tests your ability to distinguish between change control and risk management. Look for keywords like 'unforeseen event' or 'uncertainty' for risk, and 'requested modification' or 'formal approval' for change control. Remember that a risk, if it materializes, might *lead* to a change request.
Project Management Concepts
Change Control and Risk Management Basics
Confusing a change request with a risk. A risk is potential; a change request is a definite proposal.
Project Management Concepts
Change Control and Risk Management Basics
Ignoring small changes, leading to significant scope creep over time.
Project Management Concepts
Change Control and Risk Management Basics
Failing to document risks or changes, making it impossible to track or manage them effectively.
Project Management Concepts
Communication Plan
Document detailing how project information will be shared.
Project Management Concepts
Critical Path Method (CPM)
Technique to identify the longest sequence of project tasks.
Project Management Concepts
Critical Path
Sequence of tasks that determines the project's shortest duration.
Project Management Concepts
Float (Slack)
Amount of time a task can be delayed without affecting project end date.
Project Management Concepts
Network Diagram
Visual representation of project tasks and their dependencies.
Project Management Concepts
Dependency
Relationship where one task must finish before another can start.
Project Management Concepts
Communication Planning and Scheduling with Critical Path
COMMUNICATE: C-Channels, O-Objectives, M-Methods, M-Messages, U-Updates, N-Needs, I-Information, C-Context, A-Audience, T-Timing, E-Escalation.
Project Management Concepts
Communication Planning and Scheduling with Critical Path
The exam often tests your understanding of communication plan components and the purpose of the critical path. Remember that the critical path determines the earliest project completion date and has zero float.
Project Management Concepts
Communication Planning and Scheduling with Critical Path
Failing to identify all key stakeholders and their communication needs.
Project Management Concepts
Communication Planning and Scheduling with Critical Path
Not updating the communication plan as the project evolves or new stakeholders emerge.
Project Management Concepts
Communication Planning and Scheduling with Critical Path
Confusing tasks with float for critical path tasks, leading to misallocation of resources.
Project Management Concepts
Project Charter
Formal document authorizing project and PM authority.
Project Life Cycle Phases
Discovery Phase
Initial stage identifying problems, opportunities, and needs.
Project Life Cycle Phases
Initiation Phase
Formal recognition of a project's existence and authorization.
Project Life Cycle Phases
ROI
Return on Investment; measure of project's financial gain.
Project Life Cycle Phases
Discovery and Initiation: Business Case and Charter
Imagine a 'B.C.' (Business Case) like a historical document, explaining *why* something happened. Then, the 'P.C.' (Project Charter) is like a birth certificate, officially stating *what* is born and *who* its guardian is.
Project Life Cycle Phases
Discovery and Initiation: Business Case and Charter
The Project+ exam often tests the distinct purposes of the business case and the project charter. Remember: the business case justifies *why* the project should be done, while the project charter formally authorizes *that* the project will be done and *who* will lead it.
Project Life Cycle Phases
Discovery and Initiation: Business Case and Charter
Confusing the business case with the project charter; they serve different purposes.
Project Life Cycle Phases
Discovery and Initiation: Business Case and Charter
Skipping the formal initiation phase, leading to projects without proper authorization or clear leadership.
Project Life Cycle Phases
Discovery and Initiation: Business Case and Charter
Failing to identify key stakeholders early, which can lead to resistance or missed requirements later.
Project Life Cycle Phases
Project Scope
The work required to deliver a product, service, or result.
Project Life Cycle Phases
WBS
Hierarchical decomposition of project work into smaller, manageable parts.
Project Life Cycle Phases
Work Package
The lowest level of a WBS; a manageable unit of work.
Project Life Cycle Phases
Project Baseline
Approved version of a work product used as a fixed reference point.
Project Life Cycle Phases
Scope Baseline
Includes scope statement, WBS, and WBS dictionary.
Project Life Cycle Phases
Planning: Scope, WBS, and Baselines
To remember the three baselines, think 'SSC': Scope, Schedule, Cost. These are your 'Standard Success Checkpoints'!
Project Life Cycle Phases
Planning: Scope, WBS, and Baselines
The exam often tests the difference between project scope (what the project will deliver) and product scope (the features of the product). Also, remember that the WBS is deliverable-oriented, not task-oriented or organizational.
Project Life Cycle Phases
Planning: Scope, WBS, and Baselines
Confusing the WBS with a project schedule or organizational chart.
Project Life Cycle Phases
Planning: Scope, WBS, and Baselines
Allowing scope changes without following a formal change control process.
Project Life Cycle Phases
Planning: Scope, WBS, and Baselines
Not creating a WBS dictionary, leading to ambiguity in work package definitions.
Project Life Cycle Phases
Execution Phase
Where project work is performed to create deliverables.
Project Life Cycle Phases
Quality Assurance (QA)
Process of ensuring processes meet quality standards.
Project Life Cycle Phases
Quality Control (QC)
Process of monitoring results to identify defects.
Project Life Cycle Phases
Team Charter
Document defining team values, roles, and operating guidelines.
Project Life Cycle Phases
Resource Management
Acquiring, allocating, and managing project resources.
Project Life Cycle Phases
Corrective Action
An action taken to bring future project performance in line with the project management plan.
Project Life Cycle Phases
Execution: Managing Teams and Deliverables
To remember the execution phase, think 'DREAM': Directing, Resources, Execution, Assurance, Monitoring. It's where your plans become reality!
Project Life Cycle Phases
Execution: Managing Teams and Deliverables
The exam often tests your understanding of the project manager's role in guiding the team and managing physical and human resources during execution. Look for keywords like 'directing project work,' 'managing team performance,' and 'producing deliverables.' Remember that quality assurance focuses on processes, while quality control focuses on deliverables.
Project Life Cycle Phases
Execution: Managing Teams and Deliverables
Failing to communicate effectively with the project team and stakeholders, leading to misunderstandings or missed expectations.
Project Life Cycle Phases
Execution: Managing Teams and Deliverables
Neglecting ongoing quality assurance and control, resulting in defective deliverables and costly rework later.
Project Life Cycle Phases
Execution: Managing Teams and Deliverables
Not actively managing team conflicts or low morale, which can severely impact productivity and project success.
Project Life Cycle Phases
Monitoring and Control
Tracking, reviewing, and regulating project progress.
Project Life Cycle Phases
Key Performance Indicator (KPI)
Quantifiable measure of project success.
Project Life Cycle Phases
Baseline
Approved plan for scope, schedule, or cost.
Project Life Cycle Phases
Earned Value Management (EVM)
Integrates scope, schedule, and cost performance.
Project Life Cycle Phases
Variance Analysis
Comparing actual results to planned results.
Project Life Cycle Phases
Schedule Variance (SV)
Difference between earned value and planned value.
Project Life Cycle Phases
Cost Variance (CV)
Difference between earned value and actual cost.
Project Life Cycle Phases
Monitoring and Control: Tracking Performance
To remember the key baselines, think: 'SSC' - Scope, Schedule, Cost. These are your project's 'Standard Success Criteria'.
Project Life Cycle Phases
Monitoring and Control: Tracking Performance
The CompTIA Project+ exam emphasizes understanding the purpose of monitoring and control, and how to use baselines to measure performance. Be prepared to identify common KPIs (like SV, CV, SPI, CPI) and their implications.
Project Life Cycle Phases
Monitoring and Control: Tracking Performance
Ignoring small deviations, hoping they will resolve themselves, which can lead to larger, unmanageable problems later.
Project Life Cycle Phases
Monitoring and Control: Tracking Performance
Failing to establish clear and measurable baselines and KPIs during the planning phase, making effective monitoring impossible.
Project Life Cycle Phases
Monitoring and Control: Tracking Performance
Focusing only on schedule and cost, neglecting quality, risk, and stakeholder satisfaction metrics.
Project Life Cycle Phases
Project Closing
The final phase of the project life cycle, formally ending the project.
Project Life Cycle Phases
Project Handover
Formal transfer of project deliverables and responsibilities to operations.
Project Life Cycle Phases
Formal Sign-off
Official acceptance of project completion by stakeholders.
Project Life Cycle Phases
Lessons Learned
Documentation of project successes, failures, and insights for future use.
Project Life Cycle Phases
Administrative Closure
Completing all administrative tasks, including contracts and financials.
Project Life Cycle Phases
Archiving
Storing project documents for historical reference and legal compliance.
Project Life Cycle Phases
Organizational Process Assets (OPA)
Knowledge base of lessons learned, policies, and procedures.
Project Life Cycle Phases
Closing: Handover, Lessons Learned, and Sign-off
CLOSE IT: C-Contracts closed, L-Lessons learned, O-Operational handover, S-Sign-off, E-Equipment released, I-Information archived, T-Team released.
Project Life Cycle Phases
Closing: Handover, Lessons Learned, and Sign-off
The exam often tests the purpose and outputs of each closing activity. Remember that 'lessons learned' are a key output used for future projects, and 'formal sign-off' confirms stakeholder acceptance.
Project Life Cycle Phases
Closing: Handover, Lessons Learned, and Sign-off
Failing to get formal sign-off, leading to disputes about project completion.
Project Life Cycle Phases
Closing: Handover, Lessons Learned, and Sign-off
Skipping lessons learned sessions, causing the organization to repeat past mistakes.
Project Life Cycle Phases
Closing: Handover, Lessons Learned, and Sign-off
Neglecting proper documentation and archiving, making it difficult to retrieve information later.
Project Life Cycle Phases
Gantt Chart
Bar chart illustrating a project schedule.
Tools and Documentation
Milestone
Significant point or event in a project.
Tools and Documentation
Timeline
Simple visual of events over time.
Tools and Documentation
Gantt Charts and Other Scheduling Visuals
GANTT: 'G'o 'A'head 'N'ow, 'T'asks 'T'ime!
Tools and Documentation
Gantt Charts and Other Scheduling Visuals
The CompTIA Project+ exam expects you to differentiate between various scheduling visuals. Pay close attention to the specific components and primary use cases of Gantt charts, milestone charts, and network diagrams. Keywords like 'task duration,' 'dependencies,' and 'critical path' are strong indicators for Gantt chart questions.
Tools and Documentation
Gantt Charts and Other Scheduling Visuals
Confusing a Gantt chart with a network diagram: Gantt charts focus on time-based durations, while network diagrams emphasize task relationships and flow.
Tools and Documentation
Gantt Charts and Other Scheduling Visuals
Not understanding the critical path: Delays on non-critical path tasks might not impact the project end date, but critical path delays always do.
Tools and Documentation
Gantt Charts and Other Scheduling Visuals
Failing to update the schedule: A Gantt chart is only useful if it reflects the current project status, not just the initial plan.
Tools and Documentation
RACI Matrix
A chart defining roles for project tasks.
Tools and Documentation
Responsible (R)
Performs the work for a task.
Tools and Documentation
Accountable (A)
Ultimately answerable, approves work (one per task).
Tools and Documentation
Consulted (C)
Provides input before a decision.
Tools and Documentation
Informed (I)
Kept updated on task progress/completion.
Tools and Documentation
Responsibility Assignment Matrix
Another name for a RACI matrix.
Tools and Documentation
RACI Matrix and Responsibility Assignment
Remember RACI: 'R' for 'Runs' the task, 'A' for 'Approves' the task, 'C' for 'Chats' about the task, 'I' for 'Informs' about the task.
Tools and Documentation
RACI Matrix and Responsibility Assignment
The exam often tests your understanding of the 'one A' rule for Accountable. Be able to identify scenarios where a RACI matrix is most beneficial, such as clarifying roles or resolving conflicts.
Tools and Documentation
RACI Matrix and Responsibility Assignment
Assigning more than one 'Accountable' person to a single task, leading to confusion and lack of ultimate ownership.
Tools and Documentation
RACI Matrix and Responsibility Assignment
Over-assigning 'Consulted' or 'Informed' roles, causing communication overload and slowing down decision-making.
Tools and Documentation
RACI Matrix and Responsibility Assignment
Not involving the team in the creation of the RACI matrix, which can lead to a lack of buy-in and understanding of assigned roles.
Tools and Documentation
Burndown Chart
Visualizes work remaining over time in an agile project.
Tools and Documentation
Burnup Chart
Visualizes work completed over time against total scope.
Tools and Documentation
Story Points
Relative units of effort for user stories in agile.
Tools and Documentation
Velocity
Measure of work a team completes in an iteration.
Tools and Documentation
Backlog
Prioritized list of features or tasks for a project.
Tools and Documentation
Ideal Burndown
Expected linear progress towards zero work remaining.
Tools and Documentation
Burndown Charts and Agile Tracking Tools
Remember 'BURNDOWN' as 'Burning DOWN the work, day by day!' The line goes down as work gets done.
Tools and Documentation
Burndown Charts and Agile Tracking Tools
The exam often tests your understanding of what a burndown chart represents (work remaining) and how to interpret its lines. Pay attention to how scope changes affect the chart and the difference between burndown and burnup. Keywords like 'work remaining,' 'time,' and 'sprint progress' are crucial.
Tools and Documentation
Burndown Charts and Agile Tracking Tools
Confusing burndown (work remaining) with burnup (work completed).
Tools and Documentation
Burndown Charts and Agile Tracking Tools
Ignoring an actual burndown line that is consistently above the ideal line, indicating a problem.
Tools and Documentation
Burndown Charts and Agile Tracking Tools
Not updating the burndown chart regularly, leading to inaccurate progress tracking.
Tools and Documentation
Project Management Software
Tools for planning, executing, and tracking projects.
Tools and Documentation
Collaboration Platform
Integrated tools for team communication and document sharing.
Tools and Documentation
Status Report
Periodic update on project progress, health, and issues.
Tools and Documentation
RAG Status
Red, Amber, Green indicator for project health.
Tools and Documentation
Meeting Minutes
Official record of meeting discussions, decisions, and actions.
Tools and Documentation
Formal Communication
Structured, documented communication for official records.
Tools and Documentation
Informal Communication
Casual, less structured communication for quick updates.
Tools and Documentation
Project Software, Meeting Tools, and Status Reports
STATUS: S-tatus, T-asks, A-ctions, T-roubles, U-pdates, S-takeholders. This helps remember key elements of a status report.
Tools and Documentation
Project Software, Meeting Tools, and Status Reports
The exam often asks about the purpose and key components of different project documents. Memorize what typically goes into a status report (e.g., RAG status, progress, issues, next steps) and why it's used.
Tools and Documentation
Project Software, Meeting Tools, and Status Reports
Not tailoring communication to the audience; executives need summaries, team members need details.
Tools and Documentation
Project Software, Meeting Tools, and Status Reports
Failing to follow up on action items from meetings, rendering the meeting ineffective.
Tools and Documentation
Project Software, Meeting Tools, and Status Reports
Over-reporting or under-reporting project status, leading to stakeholder frustration or lack of awareness.
Tools and Documentation
IT Infrastructure
Hardware, software, network, and services supporting IT.
Basics of IT and Governance
Cloud Computing
On-demand delivery of IT resources over the internet.
Basics of IT and Governance
IaaS
Infrastructure as a Service; virtualized computing resources.
Basics of IT and Governance
PaaS
Platform as a Service; development environment in the cloud.
Basics of IT and Governance
SaaS
Software as a Service; applications delivered over the internet.
Basics of IT and Governance
Public Cloud
Shared, third-party owned cloud resources.
Basics of IT and Governance
Private Cloud
Cloud resources dedicated to a single organization.
Basics of IT and Governance
Hybrid Cloud
Combination of public and private cloud models.
Basics of IT and Governance
IT Infrastructure and Cloud Fundamentals
Remember the cloud service models with 'I Am So Puzzled': IaaS (Infrastructure), PaaS (Platform), SaaS (Software). Each level adds more managed services from the provider.
Basics of IT and Governance
IT Infrastructure and Cloud Fundamentals
The CompTIA Project+ exam expects you to understand the fundamental components of IT infrastructure and the differences between IaaS, PaaS, and SaaS. Look for questions that describe a scenario and ask you to identify the most suitable cloud service model or deployment type. Memorize the 'who manages what' for each service model.
Basics of IT and Governance
IT Infrastructure and Cloud Fundamentals
Confusing IaaS, PaaS, and SaaS: Remember, IaaS gives you the most control, SaaS the least.
Basics of IT and Governance
IT Infrastructure and Cloud Fundamentals
Underestimating the importance of network infrastructure: Even cloud services rely on robust network connectivity.
Basics of IT and Governance
IT Infrastructure and Cloud Fundamentals
Ignoring security and compliance in cloud decisions: Data residency and regulatory requirements are critical.
Basics of IT and Governance
Data Privacy
Individual's right to control their personal information.
Basics of IT and Governance
Compliance
Adherence to laws, regulations, and standards.
Basics of IT and Governance
GDPR
EU regulation for data protection and privacy.
Basics of IT and Governance
HIPAA
US law protecting patient health information.
Basics of IT and Governance
CCPA/CPRA
California laws granting consumer privacy rights.
Basics of IT and Governance
Privacy-by-Design
Embedding privacy into systems from the start.
Basics of IT and Governance
Data Security
Protecting data from unauthorized access or damage.
Basics of IT and Governance
DPIA
Assessment to identify and minimize data protection risks.
Basics of IT and Governance
Data Privacy, Compliance, and Regulations
Remember 'P.S.C.' for Privacy, Security, Compliance. Privacy is about YOU, Security is about LOCKS, Compliance is about RULES.
Basics of IT and Governance
Data Privacy, Compliance, and Regulations
The exam often tests your understanding of GDPR's core principles (e.g., right to be forgotten, consent) and the project manager's responsibility to ensure compliance throughout the project lifecycle. Look for keywords like 'data subject rights,' 'data protection officer,' and 'data breach notification.'
Basics of IT and Governance
Data Privacy, Compliance, and Regulations
Confusing data security with data privacy; they are related but distinct concepts.
Basics of IT and Governance
Data Privacy, Compliance, and Regulations
Assuming compliance is solely a legal team's responsibility; PMs must integrate it into projects.
Basics of IT and Governance
Data Privacy, Compliance, and Regulations
Ignoring regional regulations and only focusing on global ones, or vice-versa.
Basics of IT and Governance
Data Breach
Unauthorized access to or disclosure of sensitive data.
Basics of IT and Governance
Insider Threat
Security risk originating from within the organization.
Basics of IT and Governance
Access Control
Mechanisms to restrict who can view or use resources.
Basics of IT and Governance
Encryption
Converting data into a code to prevent unauthorized access.
Basics of IT and Governance
Risk Assessment
Identifying and evaluating potential threats and vulnerabilities.
Basics of IT and Governance
Multi-Factor Authentication (MFA)
Requires multiple verification methods for identity.
Basics of IT and Governance
Supply Chain Risk
Security vulnerabilities introduced by third-party providers.
Basics of IT and Governance
Security Considerations in Project Management
Think 'SECURE project': **S**tart early, **E**ncrypt everything, **C**ontrol access, **U**nderstand risks, **R**egular audits, **E**ducate team.
Basics of IT and Governance
Security Considerations in Project Management
The exam often asks about the importance of integrating security early in the project lifecycle and identifying common types of security risks. Look for keywords like 'proactive security planning' or 'risk assessment' in the initial phases.
Basics of IT and Governance
Security Considerations in Project Management
Treating security as an afterthought or a separate task, rather than integrating it into every project phase.
Basics of IT and Governance
Security Considerations in Project Management
Underestimating insider threats, assuming all team members are trustworthy without implementing proper controls.
Basics of IT and Governance
Security Considerations in Project Management
Failing to conduct regular security risk assessments and update security plans as the project evolves.
Basics of IT and Governance
Change Management
Structured approach to managing IT system changes.
Basics of IT and Governance
Request for Change (RFC)
Formal document proposing an IT system modification.
Basics of IT and Governance
Change Advisory Board (CAB)
Group that assesses and approves IT changes.
Basics of IT and Governance
IT Governance
Framework ensuring IT supports organizational objectives.
Basics of IT and Governance
COBIT
Framework for IT governance and management.
Basics of IT and Governance
ITIL
Framework for IT service management best practices.
Basics of IT and Governance
Policy
High-level rule or principle guiding IT behavior.
Basics of IT and Governance
Procedure
Detailed, step-by-step instructions for tasks.
Basics of IT and Governance
IT Change Management and Governance Processes
To remember the Change Management Process: 'R.A.P.I.R.' — Request, Assess, Plan, Implement, Review.
Basics of IT and Governance
IT Change Management and Governance Processes
The exam often tests your understanding of the purpose of change management (e.g., 'reduce risk,' 'ensure stability') and the role of the CAB. Memorize the typical steps in the change management process and the general purpose of frameworks like ITIL and COBIT.
Basics of IT and Governance
IT Change Management and Governance Processes
Skipping the impact assessment phase, leading to unforeseen system conflicts.
Basics of IT and Governance
IT Change Management and Governance Processes
Failing to communicate changes effectively to end-users, causing confusion and resistance.
Basics of IT and Governance
IT Change Management and Governance Processes
Not having a rollback plan, which can turn a failed change into a catastrophic outage.
Basics of IT and Governance