DEV Community: Falade Timilehin

BABOK® v3: BA Planning and Monitoring

Falade Timilehin — Sun, 13 Sep 2026 12:14:26 +0000

Business Analysis Planning and Monitoring: What a Business Analyst Really Does

When people hear the term Business Analyst, they often think about requirements, meetings, documents, and asking stakeholders what they need.

Those things are important, but they are only part of the job.

A good Business Analyst also needs to think about how the analysis itself will be carried out. Who needs to be involved? What approach should the team use? How will decisions be made? Where will requirements and other information be stored? How will we know whether the analysis is working?

This is where Business Analysis Planning and Monitoring becomes important.

The BABOK Guide describes Business Analysis Planning and Monitoring as a knowledge area covering five key tasks:

Plan Business Analysis Approach
Plan Stakeholder Engagement
Plan Business Analysis Governance
Plan Business Analysis Information Management
Identify Business Analysis Performance Improvements

These tasks are not necessarily performed once, in a strict sequence. Business analysis work is often iterative, and several tasks can happen at the same time.

What is Business Analysis Planning?

Business Analysis Planning is about deciding how the Business Analyst will approach the work.

Before jumping into workshops, interviews, requirements documents, or process models, the analyst needs to understand the situation.

For example, suppose a company wants to replace an old customer management system.

There might be several questions to answer first:

Who needs to be involved?

How will requirements be gathered?

Should the project follow a predictive approach such as Waterfall, or an adaptive approach such as Agile?

Who has authority to approve requirements?

How will changes be controlled?

Where will project information be stored?

How will progress and performance be measured?

These decisions form part of the Business Analysis Approach.

The goal is simple. The team needs a clear way of working before analysis begins.

The Five BABOK Tasks

The five tasks provide a useful structure for planning and monitoring Business Analysis work.

Each task produces an output that supports other activities. The outputs are not necessarily large documents. Depending on the organisation and project, an output might be a formal document, part of a project plan, a set of records, or another form of business analysis information.

1. Plan Business Analysis Approach

The first task is deciding how Business Analysis work will be performed.

The Business Analyst considers the methodology, activities, tasks, deliverables, timing, resources, and level of formality required.

For example, a large regulatory project might require formal documentation, defined approval points, and detailed traceability.

A small Agile product team might work through shorter planning cycles, with analysis performed alongside each iteration.

The important point is to select an approach that fits the situation.

Output:

Business Analysis Approach

The Business Analysis Approach describes how the analysis work will be performed, including planned activities, tasks, deliverables, and the way the work will be organised.

Frequently used BABOK techniques include:

• Business Cases

• Financial Analysis

• Functional Decomposition

• Item Tracking

• Risk Analysis and Management

These techniques help the analyst understand the work, break down activities, consider costs and risks, and track relevant work items.

A useful way to think about this task is:

“How are we going to do the Business Analysis?”

2. Plan Stakeholder Engagement

The second task focuses on people.

A Business Analyst needs to identify the stakeholders involved in the initiative and understand their roles, interests, influence, concerns, and communication needs.

Stakeholders might include:

• Project sponsors

• Customers

• End users

• Subject Matter Experts

• Project Managers

• Business owners

• Suppliers

• Regulators

The analyst then decides how to establish and maintain effective working relationships with these stakeholders.

Output:

Stakeholder Engagement Approach

The approach describes how stakeholders will be involved, communicated with, and supported during the initiative.

Frequently used BABOK techniques include:

• Brainstorming

• Business Rules Analysis

• Document Analysis

• Interviews

• Lessons Learned

• Mind Mapping

• Organisational Modelling

• Process Modelling

• Risk Analysis and Management

• Scope Modelling

• Stakeholder List, Map, or Personas

• Survey or Questionnaire

• Workshops

For example, a stakeholder map might show who has high influence and who has high interest.

An interview might help the analyst understand the concerns of a Subject Matter Expert.

A workshop might bring several stakeholders together to reach agreement.

The question behind this task is:

“Who needs to be involved, and how should we work with them?”

3. Plan Business Analysis Governance

Governance is about decision-making.

A project might involve dozens of people. Without clear governance, disagreements over requirements, priorities, scope, and changes can slow the project down.

Business Analysis Governance defines how decisions will be made about requirements and designs. This includes reviews, approvals, prioritisation, and change control.

Output:

Governance Approach

The Governance Approach identifies decision-makers and explains how approvals, prioritisation, reviews, and change control will operate.

Frequently used BABOK techniques include:

• Document Analysis

• Interviews

• Organisational Modelling

• Process Modelling

• Workshops

For example, suppose a stakeholder asks for a new feature halfway through a project.

The Business Analyst should not simply add the request to the requirements.

The request needs to be assessed.

What is the business reason?

What impact will the change have?

Will the deadline change?

Will the budget change?

Does the change affect other requirements?

Who has authority to approve it?

The governance process gives the team a structured way to answer these questions.

The question behind this task is:

“Who decides what, and how are those decisions controlled?”

4. Plan Business Analysis Information Management

Business Analysts deal with a large amount of information.

This includes:

• Requirements

• Meeting notes

• Stakeholder concerns

• Business rules

• Process models

• Designs

• Decisions

• Workshop outcomes

• Policies

• Regulatory information

Without proper information management, important details become difficult to find.

People might start working from different versions of the same requirement.

A decision made three weeks earlier might be forgotten.

A stakeholder might challenge a requirement because there is no clear record showing where the requirement came from.

Output:

Information Management Approach

The Information Management Approach explains how Business Analysis information will be captured, organised, stored, accessed, traced, and used during and after the change.

Frequently used BABOK techniques include:

• Interviews

• Item Tracking

• Lessons Learned

• Mind Mapping

• Process Modelling

For example, the analyst might establish a naming convention for requirements, define access permissions, agree where documents will be stored, and establish how changes will be tracked.

The question behind this task is:

“How will we manage the information we create and use?”

5. Identify Business Analysis Performance Improvements

The final task focuses on learning and improvement.

Planning does not end when the project starts.

The Business Analyst needs to monitor how well the analysis is being performed.

Questions might include:

Are stakeholders providing information on time?

Are requirements clear?

Are requirements being approved efficiently?

Are there recurring misunderstandings?

Are workshops producing useful results?

Are analysis activities taking longer than expected?

What should we do differently next time?

Output:

Business Analysis Performance Assessment

The assessment records the results of evaluating Business Analysis performance, including identified causes of performance gaps and potential improvements.

Frequently used techniques include:

• Brainstorming

• Interviews

• Item Tracking

• Lessons Learned

• Metrics and Key Performance Indicators

• Observation

• Process Analysis

• Process Modelling

• Reviews

• Risk Analysis and Management

• Root Cause Analysis

• Survey or Questionnaire

• Workshops

This task is particularly important because the Business Analyst is not only interested in whether the project delivers a solution. The analyst also needs to understand whether the analysis process itself worked well.

For example, if requirements repeatedly needed clarification because stakeholders were not involved early enough, the analyst might change the stakeholder engagement approach on the next initiative.

The question behind this task is:

“How well did our Business Analysis work, and what should we improve?”

BABOK Planning and Monitoring at a Glance

Task 1: Plan Business Analysis Approach

Output: Business Analysis Approach

Main question: How will we perform the analysis?

Key techniques: Business Cases, Financial Analysis, Functional Decomposition, Item Tracking, Risk Analysis and Management.

Task 2: Plan Stakeholder Engagement

Output: Stakeholder Engagement Approach

Main question: Who needs to be involved, and how will we work with them?

Key techniques: Brainstorming, Interviews, Mind Mapping, Stakeholder List, Map, or Personas, Risk Analysis and Management, Workshops.

Task 3: Plan Business Analysis Governance

Output: Governance Approach

Main question: Who makes decisions, and how will decisions be controlled?

Key techniques: Document Analysis, Interviews, Organisational Modelling, Process Modelling, Workshops.

Task 4: Plan Business Analysis Information Management

Output: Information Management Approach

Main question: How will Business Analysis information be captured, organised, stored, and accessed?

Key techniques: Interviews, Item Tracking, Lessons Learned, Mind Mapping, Process Modelling.

Task 5: Identify Business Analysis Performance Improvements

Output: Business Analysis Performance Assessment

Main question: How well is Business Analysis performing, and what should improve?

Key techniques: Brainstorming, Interviews, Lessons Learned, Metrics and KPIs, Observation, Process Analysis, Process Modelling, Reviews, Root Cause Analysis, Surveys or Questionnaires, Workshops.

The IIBA describes techniques as methods Business Analysts use to perform tasks. The BABOK technique list is broad, so the techniques above represent those commonly associated with these planning and monitoring tasks rather than a requirement to use every technique on every project.

Choosing the Right Technique

One thing worth remembering is that BABOK does not mean a Business Analyst should use every technique available.

The technique should match the situation.

For example:

If you need detailed information from one stakeholder, use an Interview.

If you need several stakeholders to reach agreement, use a Workshop.

If you need to understand existing policies or procedures, use Document Analysis.

If you need to understand relationships between stakeholders, use a Stakeholder List, Map, or Personas.

If you need to understand why a problem keeps occurring, use Root Cause Analysis.

If you need to measure performance, use Metrics and Key Performance Indicators.

If you need to identify possible risks, use Risk Analysis and Management.

If you need to understand how a process works, use Process Modelling.

The Business Analyst uses judgement to select the technique or combination of techniques most suitable for the situation. IIBA also states that BABOK techniques are not intended to be an exhaustive list, and practitioners are expected to select and adapt techniques according to context.

A Simple Example

Consider a hospital introducing a new electronic appointment system.

The Business Analyst starts by understanding the need.

Patients are experiencing long waiting times when booking appointments.

The analyst then identifies stakeholders.

These might include patients, reception staff, clinicians, IT teams, managers, and external suppliers.

The analyst then plans the Business Analysis approach.

Interviews might be used with staff. Workshops might be used to agree requirements. Process Modelling might be used to understand the current appointment process.

Next, stakeholder engagement is planned.

The analyst identifies which stakeholders need to be consulted, informed, involved, or asked to approve decisions.

Governance is then established.

The team agrees who approves requirements, who makes priority decisions, and how changes are handled.

Information management is also planned.

Requirements, workshop notes, decisions, and stakeholder feedback need to be stored consistently and securely.

Finally, performance is monitored.

The analyst checks whether stakeholder engagement is working, whether requirements are being completed as expected, and whether the analysis approach needs improvement.

This example shows how the five BABOK tasks connect.

Why the Outputs Matter

The outputs from these tasks are useful because they create a clear structure around Business Analysis work.

The Business Analysis Approach tells the team how analysis will be performed.

The Stakeholder Engagement Approach explains how people will be involved.

The Governance Approach establishes decision-making and change control.

The Information Management Approach explains how analysis information will be managed.

The Business Analysis Performance Assessment captures lessons about how the analysis performed and where improvements are needed.

These outputs also support other Business Analysis activities. For example, the Business Analysis Approach feeds into stakeholder engagement, governance, information management, and performance improvement. The Governance Approach then helps control requirements decisions and changes.

How Everything Fits Together

Business Analysis Planning and Monitoring brings several activities together.

The Business Analyst:

Understands the need and context.
Selects an appropriate Business Analysis approach.
Plans how stakeholders will be engaged.
Establishes governance and decision-making responsibilities.
Plans how Business Analysis information will be stored and managed.
Monitors Business Analysis performance.
Identifies opportunities for improvement.

These activities are connected.

The chosen approach affects stakeholder engagement.

Stakeholder roles influence governance.

Governance affects how requirements and changes are approved.

Information management supports traceability and communication.

Performance monitoring helps the analyst improve the approach throughout the work.

Final Thoughts

Business Analysis Planning and Monitoring is about creating the conditions for effective analysis.

A Business Analyst needs to think about the approach, stakeholders, governance, information, and performance before and throughout the work.

The BABOK tasks provide a useful framework:

Plan the approach.

Plan stakeholder engagement.

Plan governance.

Plan information management.

Improve Business Analysis performance.

The techniques then provide practical ways to carry out those tasks.

The key lesson is simple.

Good analysis needs structure.

You need the right approach.

You need the right people involved.

You need clear decision-making.

You need organised information.

You need measurable performance.

And you need to learn from the work as the initiative progresses.

When these areas work together, the Business Analyst has a stronger foundation for helping an organisation understand problems, manage change, make better decisions, and deliver value.

CompTIA Network+: IPv4 Network Addressing

Falade Timilehin — Sat, 12 Sep 2026 18:08:02 +0000

Mastering IPv4 Network Addressing & Subnetting: A CompTIA Network+ Guide

Subtitle: A comprehensive breakdown of public vs. private IPs, RFC 1918, APIPA, classful subnetting, supernetting, and calculating subnet boundaries.

Understanding IPv4 addressing and subnetting is one of the foundational requirements for passing the CompTIA Network+ exam and managing real-world network infrastructure. As the available pool of global IPv4 addresses shrinks, knowing how to structure, divide, and aggregate IP address space efficiently is critical for network administrators.

Below is a complete breakdown of the key concepts covered in this core training module.

1. Public vs. Private IP Addresses & RFC 1918

IPv4 relies on 32-bit addresses split into network and host portions. To mitigate the exhaustion of the ~4 billion total IPv4 addresses, modern network design relies heavily on private addressing and translation protocols.

Public IP Addresses: Unique across the global web, assigned by IANA/ISPs, and strictly required for direct Internet access.
Private IP Addresses: Reserved for internal use within Local Area Networks (LANs). Organizations can reuse private ranges internally without conflict.
Network Address Translation (NAT): Maps private IP addresses to a single public IP at the router interface, allowing local devices to communicate externally while conserving public IPv4 space.

Reserved Private Ranges (RFC 1918)

Network Class	Private Address Range	Default Subnet Mask	CIDR Prefix
Class A	`10.0.0.0` – `10.255.255.255`	`255.0.0.0`	`/8`
Class B	`172.16.0.0` – `172.31.255.255`	`255.240.0.0`	`/12`
Class C	`192.168.0.0` – `192.168.255.255`	`255.255.0.0`	`/16`

2. Specialized IPv4 Addresses & Fallback Protocols

Network interfaces rely on specific diagnostic and fallback address types for local routing:

Default Gateway: The router IP interface on the local segment that routes traffic destined for outside subnets or the Internet.
Loopback Address (127.0.0.1): Routes traffic straight back to the local network adapter to diagnose local TCP/IP stack functionality (ping 127.0.0.1).
Link-Local / APIPA (169.254.0.0/16): Automatic Private IP Addressing automatically assigns an IP in the 169.254.0.1–169.254.255.254 range when a client fails to reach a DHCP server. While APIPA allows local host-to-host communication, devices cannot pass through a router to reach external networks.
IPv6 EUI-64: In IPv6 environments, devices auto-assign unique link-local addresses using the hardware MAC address rather than relying on DHCP.

3. Subnetting Class A, B, and C Networks

Subnetting divides a single large network into smaller, isolated subnets to limit broadcast domains and optimize security.

Base-2 Math: Every octet consists of 8 binary bits (128, 64, 32, 16, 8, 4, 2, 1).
CIDR Notation: Classless Inter-Domain Routing (e.g., /24) defines exact network bit lengths beyond rigid classful limits.
Class C Subnetting: Standard /24 (255.255.255.0) provides 256 total IPs with 254 usable host addresses (subtracting the Network ID and Broadcast address).
Class B Subnetting: Standard /16 (255.255.0.0) supports ~65,000 hosts. Borrowing bits to create a /20 mask (255.255.240.0) yields 16 subnets of ~4,000 usable hosts each.
Class A Subnetting: Standard /8 (10.0.0.0) offers 24 host bits (~16 million hosts). Organizations often subnet Class A down to a /17 (255.255.128.0) to yield 512 subnets of ~30,000 hosts, or straight down to /24 blocks for simpler host management.

4. Calculating Subnet Boundaries

Determining host placement and increments requires finding the subnet block size:

Calculate Increments: Subtract the value of the custom subnet mask octet from 256.
Track Subnet Ranges: Increments dictate the step sizes (e.g., increments of 64 in an octet yield subnets starting at .0, .64, .128, and .192).
Local Routing: Devices sharing the exact same subnet boundary communicate directly; devices outside the boundary require a default gateway.

5. Supernetting Strategies (Route Aggregation)

Where subnetting breaks networks down, supernetting aggregates contiguous smaller networks into a single larger route entry.

How It Works: Shifts the subnet mask boundary to the left, decreasing network bits and expanding available host space.
Example: Merging four Class C /24 subnets into a single /22 network (255.255.252.0) supports ~1,000 hosts without shifting to a Class B scheme.
Key Advantage: Reduces router processing load and shrinks global routing tables while preserving existing IP allocations.

Key Takeaways for the CompTIA Network+ Exam

APIPA Signals DHCP Failure: Spotting a 169.254.x.x address is an instant diagnostic clue that DHCP renewal or reachability failed.
Usable Hosts Formula: Always calculate host capacity as $2^h - 2$ (reserving the network ID and broadcast IP).
Supernetting vs. Subnetting: Remember that subnetting moves the mask to the right (smaller networks, fewer hosts), while supernetting moves the mask to the left (larger networks, fewer routes).

CompTIA Network+: IPv4 Network Addressing

Falade Timilehin — Sat, 12 Sep 2026 17:59:29 +0000

If you’re studying for the CompTIA Network+ or working in IT, mastering IPv4 addressing and subnetting is non-negotiable.

Most people struggle with binary math and subnetting calculations, but once you break down the core mechanics, it clicks.

Here is your ultimate cheat sheet to mastering IPv4 for the Network+ exam and real-world network admin tasks. 👇

1. Public vs. Private IP Addresses (RFC 1918)

Private IPs aren't routable on the public web. Devices use NAT (Network Address Translation) at the router to communicate globally.

Memorize these three reserved RFC 1918 ranges for the exam:

Class A: 10.0.0.0 – 10.255.255.255 (/8 | 255.0.0.0)
Class B: 172.16.0.0 – 172.31.255.255 (/12 | 255.240.0.0)
Class C: 192.168.0.0 – 192.168.255.255 (/16 | 255.255.0.0)

2. Crucial IPs to Spot instantly

Loopback (127.0.0.1): Tests your local TCP/IP stack (ping 127.0.0.1).
APIPA (169.254.0.1 – 169.254.255.254): If a device gets a 169.254.x.x address, your DHCP server failed to respond. It can talk locally, but can't reach the internet.

3. Quick Subnet Boundary Formula

Forget slow binary conversions during exam time. Use the Magic Number rule:

Find the Block Size: Subtract the subnet mask's changing octet from 256.
Example: For a /26 mask (255.255.255.192), $256 - 192 =$ 64 (Block size is 64).
Determine Subnets: Count up by your block size (0, 64, 128, 192).
Calculate Usable Hosts: Always use $2^h - 2$ (Subtract 1 for the Network ID and 1 for the Broadcast Address).

4. Subnetting vs. Supernetting

Subnetting: Carves a large network into smaller ones to reduce broadcast traffic.
Supernetting (Route Summarization): Combines multiple small networks into a single route entry (e.g., merging four /24 subnets into one /22 route) to save router memory and CPU.

💡 Pro-Tip for Exam Day: The moment your tutorial time starts, write out the 8-bit values (128, 64, 32, 16, 8, 4, 2, 1) on your scratch paper!

What’s the one networking concept that took you the longest to master? Let me know in the comments! 💬

CompTIA #NetworkPlus #Networking #ITCertification #Subnetting #Cybersecurity #ITCareers #TechTips

Business Analysis: An Introduction to BABOK® v3

Falade Timilehin — Thu, 03 Sep 2026 10:28:39 +0000

1. What Is Business Analysis?

Business analysis is the practice of identifying business needs, understanding problems and opportunities, and determining solutions that deliver value to stakeholders.

A Business Analyst looks at three major areas:

• People
• Processes
• Technology

The goal is to understand how an organisation currently works, identify what needs to change, and help define a solution that supports the organisation's objectives.

Business analysis applies to many types of work, including:

• New projects
• System implementations
• Business process improvements
• Digital transformation
• Product development
• Organisational change
• Continuous improvement

For example, suppose a bank receives many customer complaints because opening an account takes three days.

A Business Analyst would investigate:

• Why does account opening take three days?
• Which teams are involved?
• Which steps create delays?
• Which systems are being used?
• What information does the customer provide?
• What regulations must the bank follow?
• What would the future process look like?

The BA then works with stakeholders to define requirements for improving the process.

2. The Role of the Business Analyst

A Business Analyst is not limited to one job title.

Business analysis represents a set of activities and responsibilities.

Different roles perform business analysis activities.

Examples include:

• Business Analyst
• Systems Analyst
• Product Manager
• Management Consultant
• Process Analyst
• Business Architect
• Product Owner

Systems Analyst

A Systems Analyst focuses heavily on technology and systems.

They help translate business needs into clear system requirements.

For example:

Business need:

"Customers need faster access to their account statements."

System requirement:

"The system shall allow customers to download statements for the previous 24 months in PDF format."

Management Consultant

A Management Consultant focuses on business strategy, operations and organisational problems.

For example, a consultant might analyse why a company's operating costs are increasing and recommend changes to its operating model.

Product Manager

A Product Manager focuses on creating products that deliver value to customers and the organisation.

They need to understand:

• Customer problems
• Market needs
• Business objectives
• Product opportunities
• Priorities
• Product performance

3. Why Business Analysis Is Valuable

Good business analysis reduces the risk of building the wrong solution.

Imagine a company spends £500,000 developing a new system.

Six months after launch, users complain that the system does not solve their problems.

The technical team might have built the system correctly.

The problem was poor understanding of the business need.

This is where business analysis provides value.

A BA helps an organisation:

• Understand the real problem
• Identify the right stakeholders
• Define clear requirements
• Manage stakeholder expectations
• Reduce misunderstandings
• Control scope
• Identify risks early
• Improve processes
• Support accurate cost estimates
• Support accurate delivery estimates
• Improve communication
• Measure whether the solution delivers value

A strong BA also challenges a proposed project when the project does not align with business objectives.

The question is not:

"How do we build this?"

The better question is:

"Why are we building this, and what business problem are we solving?"

4. The Six BABOK® Knowledge Areas

BABOK® v3 identifies six knowledge areas.

You should learn these because they form an important part of Business Analysis terminology.

Business Analysis Planning and Monitoring
Elicitation and Collaboration
Requirements Life Cycle Management
Strategy Analysis
Requirements Analysis and Design Definition
Solution Evaluation

4.1 Business Analysis Planning and Monitoring

This focuses on planning how the BA work will happen.

The BA considers:

• Who needs to be involved?
• How will information be gathered?
• How will requirements be documented?
• How will requirements be prioritised?
• How will stakeholders communicate?
• How will progress be monitored?

Stakeholder analysis forms an important part of planning.

4.2 Elicitation and Collaboration

Elicitation means obtaining information from stakeholders.

A BA does not simply wait for stakeholders to provide requirements.

The BA actively investigates and explores their needs.

Common elicitation techniques include:

• Interviews
• Workshops
• Surveys
• Observation
• Brainstorming
• Document analysis
• Focus groups
• Prototyping

For example, if you are developing a new hospital appointment system, you might interview:

• Doctors
• Nurses
• Reception staff
• Patients
• IT staff
• Managers

Each stakeholder sees the problem differently.

The BA brings those perspectives together.

5. Requirements Life Cycle Management

Requirements do not simply get written once and forgotten.

They need to be managed throughout the initiative.

The BA needs to understand:

• Where each requirement came from
• Why the requirement exists
• Who owns the requirement
• How important the requirement is
• What solution component satisfies it
• Whether the requirement has changed

This is where traceability becomes important.

For example:

Business requirement:

"Reduce customer onboarding time."

↓

Stakeholder requirement:

"Customer service staff need a faster customer verification process."

↓

Functional requirement:

"The system shall automatically retrieve customer information from the verification service."

↓

Test:

"Verify that customer information is retrieved automatically."

This creates a connection between the original business objective and the final solution.

6. Strategy Analysis

Strategy analysis focuses on understanding the current state and determining the desired future state.

A BA asks:

"Where are we now?"

"What do we want to achieve?"

"What is stopping us?"

"What needs to change?"

For example:

Current state:

• Customers complete paper forms.
• Staff manually enter information.
• Processing takes two days.
• Errors occur during data entry.

Future state:

• Customers complete digital forms.
• Information enters the system automatically.
• Processing takes 30 minutes.
• Validation reduces errors.

The BA then analyses the gap between the current state and future state.

This is known as gap analysis.

7. Requirements Analysis and Design Definition

This area focuses on analysing requirements and defining possible solutions.

Requirements need to be:

• Clear
• Relevant
• Testable
• Feasible
• Understandable
• Consistent
• Traceable

The BA works with stakeholders and technical teams to determine how the requirements might be satisfied.

Requirements and designs are closely connected.

As the team learns more about the problem, requirements might change.

As the team explores possible designs, new requirements might emerge.

Therefore, requirements and design evolve together.

8. Solution Evaluation

After implementing a solution, the BA needs to determine whether the solution delivered the expected value.

For example, suppose the business introduced an automated customer onboarding system.

The original objective was:

"Reduce onboarding time from two days to 30 minutes."

After implementation, the BA measures:

• Average onboarding time
• Error rate
• Customer satisfaction
• Staff productivity
• Processing costs
• Number of failed applications

If onboarding time falls from two days to 25 minutes, the solution achieved the target.

If onboarding time remains at two days, further investigation is required.

The BA therefore asks:

"Did the solution solve the original problem?"

9. The Business Analysis Core Concept Model

BABOK® uses the Business Analysis Core Concept Model, known as BACCM.

It contains six core concepts:

Change
Need
Solution
Stakeholder
Value
Context

A useful way to remember them is:

Need → Change → Solution → Value

within a particular Context and involving Stakeholders.

Change

Change is the transformation from an existing state to a future state.

Example:

Moving from manual invoice processing to automated invoice processing.

Need

A need represents a problem or opportunity requiring attention.

Example:

"Invoice processing takes too long."

Solution

A solution addresses a need.

Example:

An automated invoice management system.

Stakeholder

A stakeholder is a person or group involved in, affected by, or interested in the change.

Example:

• Customers
• Employees
• Managers
• Suppliers
• Regulators
• Developers

Value

Value represents the benefit, importance or worth delivered to stakeholders.

Example:

Automating invoices might produce:

• Lower processing costs
• Faster payments
• Fewer errors
• Better visibility

Context

Context represents the circumstances surrounding the change.

This includes:

• Organisation
• Culture
• Technology
• Regulations
• Market
• Processes
• Resources

A solution that works in one organisation might fail in another because the context differs.

10. Stakeholders

Stakeholders are central to business analysis.

Common project stakeholders include:

Sponsor

The sponsor supports the initiative, establishes goals and provides resources or funding.

Business Analyst

The BA investigates the business need, manages requirements and supports the definition of the solution.

Project Manager

The Project Manager focuses on delivery.

Typical areas include:

• Scope
• Budget
• Schedule
• Quality
• Risks
• Resources

Domain Subject Matter Expert

A Domain SME understands the business area.

For example, in a banking project, a compliance specialist might act as a Domain SME.

Implementation Subject Matter Expert

An Implementation SME understands how the solution will be implemented.

Examples include:

• Developer
• Solution Architect
• Database specialist
• Technical architect

Tester

The tester verifies whether the solution satisfies the defined requirements and quality expectations.

11. External Stakeholders

Not every stakeholder works inside the organisation.

External stakeholders might include:

• Customers
• Suppliers
• Government agencies
• Regulators
• Partners
• Investors
• External consultants

For example, a banking system might involve internal employees, customers, payment providers and financial regulators.

The BA needs to understand each stakeholder's interests and influence.

12. Requirements Classification

BABOK® divides requirements into four major categories.

1. Business Requirements

Business requirements explain why the organisation needs the change.

Example:

"Reduce customer onboarding time from two days to 30 minutes."

This describes the business objective.

2. Stakeholder Requirements

Stakeholder requirements describe what stakeholders need from the solution.

Example:

"Customer service staff need to view customer verification results within the onboarding screen."

This connects the business need to stakeholder needs.

3. Solution Requirements

Solution requirements describe what the solution needs to provide.

They include:

Functional requirements

and

Non-functional requirements.

Functional requirement

Describes what the system must do.

Example:

"The system shall send an email confirmation after successful registration."

Non-functional requirement

Describes qualities or characteristics of the solution.

Examples:

• Performance
• Security
• Reliability
• Usability
• Availability
• Scalability

Example:

"The system shall display the customer's dashboard within two seconds."

4. Transition Requirements

Transition requirements support the movement from the current state to the future state.

Examples include:

• Data migration
• Staff training
• User support
• System deployment
• Business continuity
• Temporary processes

For example, employees might need training before a new CRM system launches.

Training is therefore part of the transition requirements.

13. Requirements vs Design

This distinction is important.

A requirement describes a need or capability.

A design describes how the solution will satisfy the requirement.

Example:

Requirement:

"Customers need to reset their passwords without contacting customer support."

Design:

A password-reset screen using email verification and a temporary reset token.

The requirement describes what is needed.

The design describes how the solution addresses the need.

Requirements and designs often evolve together.

As the team develops the design, they might identify missing requirements.

As stakeholders refine their requirements, the design might also change.

14. A Simple Business Analysis Example

Let's bring everything together.

Imagine a company receives customer complaints because refunds take seven days.

Step 1: Identify the need

Customers want faster refunds.

Step 2: Understand the current state

The BA investigates the process.

They find:

• Customer requests refund.
• Customer service reviews request.
• Finance approves refund.
• Finance manually processes payment.
• Customer receives confirmation.

Average processing time: seven days.

Step 3: Identify stakeholders

The BA speaks to:

• Customers
• Customer service
• Finance
• Operations
• IT
• Compliance

Step 4: Define the business requirement

"Reduce average refund processing time from seven days to two days."

Step 5: Define stakeholder requirements

Finance needs an approval workflow.

Customer service needs visibility of refund status.

Customers need confirmation when the refund is processed.

Step 6: Define solution requirements

Functional:

"The system shall route refund requests to the appropriate finance approver."

Non-functional:

"The refund system shall maintain an audit trail of all approval actions."

Step 7: Define transition requirements

Staff need training.

Existing refund records need migration.

The new process needs a controlled rollout.

Step 8: Evaluate the solution

After implementation, the BA measures the results.

Average refund time:

Before: 7 days

After: 1.8 days

The solution has achieved the target.

15. What You Should Remember for Your Exam

Focus on these points:

Business analysis:

Identifies needs, problems and opportunities and helps define solutions that deliver value.

Six knowledge areas:

Planning and Monitoring
Elicitation and Collaboration
Requirements Life Cycle Management
Strategy Analysis
Requirements Analysis and Design Definition
Solution Evaluation

BACCM:

Change
Need
Solution
Stakeholder
Value
Context

Four requirement categories:

Business
Stakeholder
Solution
Transition

Solution requirements:

Functional
Non-functional

Key distinction:

Requirement = what is needed.

Design = how the need will be satisfied.

The BA's central question is:

"What business problem are we solving, who needs the change, what does the future state look like, and how will we know the solution delivered value?"

This is the foundation you need before moving into Business Analysis Planning and Monitoring.

CompTIA Network+: Ports & Protocols

Falade Timilehin — Sun, 16 Aug 2026 12:26:46 +0000

Introduction

Ports and protocols are essential parts of computer networking. A protocol defines how devices communicate. A port identifies the network service or application receiving the communication.

For CompTIA Network+, you need to recognise common protocols, their purpose, transport protocol, and default port number.

For example, when you visit a website using HTTPS, your computer communicates with a web server using HTTPS over TCP port 443.

1. Ports and Protocols

A port is a logical communication endpoint used by network services.

Port numbers range from 0 to 65,535.

The main port ranges are:

0 to 1,023: Well-known ports
1,024 to 49,151: Registered ports
49,152 to 65,535: Dynamic or ephemeral ports

TCP and UDP use port numbers.

TCP provides reliable, connection-oriented communication. It establishes a connection before transferring data and uses acknowledgements and retransmissions.

UDP provides connectionless communication. It has lower overhead but does not guarantee delivery.

2. FTP and SFTP

FTP stands for File Transfer Protocol. FTP transfers files between a client and server.

FTP normally uses:

TCP 21: Control connection
TCP 20: Data connection in active mode

FTP does not encrypt usernames, passwords, or file contents.

SFTP stands for SSH File Transfer Protocol. SFTP transfers files securely through an SSH connection.

SFTP uses:

TCP 22

SFTP encrypts the communication between the client and server.

Remember:

FTP = TCP 20/21
SFTP = TCP 22

3. SSH

SSH stands for Secure Shell.

SSH provides secure remote access to computers and network devices. Administrators use SSH to manage Linux servers, routers, switches, and other systems.

SSH uses:

TCP 22

SSH encrypts the session, including authentication credentials and commands.

Example:

An administrator connects to a Linux server remotely using:

ssh user@server

The connection uses TCP port 22.

4. Telnet

Telnet provides remote command-line access to a device.

Telnet uses:

TCP 23

Telnet does not encrypt communication. Usernames, passwords, and commands travel in plaintext.

For this reason, SSH is preferred for secure remote administration.

Remember:

SSH = secure remote administration = TCP 22
Telnet = insecure remote administration = TCP 23

5. SMTP

SMTP stands for Simple Mail Transfer Protocol.

SMTP is used to send email between mail clients and mail servers, and between mail servers.

Common SMTP ports include:

TCP 25: Server-to-server SMTP
TCP 587: Message submission
TCP 465: SMTP over implicit TLS

Port 25 is commonly used for mail server communication. Port 587 is commonly used when an email client submits outgoing mail to a mail server.

Example:

When an application sends an email through an SMTP service, the application connects to the SMTP server using the configured SMTP port.

6. DNS

DNS stands for Domain Name System.

DNS translates domain names into IP addresses.

For example:

www.example.com → 93.184.216.34

DNS normally uses:

UDP 53: Standard DNS queries
TCP 53: DNS transfers and situations requiring TCP

UDP is normally preferred because DNS queries are small and fast.

DNS is essential because users remember domain names more easily than IP addresses.

7. DHCP

DHCP stands for Dynamic Host Configuration Protocol.

DHCP automatically provides network configuration to devices.

A DHCP server typically provides:

IP address
Subnet mask
Default gateway
DNS server address
Lease information

DHCP uses:

UDP 67: DHCP server
UDP 68: DHCP client

A common DHCP process is known as DORA:

Discover
Offer
Request
Acknowledge

A new device broadcasts a DHCP Discover message. A DHCP server responds with an Offer. The client sends a Request, and the server sends an Acknowledgement.

Remember:

DHCP server = UDP 67
DHCP client = UDP 68

8. TFTP

TFTP stands for Trivial File Transfer Protocol.

TFTP provides simple file transfers without the features and security of FTP.

TFTP uses:

UDP 69

TFTP does not provide authentication or encryption.

Network administrators sometimes use TFTP for tasks such as transferring configuration files or firmware in controlled network environments.

Remember:

TFTP = UDP 69

9. HTTP

HTTP stands for Hypertext Transfer Protocol.

HTTP is used to transfer web content between clients and web servers.

HTTP uses:

TCP 80

When you access an HTTP website, your browser communicates with the web server using TCP port 80.

HTTP does not encrypt the traffic.

10. HTTPS

HTTPS stands for Hypertext Transfer Protocol Secure.

HTTPS provides secure web communication by using TLS encryption.

HTTPS uses:

TCP 443

HTTPS protects data exchanged between the browser and web server.

Examples include:

Online banking
Online shopping
Login pages
Payment systems
Web applications

Remember:

HTTP = TCP 80
HTTPS = TCP 443

11. NTP

NTP stands for Network Time Protocol.

NTP synchronises clocks between computers and network devices.

NTP uses:

UDP 123

Accurate time is important for:

Log analysis
Authentication
Security monitoring
Event correlation
Certificates
Network troubleshooting

For example, if servers have incorrect times, security logs from different systems become harder to compare.

Remember:

NTP = UDP 123

12. SNMP

SNMP stands for Simple Network Management Protocol.

SNMP allows administrators to monitor and manage network devices.

SNMP is commonly used to monitor:

Routers
Switches
Servers
Printers
Firewalls
Network interfaces

Common SNMP ports are:

UDP 161: Queries and management
UDP 162: Traps and notifications

An SNMP manager might query a router to check CPU usage, memory usage, interface status, or network traffic.

Remember:

SNMP = UDP 161
SNMP traps = UDP 162

13. LDAP

LDAP stands for Lightweight Directory Access Protocol.

LDAP provides access to directory services.

Organisations use directory services to manage information such as:

Users
Groups
Computers
Authentication information
Organisational structures

LDAP uses:

TCP/UDP 389

LDAPS provides LDAP communication over TLS and commonly uses:

TCP 636

Remember:

LDAP = 389
LDAPS = 636

14. SMB

SMB stands for Server Message Block.

SMB allows systems to share files, folders, printers, and other network resources.

SMB commonly uses:

TCP 445

SMB is widely used in Windows environments.

Example:

A company might have a shared folder on a file server. Employees access the folder through SMB.

Remember:

SMB = TCP 445

15. Syslog

Syslog provides a standard method for sending and storing system log messages.

Network devices and servers can send logs to a central logging server.

Syslog commonly uses:

UDP 514

Secure implementations also exist using other transport methods and ports.

Centralised logging helps administrators investigate:

Failed login attempts
Network errors
Firewall events
Service failures
Security incidents

Remember:

Syslog = UDP 514

16. SQL

SQL stands for Structured Query Language.

SQL is used to interact with relational databases.

SQL itself is a language rather than a single network protocol, so the port depends on the database system.

Common database ports include:

MySQL = TCP 3306
Microsoft SQL Server = TCP 1433
PostgreSQL = TCP 5432
Oracle Database = TCP 1521

For Network+ questions, pay attention to the database product named in the question.

17. RDP

RDP stands for Remote Desktop Protocol.

RDP allows users to remotely access graphical desktops, especially Windows systems.

RDP commonly uses:

TCP 3389
UDP 3389

RDP is useful for remote administration and accessing Windows desktops.

Because exposed RDP services are frequently targeted by attackers, administrators should protect RDP with strong authentication, network restrictions, VPNs, and appropriate security controls.

Remember:

RDP = TCP/UDP 3389

18. SIP

SIP stands for Session Initiation Protocol.

SIP is used to establish, modify, and terminate communication sessions.

SIP is commonly associated with:

VoIP
Video calls
Internet-based communication

Common SIP ports include:

UDP 5060
TCP 5060
TCP 5061 for SIP over TLS

SIP handles signalling. The actual voice or video media normally uses other protocols, such as RTP.

Remember:

SIP = 5060
Secure SIP = 5061

19. IP Protocol Types

IP operates at the network layer and provides addressing and routing between networks.

Two major versions are:

IPv4

IPv4 uses 32-bit addresses.

Example:

192.168.1.10

IPv6

IPv6 uses 128-bit addresses.

Example:

2001:db8::1

IPv6 provides a much larger address space than IPv4.

Important IPv4 concepts include:

Unicast: One sender to one receiver
Broadcast: One sender to all devices on the local broadcast domain
Multicast: One sender to multiple subscribed receivers

IPv6 does not use traditional broadcast. IPv6 uses multicast and anycast mechanisms instead.

20. Traffic Types

Network traffic describes how data moves between devices.

Unicast

One device communicates with another device.

Example:

Your computer sends a request to a web server.

One sender → One receiver

Broadcast

One device sends traffic to all devices within the relevant broadcast domain.

Example:

DHCP Discover traffic uses broadcast during the initial DHCP process when the client does not yet have an IP address.

One sender → All relevant devices

Multicast

One sender sends traffic to multiple subscribed devices.

Multicast is useful when the same information needs to reach a selected group of receivers.

One sender → Multiple subscribed receivers

Anycast

Anycast uses an address shared by multiple possible destinations. Network routing directs traffic toward a suitable destination, often the nearest or best available one.

Anycast is widely used in distributed services such as DNS.

21. Essential CompTIA Network+ Port Table

Protocol	Port	Transport	Purpose
FTP	20/21	TCP	File transfer
SFTP	22	TCP	Secure file transfer
SSH	22	TCP	Secure remote access
Telnet	23	TCP	Remote access
SMTP	25	TCP	Email transfer
DNS	53	UDP/TCP	Name resolution
DHCP Server	67	UDP	IP configuration
DHCP Client	68	UDP	IP configuration
TFTP	69	UDP	Simple file transfer
HTTP	80	TCP	Web traffic
HTTPS	443	TCP	Secure web traffic
NTP	123	UDP	Time synchronisation
SNMP	161	UDP	Network management
SNMP Trap	162	UDP	Network notifications
LDAP	389	TCP/UDP	Directory services
SMB	445	TCP	File and printer sharing
Syslog	514	UDP	Log messages
LDAPS	636	TCP	Secure directory services
RDP	3389	TCP/UDP	Remote desktop
MySQL	3306	TCP	Database
PostgreSQL	5432	TCP	Database
SIP	5060	TCP/UDP	VoIP signalling
SIP over TLS	5061	TCP	Secure VoIP signalling

22. Ports You Should Memorise First

For the CompTIA Network+ exam, start with these:

22 = SSH/SFTP

23 = Telnet

25 = SMTP

53 = DNS

67/68 = DHCP

69 = TFTP

80 = HTTP

123 = NTP

161/162 = SNMP

389 = LDAP

443 = HTTPS

445 = SMB

514 = Syslog

636 = LDAPS

3389 = RDP

3306 = MySQL

5432 = PostgreSQL

5060/5061 = SIP

23. TCP vs UDP

Knowing the port number is only part of the question. You should also recognise whether the service normally uses TCP or UDP.

TCP provides:

Connection establishment
Reliable delivery
Sequencing
Error detection
Retransmission
Flow control

UDP provides:

Connectionless communication
Lower overhead
Faster transmission
No guaranteed delivery
No built-in sequencing or retransmission

Examples of TCP-based services include:

SSH
FTP
HTTP
HTTPS
SMB
RDP

Examples of UDP-based services include:

DHCP
DNS queries
NTP
SNMP
TFTP
Syslog

Some services support both TCP and UDP depending on the implementation or function.

24. How to Approach Network+ Exam Questions

When you see a port question, identify three things:

What service is being described?
What port does the service use?
Does the service use TCP, UDP, or both?

For example:

A question says:

“An administrator needs secure remote command-line access to a Linux server. Which protocol and port should be used?”

Think:

Secure remote command-line access = SSH

SSH = TCP 22

Answer: SSH over TCP port 22.

Another example:

“A workstation needs to automatically obtain an IP address from a DHCP server.”

Think:

Automatic IP configuration = DHCP

DHCP server = UDP 67

DHCP client = UDP 68

25. Quick Memory Guide

Use these associations:

22 = Secure Shell

23 = Telnet

25 = Email

53 = DNS

67/68 = DHCP

69 = TFTP

80 = Web

123 = Time

161/162 = Network management

389 = Directory services

443 = Secure web

445 = Windows file sharing

514 = Logs

636 = Secure LDAP

3306 = MySQL

3389 = Remote desktop

5432 = PostgreSQL

5060/5061 = VoIP signalling

Final Revision Summary

Ports identify network services. Protocols define how those services communicate.

The most important Network+ knowledge is the relationship between the service, port, transport protocol, and purpose.

Focus heavily on:

SSH, TCP 22
Telnet, TCP 23
SMTP, TCP 25
DNS, UDP/TCP 53
DHCP, UDP 67/68
TFTP, UDP 69
HTTP, TCP 80
HTTPS, TCP 443
NTP, UDP 123
SNMP, UDP 161/162
LDAP, TCP/UDP 389
SMB, TCP 445
Syslog, UDP 514
LDAPS, TCP 636
RDP, TCP/UDP 3389
MySQL, TCP 3306
PostgreSQL, TCP 5432
SIP, 5060/5061

If you know what each protocol does, its default port, and whether it uses TCP or UDP, you will have a strong foundation for the Ports & Protocols section of CompTIA Network+.

CompTIA Network+: Cloud Computing Concepts

Falade Timilehin — Sat, 15 Aug 2026 15:32:24 +0000

Cloud computing is a fundamental pillar of modern network architecture, shifting infrastructure management from physical data centers to flexible, virtualized environments. This guide breaks down core cloud concepts, architecture models, service types, and operational characteristics aligned with CompTIA Network+ objectives.

Virtualization and Network FoundationsNetwork Functions Virtualization (NFV)NFV replaces dedicated, proprietary hardware appliances (such as firewalls, load balancers, and routers) with virtual appliances running on standard servers. This decouples network functions from physical hardware, allowing for rapid deployment, easier scaling, and reduced capital expenditure.Virtual Private Cloud (VPC)A Virtual Private Cloud (VPC) provides an isolated, private cloud environment dedicated to a single customer within a shared public cloud infrastructure.Resource Separation: Uses subnets, VLANs, and tunneling to isolate compute, storage, and networking resources.Control: Customers have full administrative control over their network configuration, IP address ranges, and routing tables.Security: Regulated via Network Security Groups (NSGs) and Access Control Lists (ACLs) to govern traffic entering and leaving subnets.Cloud Gateways & Connection MethodsCloud gateways serve as translation points or secure entryways between on-premises networks and cloud environments. Organizations connect to cloud resources using several methods:Site-to-Site VPNs: Encrypted tunnels over the public internet connecting an on-premises office or data center to a VPC.Dedicated Interconnects (e.g., AWS Direct Connect, Azure ExpressRoute): High-speed, private, dedicated circuits that bypass the public internet for enhanced security, lower latency, and predictable performance.
Cloud Deployment ModelsCloud architecture defines where infrastructure is hosted and who manages the underlying hardware.ModelCharacteristicsBest Suited ForPublic CloudOwned and operated by a third-party provider (e.g., AWS, Azure, GCP); resources are shared across multiple tenants.High scalability, cost efficiency, and general web applications.Private CloudDedicated exclusively to a single organization, hosted on-premise or managed externally.Highly regulated industries requiring strict data sovereignty and custom security controls.Hybrid CloudCombines public and private clouds, allowing data and apps to be shared between them via secure connections.Workloads with fluctuating demands or sensitive data that must remain on-premises paired with scalable compute.
Cloud Service Models (XaaS)Cloud computing offers tiered service models that divide responsibility between the cloud provider and the customer.Infrastructure as a Service (IaaS)What it is: Provides fundamental computing resources over the internet—virtual machines, storage, and networking.Customer Responsibility: The customer configures and manages the operating system, middleware, data, and applications.Use Cases: Lift-and-shift migrations, development and testing environments, and high-performance computing.Platform as a Service (PaaS)What it is: Delivers a framework and managed platform for developers to build, test, and deploy applications without worrying about underlying infrastructure management.Customer Responsibility: Application code and data management; the provider manages servers, storage, and networking.Software as a Service (SaaS)What it is: Delivers fully functioning, ready-to-use software applications over the internet on a subscription basis.Customer Responsibility: User access management and data configuration; the provider handles all maintenance, patching, and infrastructure.Examples: Email services, CRMs, and streaming platforms.
Operational Characteristics: Elasticity vs. ScalabilityWhile often used interchangeably, elasticity and scalability represent two distinct ways cloud environments handle workload demands.Cloud Elasticity: The ability of a system to automatically expand or shrink resource allocation (CPU, RAM, storage) dynamically based on real-time demand. This prevents both over-provisioning and under-provisioning.Scalability: The ability to handle growing workloads by adding resources (scaling up/vertical by adding power to a single node, or scaling out/horizontal by adding more nodes). Scaling can be manual, automated, or provider-requested.
MultitenancyMultitenancy means multiple distinct customers (tenants) share the same underlying physical hardware, hypervisor, or application instance.Isolation: Strict logical separation ensures that tenant data and configurations remain completely private and secure from other users.Benefits: Lower costs, efficient resource utilization, and streamlined provider maintenance.Considerations: Potential risks include noisy neighbor performance bottlenecks and shared-risk security vulnerabilities if isolation controls misconfigure.

CompTIA Network+: Networking Appliances, Applications, and Functions

Falade Timilehin — Wed, 29 Jul 2026 09:59:00 +0000

Introduction

Computer networks rely on different devices and services to connect users, manage traffic, protect data, and deliver applications. Understanding these technologies is important for the CompTIA Network+ certification and for working in real-world IT environments.

This article explains the main networking appliances, applications, and functions covered in this section:

• Ethernet network switches
• Ethernet network routers
• Proxies and load balancers
• Firewall appliances
• Intrusion Detection Systems
• Network-Attached Storage and Storage Area Networks
• Wireless Access Points and Controllers
• Content Delivery Networks
• Common networking functions

Ethernet Network Switches

An Ethernet switch connects devices within a local area network, known as a LAN.

Examples of devices connected to a switch include:

• Desktop computers
• Laptops
• Servers
• Printers
• IP phones
• Wireless access points
• Network cameras

A switch uses MAC addresses to identify devices on the network. When a frame arrives, the switch examines the destination MAC address and forwards the frame through the appropriate port.

Switches operate mainly at Layer 2 of the OSI model, the Data Link Layer. Some advanced switches, known as Layer 3 switches, also perform routing functions.

Important switch concepts include:

MAC Address Table

A switch learns which MAC address is connected to each physical port. It stores this information in a MAC address table.

For example:

Port 1 → PC A
Port 2 → PC B
Port 3 → Printer

When PC A sends data to PC B, the switch checks its MAC address table and forwards the traffic directly to the correct port.

VLANs

A Virtual LAN, or VLAN, divides a physical switch into separate logical networks.

For example:

VLAN 10 → Employees
VLAN 20 → Guests
VLAN 30 → Servers

VLANs improve network organisation and security by separating traffic.

PoE

Power over Ethernet, or PoE, allows a network cable to carry both data and electrical power.

PoE often powers:

• Wireless access points
• IP phones
• Security cameras

This reduces the need for separate power cables.

Ethernet Network Routers

A router connects different networks together.

For example, a router might connect:

Home LAN → Internet

Or:

Office Network → Branch Office Network

Routers use IP addresses to determine where network traffic should go. They operate primarily at Layer 3, the Network Layer, of the OSI model.

Routing Table

A routing table contains information about available networks and the paths used to reach them.

A router examines the destination IP address of a packet and selects the best available route.

Default Gateway

A default gateway allows devices on a local network to communicate with networks outside their own subnet.

For example, a computer might have:

IP address: 192.168.1.20
Default gateway: 192.168.1.1

When the computer wants to access the internet, it sends traffic to the default gateway.

NAT

Network Address Translation, or NAT, allows private IP addresses to communicate with public networks.

For example, multiple devices inside a home might use private IP addresses while sharing one public IP address when accessing the internet.

Proxies and Load Balancers

Proxy Servers

A proxy server acts as an intermediary between a client and another system.

Instead of:

Client → Internet Server

The connection becomes:

Client → Proxy → Internet Server

A proxy can provide:

• Web filtering
• Access control
• Caching
• Privacy
• Security
• Monitoring

Forward Proxy

A forward proxy represents the client.

It is often used by organisations to control and monitor internet access.

Reverse Proxy

A reverse proxy represents the server.

It receives requests from users and forwards them to backend servers.

A reverse proxy can improve:

• Security
• Performance
• Scalability
• Availability

Load Balancers

A load balancer distributes network traffic across multiple servers.

For example:

User 1 → Server A
User 2 → Server B
User 3 → Server C

This prevents one server from handling all the traffic.

Load balancing improves:

• Performance
• Availability
• Scalability
• Fault tolerance

Common load-balancing methods include:

Round Robin

Requests are distributed between servers in sequence.

Least Connections

New requests go to the server with the fewest active connections.

Health Checks

The load balancer checks whether servers are working correctly. If a server fails, the load balancer stops sending traffic to it.

Firewall Appliances

A firewall controls network traffic based on predefined security rules.

A firewall can allow or block traffic based on factors such as:

• Source IP address
• Destination IP address
• Port number
• Protocol
• Application
• User identity

For example, a firewall might allow HTTPS traffic on TCP port 443 while blocking unwanted connections.

Types of Firewalls

Network Firewall

Protects an entire network by controlling traffic entering and leaving the network.

Host-Based Firewall

Runs directly on an individual computer or server.

Next-Generation Firewall

A Next-Generation Firewall, or NGFW, provides advanced security features such as:

• Application awareness
• Deep packet inspection
• Intrusion prevention
• User-based policies

Firewalls are an important part of network security, but they should work alongside other security controls.

Intrusion Detection Systems

An Intrusion Detection System, or IDS, monitors network or system activity and looks for suspicious behaviour.

When an IDS detects potential malicious activity, it generates an alert.

Network IDS

A Network Intrusion Detection System, or NIDS, monitors network traffic.

Host IDS

A Host Intrusion Detection System, or HIDS, monitors activity on an individual computer or server.

IDS vs IPS

IDS:

Detects suspicious activity.
Generates alerts.
Does not normally block the attack automatically.

IPS:

Detects suspicious activity.
Can actively block or prevent the attack.

A simple way to remember this is:

IDS = Detect and alert

IPS = Detect and prevent

Network-Attached Storage

Network-Attached Storage, or NAS, provides file storage over a network.

Users access files stored on a NAS device through the network.

NAS is commonly used for:

• File sharing
• Backups
• Document storage
• Media storage

For example:

Computer A
Computer B
Computer C
↓
NAS

All three computers can access shared files stored on the NAS.

NAS generally operates at the file level. Users interact with files and folders rather than directly managing individual storage blocks.

Storage Area Networks

A Storage Area Network, or SAN, provides high-speed access to storage resources.

SAN technology is commonly used in enterprise environments and data centres.

Unlike NAS, which typically provides file-level access, SANs provide block-level storage access.

A simplified comparison is:

NAS → File-level storage

SAN → Block-level storage

SANs are useful for:

• Databases
• Virtual machines
• Enterprise applications
• High-performance storage

SAN technologies include Fibre Channel and iSCSI.

Wireless Access Points

A Wireless Access Point, or WAP, allows wireless devices to connect to a wired network.

For example:

Laptop
↓ Wi-Fi
Wireless Access Point
↓ Ethernet
Network Switch
↓
Network

Wireless access points use Wi-Fi standards to provide wireless connectivity.

Important wireless concepts include:

SSID

The Service Set Identifier, or SSID, is the name users see when selecting a wireless network.

WPA2 and WPA3

These are wireless security standards used to protect Wi-Fi networks.

WPA3 provides stronger security than older wireless security protocols.

Channels

Wireless networks use radio channels to communicate. Proper channel planning helps reduce interference.

Wireless Controllers

A Wireless LAN Controller, or WLC, manages multiple wireless access points from a central location.

A controller can help administrators:

• Configure access points
• Manage wireless security
• Monitor wireless networks
• Apply policies
• Manage roaming

Centralised management is useful in large organisations with many access points.

Content Delivery Networks

A Content Delivery Network, or CDN, is a distributed network of servers designed to deliver content to users efficiently.

Instead of every user accessing a central server, a CDN stores cached copies of content on servers located in different geographic locations.

For example:

User in London → CDN server in London

User in New York → CDN server in New York

User in Tokyo → CDN server in Tokyo

The CDN selects an appropriate server based on factors such as geographic location and network performance.

CDNs are commonly used for:

• Websites
• Images
• Videos
• Software downloads
• JavaScript and CSS files

Benefits include:

• Faster content delivery
• Reduced latency
• Reduced load on the origin server
• Better scalability
• Improved availability

Common Networking Functions

Several networking functions appear frequently in enterprise networks.

DHCP

Dynamic Host Configuration Protocol, or DHCP, automatically provides network configuration to devices.

DHCP can provide:

• IP address
• Subnet mask
• Default gateway
• DNS server

Without DHCP, administrators might need to configure every device manually.

DNS

Domain Name System, or DNS, translates domain names into IP addresses.

For example:

www.example.com → IP address

DNS allows users to access services using memorable names instead of IP addresses.

NTP

Network Time Protocol, or NTP, synchronises the clocks of network devices.

Accurate time is important for:

• Security logs
• Authentication
• Troubleshooting
• Event correlation

SNMP

Simple Network Management Protocol, or SNMP, allows network administrators to monitor and manage network devices.

SNMP can monitor:

• Routers
• Switches
• Servers
• Printers
• Firewalls

Administrators can use SNMP to monitor device health and performance.

VPN

A Virtual Private Network, or VPN, creates a secure connection over an untrusted network such as the internet.

VPNs are commonly used for:

• Remote employee access
• Connecting branch offices
• Protecting data in transit

A VPN can encrypt network traffic between the connected endpoints.

Syslog

Syslog provides a standard method for collecting and managing system and network logs.

Organisations often send logs from multiple devices to a central logging server.

This helps with:

• Troubleshooting
• Security monitoring
• Incident investigation
• Compliance

Key Comparison Table

Device or Function | Main Purpose | Key Concept

Switch | Connects devices on a LAN | MAC addresses

Router | Connects different networks | IP addresses

Proxy | Acts as an intermediary | Client or server requests

Load Balancer | Distributes traffic | Multiple servers

Firewall | Controls network traffic | Security rules

IDS | Detects suspicious activity | Alerts

IPS | Detects and blocks threats | Prevention

NAS | Provides file storage | File-level access

SAN | Provides high-performance storage | Block-level access

Wireless Access Point | Provides Wi-Fi connectivity | Wireless LAN

Wireless Controller | Manages multiple access points | Centralised management

CDN | Delivers content efficiently | Distributed servers

DHCP | Assigns network settings | Automatic configuration

DNS | Resolves names to IP addresses | Name resolution

NTP | Synchronises time | Accurate clocks

SNMP | Monitors network devices | Network management

VPN | Creates secure network connections | Encrypted tunnels

Syslog | Collects system logs | Centralised logging

CompTIA Network+ Exam Tips

For the Network+ exam, focus on understanding the purpose of each technology rather than memorising definitions alone.

Remember these key points:

Switch = Connects devices within a network.

Router = Connects different networks.

Proxy = Acts as an intermediary.

Load balancer = Distributes traffic across servers.

Firewall = Allows or blocks traffic based on rules.

IDS = Detects and alerts.

IPS = Detects and blocks.

NAS = File-level storage.

SAN = Block-level storage.

Access Point = Provides wireless network access.

Wireless Controller = Centrally manages wireless access points.

CDN = Delivers content from distributed locations.

DHCP = Automatically assigns network configuration.

DNS = Converts names into IP addresses.

NTP = Synchronises time.

SNMP = Monitors and manages network devices.

VPN = Creates a secure connection across an untrusted network.

Syslog = Collects and stores logs.

The main goal of this section is to understand how these technologies work together. A typical enterprise network might use switches to connect devices, routers to connect networks, firewalls to control traffic, wireless access points to provide Wi-Fi, DHCP and DNS to support network services, load balancers to distribute application traffic, and a CDN to deliver content efficiently to users.

Outwitting Your Mind: How to Recognize and Overcome the Three Types of Cognitive Bias

Falade Timilehin — Mon, 27 Jul 2026 17:42:46 +0000

Every day, our brains process an overwhelming amount of information. To make sense of it all and arrive at quick conclusions, our minds rely on mental shortcuts called heuristics. While these shortcuts help us navigate daily life efficiently, they often morph into cognitive biases—systematic errors in thinking that distort our judgment, skew our forecasts, and derail our decision-making.

To effectively combat these mental traps, it helps to break them down into three core categories: prediction bias, decision bias, and action bias.

Prediction Bias: The Danger of False Certainty Prediction bias occurs when we try to forecast future outcomes. By focusing too narrowly on a limited set of expected scenarios, we fall into the trap of overconfidence and inaccurate forecasting.

The Mechanism: When looking ahead, our brains naturally latch onto the most convenient or desirable narrative, ignoring variables that fall outside our narrow view. This creates a false sense of certainty.

The Antidote: Actively challenge your forecasts. Use structured techniques like "pre-mortem" analyses—imagining a project has already failed and working backward to identify all the reasons why. Actively seek out disconfirming evidence and diverse perspectives to widen your predictive lens.

Decision Bias: Narrowing the Horizon While prediction bias affects how we view the future, decision bias shapes the choices we make in the present. This bias limits the scope of options we consider, directly contradicting rational decision-making.

The Mechanism: When faced with complex choices, we often default to familiar pathways or satisfice (choosing the first option that seems "good enough" rather than evaluating the best alternative). This premature narrowing blinds us to superior solutions.

The Antidote: Force yourself to expand your choice set. Adopt a rule of generating at least three distinct alternatives before making a significant decision. Involve independent voices who can point out options you may have unconsciously filtered out.

Action Bias: The Illusion of Control When uncertainty strikes, humans have a deep-seated urge to "do something." Action bias drives us to take rash actions simply to feel in control, deeply undervaluing the power of thoughtful inaction.

The Mechanism: Sitting still or waiting feels uncomfortable during a crisis. As a result, we favor activity over accuracy—taking impulsive steps that often create more problems than they solve.

The Antidote: Cultivate pause as a strategic tool. Establish clear thresholds that must be met before taking action, and ask yourself: "Am I taking this step because it is genuinely effective, or merely to alleviate the discomfort of waiting?"

The Feedback Loop: Breaking the Cycle of Past Errors
The danger of these biases doesn't end when a decision is made. A biased evaluation of past actions continuously reinforces future errors. When we selectively remember successes or rationalize away failures, we prime our brains to repeat the exact same mistakes.

Key Takeaways for Sharper Thinking
Acknowledge the shortcuts: Recognize that cognitive bias is a natural byproduct of how the brain processes information, not a personal flaw.

Broaden your inputs: Fight prediction and decision bias by forcing yourself to consider wider variables and alternative options.

Value thoughtful inaction: Resist action bias by embracing strategic pauses when uncertainty peaks.

Audit your history: Objectively review past outcomes without ego, ensuring that yesterday's missteps become tomorrow's lessons rather than repeated habits.

Cracking CompTIA Linux+

Falade Timilehin — Thu, 23 Jul 2026 17:39:11 +0000

Your Survival Guide to Software Management
We’ve all been there—staring at a blinking terminal cursor, wondering how on earth to install a simple package without breaking the entire system. If you are studying for the CompTIA Linux+ (XK0-005) exam, software management is one of those foundational topics you just have to master.

Think of this as pulling right out of my personal study notebook. Let's break down how Linux handles software, repositories, and updates across different distributions without the dry textbook jargon.

The Big Picture: How Linux Thinks About Software
Unlike operating systems where you download an .exe or drag an app to a folder, Linux relies heavily on repositories—centralized servers or local directories holding secure, pre-compiled software packages.

The Core Loop: Software management is all about configuring these repositories, fetching updates, and installing what you need safely.

The Tools of the Trade: Different Linux families use different package managers. You'll need to get comfortable with yum (Red Hat/CentOS/Fedora), pacman (Arch Linux), and apt (Debian/Ubuntu).

Going Old School: Package managers simplify life, but they aren't always sufficient. Sometimes you have to roll up your sleeves and build software directly from source code.

Red Hat Territory: Managing Packages with yum
If you are working in an enterprise Red Hat environment, yum (Yellowdog Updater, Modified) is your best friend for managing RPM (.rpm) packages.

Check Your Sources: Always know where your packages are coming from. Run sudo yum repolist to see which repositories are currently active and enabled.

Inspect What You Have: Wondering if a tool is already installed? Use sudo yum list installed combined with grep to filter for specifics (e.g., sudo yum list installed | grep docker).

Keeping Things Fresh:

Check for available updates: sudo yum check-update

Apply all system upgrades: sudo yum update

Install and Remove:

Install a package: sudo yum install

Clean up what you don't need: sudo yum remove

Managing Services & Alternatives: Once a service is installed, you can control it using sudo service status/start/stop. Keep in mind that low-level rpm commands (rpm -i for install, rpm -e for erase) act as powerful alternatives, though they don't automatically resolve dependencies like yum does.

Debian & Ubuntu Territory: Keeping it Clean with apt
If you are spinning up Ubuntu or Debian-based systems, apt is your go-to package management tool.

The Basics: Repositories act as your software sources, whether they are remote servers or local directories.

Refresh and Upgrade:

Update your package indexes: sudo apt update

Upgrade your installed packages: sudo apt upgrade

Install and Remove:

Get new software: sudo apt install

Purge what you don't want: sudo apt remove

Expanding Repositories: Need a third-party tool? Add new repositories using sudo add-apt-repository and make sure to import public keys to verify package signatures and keep your system secure.

Arch Linux Territory: Taking Charge with pacman
Arch Linux approaches software management a bit differently through pacman, a fast and lightweight package utility.

Where the Mirrors Live: Repository URLs are stored in /etc/pacman.d/mirrorlist. They can point to https, http, or rsync links.

Custom Repos & Security: You can add custom repositories, but tread carefully—security risks are real. You may also need to manually import public keys to trust digital signatures before Arch lets you install packages from unfamiliar sources.

The Pacman Cheat Sheet: Memorize these flags for the exam (and real life):

Update everything: sudo pacman -Syu (syncs repositories and upgrades the system)

Search for a package: sudo pacman -Ss

Query installed packages: sudo pacman -Q

Install a package: sudo pacman -S

Remove a package: sudo pacman -R

Post-Install Check: For instance, if you just installed Docker via pacman, remember to use systemctl to kickstart the daemon and verify its health (sudo systemctl start docker and sudo systemctl status docker).

Going Off-Grid: Building Software from Source
As a Linux technician, you won't always find what you need in a pre-built repository. Sometimes, you have to build software straight from source code.

The Source Workflow: This involves downloading the source code, installing required dependencies and compilers, configuring the build environment, compiling the code, and finally installing it onto the system.

The Magic of configure: Before you compile, running configuration scripts (like ./configure) is crucial. It checks your system for required compilers and dependencies, letting you know if anything is missing before you run into a disastrous build error.

Pro-Tip for the Exam: Always follow the developer's installation instructions carefully. Handling missing libraries, installing compilers (gcc, make), and troubleshooting build errors are classic Linux+ scenarios.

Wrapping Up
Mastering Linux+ isn't about memorizing every single command blindly; it's about understanding why each distribution uses its specific toolset and knowing how to adapt when a package manager just isn't enough. Practice these commands in your lab until they feel like second nature. Good luck with your XK0-005 prep!

🚀 How to Start a Node.js Project (Beginner’s Guide)

Falade Timilehin — Thu, 23 Jul 2026 17:38:40 +0000

If you’re new to Node.js, starting your first project can feel confusing folders, files, npm, scripts… 😅
Don’t worry. In this guide, I’ll walk you through everything step by step, with zero assumptions. By the end of this article, you’ll have:
A working Node.js project

A basic understanding of how things fit together

A solid foundation to build APIs or backend apps

Let’s get started 👇

🔍 What is Node.js?

Node.js is a JavaScript runtime that allows you to run JavaScript outside the browser.
It’s commonly used for:

Backend APIs

Web servers

Real-time apps (chat, streaming)

Microservices

The Importance of Responsive Web Design: Why It’s a Must-Have for Every Website in 2024

Falade Timilehin — Mon, 21 Oct 2024 21:28:00 +0000

As more people access the internet through various devices, from smartphones to desktops, responsive web design has become crucial for businesses and developers alike. In 2024, with an increased focus on user experience (UX) and accessibility, every website must be responsive to succeed. Let’s explore why responsive design matters and how to implement it effectively.

1. Enhances User Experience
A responsive design adapts to different screen sizes, providing users with an optimal browsing experience no matter the device. When a website looks good and is easy to navigate on any device, it keeps users engaged longer, reduces bounce rates, and increases the likelihood of conversions.

2. Improves SEO Ranking
Google has prioritized mobile-first indexing, meaning responsive websites rank higher in search results. Without a responsive design, a website risks lower rankings, reducing visibility and organic traffic.

3. Cost-Effective
Building one responsive site is often more cost-effective than maintaining separate desktop and mobile versions. It also reduces maintenance costs, as you only need to update one site instead of multiple versions.

4. Future-Proofing
The tech landscape changes constantly, with new devices coming into play. A responsive design automatically adapts, making your website ready for whatever the future holds.

By investing in responsive design, companies can ensure a seamless, user-friendly experience, leading to better engagement, increased conversions, and stronger customer loyalty.

From Backend to Frontend – Key Skills That Make a Developer Versatile

Falade Timilehin — Sat, 19 Oct 2024 22:26:00 +0000

Introduction
Developers who can work across both backend and frontend domains bring unique value to projects. Here’s how my backend knowledge has helped me excel in frontend development and vice versa.

1. Understanding API Structures and Data Flow
Knowing how APIs are structured enables me to consume them more effectively on the frontend. My experience with database architecture also helps me design efficient data structures, making data handling smoother.

2. Proficiency in JavaScript Across the Stack
JavaScript is now the universal language for both frontend and backend (Node.js). This proficiency allows me to write code that’s consistent and optimized across the full stack.

3. Scalability and Performance Awareness
With a backend perspective, I’m more aware of the scalability challenges on the frontend, especially when dealing with high-volume data. For instance, pagination and lazy loading are techniques I often use to manage data efficiently.

4. Enhanced Debugging Skills
A solid understanding of both ends of an application makes it easier to identify and fix bugs. Being able to trace issues across the stack means faster resolutions and more reliable applications.

Conclusion

Having a full-stack skill set allows for a holistic approach to development, bridging the gap between frontend and backend and leading to more robust, cohesive applications.