C1M1: What Is the Cloud?

Recommended length: 450–550 words Maximum: 700 words

Instructional Context

Prior Knowledge: Learners have been introduced to information technology and the basic components of technology systems, including hardware, software, networks, services, and infrastructure.

Reading Objective: Compare local and cloud-based technology systems and explain why organizations use cloud computing.

Future Learning: Learners will explore hardware, software, networking, cloud services, and how technology systems interact in greater detail. This reading should establish a foundational understanding without introducing advanced cloud concepts.

Content Outline

1. What is the cloud?

• Define cloud computing as accessing computing resources and services hosted in remote data centers.
• Explain that cloud infrastructure consists of physical servers, storage, software, and networking equipment.
• Provide one familiar example, such as storing files in Google Drive.

2. On-premises vs. cloud infrastructure

• On-premises: Organizations maintain physical technology resources within their own facilities and are responsible for maintaining that infrastructure.
• Cloud-based: Organizations obtain computing resources and services from cloud providers, such as Google Cloud, AWS, or Microsoft Azure.
• Explain that cloud resources are accessed and managed remotely through network connections and software.
• Retain the existing comparison graphic to reinforce the differences.

3. Why organizations choose cloud or on-premises infrastructure

• Cost flexibility: Cloud services can reduce upfront hardware purchases, although ongoing costs depend on usage.
• Scalability: Organizations can increase or decrease computing resources as their needs change.
• Availability and accessibility: Cloud providers can offer redundancy and remote access capabilities, depending on service configuration.
• On-premises considerations: Some organizations retain local infrastructure for greater physical control or specific operational requirements.
• Briefly acknowledge that organizations may use both approaches.

4. Connecting cloud computing to IT support

• Explain that IT professionals support both local and cloud-based systems.
• Reinforce that support responsibilities may include helping users access services, identifying connectivity problems, and working with system configurations.
• Conclude that cloud computing changes where resources are hosted and how they are managed, but the underlying technology components remain familiar.

Out of Scope Guardrails

• Cloud service models: Do not introduce detailed IaaS, PaaS, or SaaS classifications.
• Advanced infrastructure: Exclude virtualization, cloud architecture, hybrid cloud configurations, and software-defined networking.
• Cloud administration: Do not demonstrate provider consoles, resource provisioning, or configuration procedures.
• Advanced financial concepts: Avoid detailed pricing models, cost calculations, and cloud cost optimization.
• Detailed troubleshooting: Do not introduce cloud diagnostic tools or technical troubleshooting procedures.

C1M1 Reading: AI Capabilities and Durable Human Skills

Target Length: Maintain approximately the same length as the source reading.

Prior Knowledge: Learners have been introduced to technology systems and cloud computing. No prior knowledge of AI tools, prompting, or IT support procedures is required.

Reading Objective: Compare the capabilities of AI with durable human skills and explain how they complement one another in technology-related work.

Content Outline

1. Introduction

• Retain the existing introduction contrasting AI capabilities with human skills.
• Replace data analytics terminology and examples with general technology and introductory IT support contexts.
• Briefly introduce AI as a technology that can assist with processing information, generating content, and recognizing patterns.
• Connect to the preceding cloud reading by noting that many AI tools and services are accessed through cloud-based systems.
• Emphasize that human judgment, communication, and critical thinking remain essential.

2. The Shifting Role of the Entry-Level IT Support Professional

Adapt the existing section, The Shifting Role of the Entry-Level Analyst.

• Introduce how AI is changing everyday technology work.
• Update the three examples of changing responsibilities:
  • From manually searching for information to using AI to help locate and summarize technical information.
  • From drafting routine communications to reviewing and personalizing AI-generated explanations.
  • From organizing information manually to using AI assistance while determining what information is relevant.
• Retain the emphasis on curiosity, adaptability, and continuous learning.
• Reinforce that foundational technical knowledge remains important even when AI tools are available.

3. What AI Does Well: Speed, Scale, and Pattern Recognition

Retain the existing heading and explanation of AI capabilities.

Replace the data analytics examples with introductory technology applications:

• Processing information: Reviewing and summarizing large amounts of technical information.
• Generating content: Drafting explanations, instructions, or routine communications.
• Organizing information: Grouping similar questions, requests, or technical notes.
• Identifying patterns: Recognizing similarities across information that may help people identify potential issues.

Keep examples conceptual and avoid technical procedures.

4. What Humans Do Well: Critical Thinking, Contextual Understanding, and More

Retain the existing heading and four human skills, adapting their descriptions to technology work.

• Contextual judgment: Understanding the situation, environment, and needs of the person using technology.
• Critical auditing: Questioning and evaluating AI-generated information rather than assuming it is correct.
• Ethical oversight: Recognizing the importance of privacy, fairness, and responsible decisions.
• Strategic empathy: Understanding people’s needs and communicating technical information in an approachable way.

Retain the planned visual representation of human and AI collaboration, updating it to reflect a general technology or IT support context.

5. Scenario: AI and Human Collaboration in IT Support

Replace Use Data to Optimize Delivery Service with a simple introductory IT support scenario.

Suggested scenario: Helping a User Understand a Slow Computer

Maintain the existing scenario structure:

• AI workflow: An IT support professional uses AI to draft a simple explanation of common reasons a computer might run slowly.
• Human validation: The professional recognizes that AI does not know the user’s specific device, circumstances, or technical experience. They review the explanation, identify unsupported assumptions, and consider the user’s needs.
• The outcome: The professional provides a clearer, more appropriate explanation without presenting AI-generated possibilities as a confirmed diagnosis.

Focus on how AI and human judgment complement one another rather than how to troubleshoot the computer.

6. Key Takeaways

Retain the existing four takeaways, updating them for technology and IT support:

• Collaborative dynamic: AI can process information and generate suggestions, while people provide context and judgment.
• Shift to output auditing: As AI assists with more tasks, evaluating the accuracy and usefulness of its output becomes increasingly important.
• Curiosity drives value: Adaptability and continuous learning help technology professionals respond to changing tools and responsibilities.
• AI answers what, humans explain why: AI can identify patterns and generate information, but people interpret that information and determine its meaning within real-world situations.

Out of Scope Guardrails

• Detailed instruction on generative AI tools or prompting techniques.
• Specific AI products, interfaces, or demonstrations.
• Technical troubleshooting procedures or diagnostic commands.
• Advanced AI automation or autonomous support workflows.
• Data analytics workflows, coding, or large-scale dataset processing.
• Detailed responsible AI practices, which will be covered in Module 4.
• Assumptions that learners already understand IT support procedures or technical problem resolution.

Scope Note: This reading introduces the complementary roles of AI capabilities and durable human skills early in the certificate. Preserve the existing sections, progression, and emphasis on human and AI collaboration. Replace data analytics terminology and examples with accessible technology and introductory IT support contexts. Learners should leave understanding that AI can assist with technical work, but human judgment, communication, critical thinking, and continuous learning remain essential. Detailed AI tool use and responsible AI practices will be covered later in Course 1, Module 4.

C1M1: Module 1 Review

Content Outline

Introduction: Congratulate learners on completing Module 1 and briefly reinforce that technology systems consist of connected components working together to support users and organizations.

Module 1 Key Concepts

• Information Technology: IT involves using technology to create, process, store, secure, and exchange information.
• IT Support Responsibilities: IT support professionals help users and organizations by setting up, maintaining, and supporting technology systems.
• Technology System Components: Technology systems include users, devices, software, networks, services, and infrastructure.
• Connected Components: Technology system components work together to provide services and accomplish tasks.
• Local Systems: Local technology resources are located on or near a user’s device or within an organization’s facilities.
• Cloud-Based Systems: Cloud systems use remotely hosted computing resources and services that organizations access through networks.

Out of Scope Guardrails

• Do not introduce new concepts or detailed technical explanations.
• Do not include specific tools, troubleshooting procedures, or advanced cloud concepts.
• Do not reference the upcoming module quiz.

C1M2 Reading: Common Device Types

Asset ID: G-QIJUHU Target Length: 500–650 words (maximum 700)

Prior Knowledge: Learners have been introduced to technology systems, basic hardware concepts, and cloud infrastructure.

Reading Objective: Identify common computing device types, describe their primary characteristics, and recognize their typical uses in workplace environments.

Content Outline

1. Introduction to Common Device Types

• Explain how organizations use different devices to support workplace tasks.
• Introduce use case and factors such as portability, computing needs, and cost.

2. Desktop Computers

• Describe stationary computers and common peripherals.
• Explain typical workplace uses, including office work and specialized workstations.

3. Laptop Computers

• Describe portable computers with integrated components.
• Explain workplace uses, including remote and hybrid work.
• Briefly introduce docking stations and external peripherals.

4. Smartphones

• Describe handheld computing devices with touchscreen interfaces and wireless connectivity.
• Identify common workplace uses, including communication, applications, and accessing information.

5. Tablets

• Describe portable touchscreen devices and optional peripherals.
• Explain common workplace uses, such as inventory management, data collection, and customer check-in.

6. Internet of Things (IoT) Devices

• Define IoT devices as connected devices that collect or exchange data.
• Provide examples such as smart thermostats, badge readers, sensors, and connected office equipment.

7. Servers

• Explain how servers provide data, applications, and shared resources to other devices.
• Identify servers as physical or virtual systems that may operate on-premises or in cloud environments.

8. Key Takeaways

• Summarize the primary characteristics and typical uses of each device type.
• Briefly introduce the term endpoint for devices that connect to and use network services.

Out of Scope Guardrails

• Detailed hardware components, specifications, and performance comparisons.
• Device repair, maintenance, troubleshooting, or configuration procedures.
• Operating system comparisons and mobile device management.
• IoT security configurations and management procedures.
• Server architecture, virtualization technologies, and administration.
• Detailed networking concepts and connectivity troubleshooting.

C1M2 Reading: Form Factors

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to common device types, including desktops, laptops, smartphones, tablets, servers, and IoT devices, along with their typical workplace uses.

Reading Objective: Identify common computer form factors and describe how physical design influences device size, component integration, and workplace use.

Content Outline

1. Understanding Form Factors

• Define form factor as the physical size, shape, and arrangement of a computing device or component.
• Explain how form factors influence space requirements, portability, and hardware expansion.

2. Desktop Computer Form Factors

• Full tower: Larger cases with room for additional components and expansion.
• Mid tower: Common desktop cases that balance size and expansion options.
• Small form factor (SFF): Compact desktops designed for environments with limited space.
• All-in-one (AiO): Computers that integrate the display and primary computing components into one unit.
• Mini PC: Very compact computers suited to basic computing tasks and space-constrained workstations.

3. Motherboard Form Factors

• Introduce the motherboard as the main circuit board connecting computer components.
• Briefly explain how motherboard size and layout influence the computer’s physical design and expansion options.
• Introduce ATX, Micro-ATX, and Mini-ITX as common motherboard form factors, emphasizing relative size rather than technical specifications.

4. System-on-Chip (SoC)

• Introduce SoC as a design that integrates multiple computing functions into a single chip.
• Explain how SoCs support compact, power-efficient devices such as smartphones, tablets, and some computers.

5. Form Factors in the Workplace

• Briefly compare how physical space, portability, and expansion needs influence device selection.
• Include a simple example comparing a full tower, mini PC, and all-in-one workstation.
• Briefly acknowledge that servers can also use different physical designs, including tower and rack-mounted configurations, without explaining server architecture.

6. Key Takeaways

• Form factors describe the physical design and arrangement of devices and components.
• Different form factors support different space, portability, and expansion requirements.
• Recognizing form factors helps IT support professionals understand device configurations and physical limitations.

Out of Scope Guardrails

• Detailed motherboard standards, dimensions, slot counts, and compatibility specifications.
• Detailed motherboard components, including chipsets, memory slots, and expansion interfaces.
• Internal component installation, replacement, or upgrades.
• Processor architecture and detailed SoC design.
• Hardware performance benchmarking and purchasing recommendations.
• Detailed server architecture, rack configurations, and data center infrastructure.
• Detailed mobile device architecture, battery management, and connectivity.
• Device troubleshooting and repair procedures.

Scope Note: The previous reading introduced common device types and their uses. This reading focuses specifically on their physical designs, without repeating general device descriptions. The existing draft should be streamlined by reducing motherboard specifications, removing exact measurements, and simplifying server form factors. Detailed hardware components and connections will be addressed later in Course 1, while configuration and troubleshooting will be covered in subsequent courses.

C1M2 Reading: Mobile Hardware

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to common device types and computer form factors. In the preceding Mobile Devices video, they explored general-purpose and specialized mobile devices, integrated hardware, System-on-Chip (SoC), power efficiency, peripherals, connectivity, and basic IT support considerations.

Reading Objective: Identify common mobile hardware components and explain how physical design supports portability, power efficiency, durability, and workplace use.

Content Outline

1. Understanding Mobile Hardware Design

• Briefly reinforce that mobile devices contain many of the same fundamental hardware resources as other computers.
• Explain how portability influences component size, integration, and physical design.
• Introduce the tradeoffs between portability, power efficiency, durability, and hardware expansion.

2. Common Mobile Hardware Components

• Battery: Rechargeable batteries provide portable power and influence how long devices can operate between charges.
• Storage: Compact flash storage provides space for operating systems, applications, and user data.
• Display and input: Touchscreens, cameras, microphones, and integrated input components support interaction without traditional peripherals.
• Sensors: Components such as accelerometers, GPS receivers, and biometric sensors enable location awareness, movement detection, and other device functions.
• Reinforce that many mobile components are tightly integrated and may not be easily replaced or upgraded.

3. Power Efficiency and Portability

• Explain why managing power consumption is especially important for battery-powered devices.
• Briefly connect integrated hardware and SoC designs from the preceding video to reduced space and power requirements.
• Describe how screen size, processing activity, and wireless connectivity can influence battery usage.
• Avoid detailed battery technologies or power management procedures.

4. Durability and Specialized Mobile Hardware

• Explain how mobile hardware may be designed for different physical environments.
• Rugged devices: Reinforced designs that help protect devices from drops, dust, and moisture.
• Wearable computers: Compact devices designed for hands-free or continuous use, such as smartwatches and industrial smart glasses.
• Vehicle-mounted computers: Devices designed for use in vehicles, including delivery, transportation, and field service environments.
• Briefly compare how workplace conditions influence hardware design.

5. Mobile Hardware in the Workplace

• Explain how IT professionals consider device portability, battery life, durability, and connectivity when supporting mobile hardware.
• Include a simple workplace example comparing a standard tablet used in an office with a rugged tablet used in a warehouse.
• Reinforce that different workplace requirements influence the hardware selected and supported.

6. Key Takeaways

• Mobile hardware uses compact, integrated components to support portable computing.
• Battery life, durability, and physical design influence how mobile devices function in different environments.
• Understanding mobile hardware characteristics helps IT professionals recognize device capabilities and limitations.

Out of Scope Guardrails

• Reintroducing general-purpose and specialized mobile device categories already explained in the preceding video.
• Detailed CPU, RAM, motherboard, or SoC architecture.
• Battery chemistry, charging technologies, and advanced power management.
• Detailed wireless networking technologies, protocols, and configuration.
• Detailed USB-C, Thunderbolt, Bluetooth, and other connector specifications.
• Mobile operating systems, app stores, and application management.
• Mobile device deployment models, BYOD policies, and privacy procedures.
• Hardware disassembly, component replacement, troubleshooting, and repair.

Scope Note: The preceding Mobile Devices video introduces mobile device categories, integrated hardware, SoC, peripherals, connectivity, and basic IT support responsibilities. This reading builds on those concepts by examining the physical components and design considerations that enable mobile computing. Avoid repeating the video’s explanations of device categories, SoC, and connectors. Focus on how mobile hardware design supports portability, power efficiency, durability, and different workplace requirements.

C1M2 Reading: Peripherals

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to common device types, form factors, and mobile hardware. In the preceding Processing, Memory, and Storage video, they explored how the CPU, RAM, and long-term storage work together to run applications and manage data.

Reading Objective: Classify common computer peripherals by function and describe how they connect to and extend the capabilities of computing systems.

Content Outline

1. Understanding Peripherals

• Define peripherals as devices that connect to a computer to provide input, output, storage, or additional functionality.
• Explain how peripherals allow users to interact with computers and extend their capabilities.
• Distinguish between internal hardware resources and connected peripheral devices.

2. Common Peripheral Types

• Input devices: Keyboards, mice, scanners, microphones, and webcams that provide information to a computer.
• Output devices: Monitors, printers, speakers, and projectors that present information from a computer.
• Input and output devices: Touchscreens and multifunction printers that support both functions.
• External storage devices: USB flash drives and external drives used to store or transfer files.
• Briefly explain that some peripheral functions may also be built into a device.

3. How Peripherals Connect

• Wired connections: Introduce USB as a common connection for peripherals, along with HDMI and DisplayPort for displays.
• Wireless connections: Introduce Bluetooth and Wi-Fi as technologies that allow compatible peripherals to communicate without a direct cable connection.
• Explain that peripherals must use connection methods supported by the computer.
• Briefly introduce device drivers as software that helps the operating system communicate with hardware.

4. Peripherals in the Workplace

• Explain how different workplace tasks require different peripheral devices.
• Include examples such as a headset for remote meetings, a barcode scanner for inventory management, and an external monitor for a workstation.
• Explain why IT support professionals need to recognize peripheral functions and connection requirements when supporting users.

5. Key Takeaways

• Peripherals extend a computer’s functionality through input, output, storage, and other capabilities.
• Peripherals connect through wired or wireless technologies.
• Understanding peripheral functions and connections helps IT professionals recognize how computing systems support workplace tasks.

Out of Scope Guardrails

• Detailed explanations of CPU, RAM, and internal storage covered in the preceding video.
• Internal data buses and detailed communication between hardware components.
• Detailed USB standards, connector generations, and transfer speeds.
• Advanced display technologies and specifications.
• Detailed printer technologies and maintenance.
• Device driver installation and operating system configuration.
• Peripheral troubleshooting, repair, and replacement procedures.
• Detailed wireless networking protocols and configuration.
• Hardware purchasing recommendations and performance comparisons.

Scope Note: The preceding Processing, Memory, and Storage video explains how internal hardware resources work together to process and retain information. This reading extends that understanding to peripheral devices that provide input, output, external storage, and additional functionality. Avoid repeating the video’s explanations of CPU, RAM, storage, or internal data movement. Focus on identifying peripheral categories, understanding basic connection methods, and recognizing their role in workplace computing. Detailed peripheral configuration and troubleshooting will be addressed in later courses.

C1M2 Reading: Ports

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to common device types, computer form factors, and mobile hardware. In the preceding Peripherals reading, they explored common input, output, and external storage devices and how these devices extend a computer’s capabilities.

Reading Objective: Identify common physical computer ports and describe their functions and basic compatibility considerations when connecting devices and peripherals.

Content Outline

1. Understanding Computer Ports

• Define a port as a physical interface on a computer or device used to connect external hardware.
• Explain how ports support functions such as data transfer, display output, audio, power delivery, and network connectivity.
• Distinguish between a port on a device and the cable or connector that plugs into it.

2. Common Computer Ports

• USB-A: A common rectangular port used to connect peripherals such as keyboards, mice, and external storage devices.
• USB-C: A small, reversible port that can support data transfer, charging, and, on compatible devices, video output.
• Thunderbolt: A high-speed connection technology used for compatible peripherals, displays, and docking stations. Briefly explain that modern Thunderbolt ports use the USB-C connector shape, but not all USB-C ports support Thunderbolt.
• HDMI: A connection commonly used to transmit video and audio to monitors, televisions, and projectors.
• DisplayPort: A connection primarily used to transmit video and audio to external displays.
• Ethernet (RJ-45): A physical port commonly used to connect a computer to a wired network.
• 3.5 mm audio jack: A common connection for headphones, speakers, microphones, and compatible headsets.

3. Ports and Device Compatibility

• Explain that ports have different physical shapes and support different functions.
• Describe the importance of matching a device’s port with a compatible cable or connector.
• Explain that some ports share the same physical connector but support different capabilities, such as USB-C and Thunderbolt.
• Briefly introduce adapters and docking stations as ways to connect devices when the required ports are not directly available.

4. Ports in the Workplace

• Explain why IT support professionals need to recognize common ports when connecting computers and peripherals.
• Include a simple workplace example involving a laptop connected to an external monitor, keyboard, and mouse.
• Briefly demonstrate how identifying available ports helps determine whether a direct cable, adapter, or docking station is needed.

5. Key Takeaways

• Physical ports provide connection points for external devices, displays, audio equipment, and networks.
• Different ports support different functions and require compatible connectors.
• Recognizing common ports helps IT professionals understand how computers connect to workplace equipment.

Out of Scope Guardrails

• Repeating detailed descriptions of peripheral categories covered in the preceding reading.
• Detailed USB and Thunderbolt versions, generations, transfer speeds, and power delivery specifications.
• Advanced display technologies and performance specifications.
• Legacy port standards such as VGA, DVI, PS/2, serial, and parallel, beyond an optional brief acknowledgment.
• Detailed Ethernet standards, network speeds, and cabling specifications.
• Internal motherboard connectors and expansion interfaces.
• Network ports used by software and communication protocols, such as TCP and UDP port numbers.
• Wired versus wireless connection comparisons, Bluetooth connectivity, and Ethernet communication.
• Device configuration, driver installation, and troubleshooting procedures.
• Detailed docking station specifications and purchasing recommendations.

Scope Note: The preceding Peripherals reading introduces devices that extend a computer’s capabilities. This reading focuses specifically on the physical ports used to connect those devices, including all seven port types identified in the Skills and Knowledge document. Emphasize visual recognition, basic functions, and physical compatibility without introducing detailed technical specifications. The following Connections reading will explain wired versus wireless connections, Bluetooth, and Ethernet. Detailed configuration and troubleshooting will be addressed in subsequent courses.

C1M2 Reading: Connections

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to common device types, computer hardware resources, and peripherals. In the preceding Ports reading, they explored common physical ports, their functions, and basic compatibility considerations when connecting devices.

Reading Objective: Compare wired and wireless connections and describe how Ethernet and Bluetooth support communication between computers, peripherals, and other devices.

Content Outline

1. Understanding Device Connections

• Explain how connections allow computers, peripherals, and other devices to exchange information.
• Distinguish between wired connections, which use physical cables, and wireless connections, which communicate without a direct cable.
• Introduce reliability, mobility, and convenience as considerations when choosing connection methods.

2. Wired Connections

• Explain how wired connections use cables to establish a physical communication path between devices.
• Ethernet: Introduce Ethernet as a common technology for connecting computers and other devices to a local network.
• Briefly explain how an Ethernet cable connects a computer to network equipment, such as a switch or router.
• Describe common advantages of wired connections, including consistent performance and reliability.

3. Wireless Connections

• Explain how wireless connections allow devices to communicate without a direct physical cable.
• Bluetooth: Introduce Bluetooth as a short-range wireless technology commonly used to connect peripherals such as keyboards, mice, headphones, and headsets.
• Wi-Fi: Briefly distinguish Wi-Fi from Bluetooth by explaining that Wi-Fi commonly connects devices to a local network, while Bluetooth commonly connects nearby devices and accessories.
• Describe how wireless connections support mobility and reduce the need for cables.

4. Comparing Wired and Wireless Connections

• Compare wired and wireless connections based on mobility, reliability, convenience, and physical requirements.
• Explain that connection quality can be influenced by factors such as distance, interference, and the surrounding environment.
• Reinforce that the appropriate connection method depends on the devices and workplace requirements.

5. Connections in the Workplace

• Include a simple workplace example comparing a desktop computer connected to a network through Ethernet with a laptop connected through Wi-Fi.
• Include a peripheral example, such as a wireless Bluetooth headset compared with a wired USB headset.
• Explain why IT support professionals need to recognize connection types when supporting users and workplace devices.

6. Key Takeaways

• Wired and wireless connections allow devices to communicate and exchange information.
• Ethernet is commonly used for wired network connections, while Bluetooth connects nearby devices and peripherals.
• Different connection methods offer different advantages depending on mobility, reliability, and workplace requirements.

Out of Scope Guardrails

• Repeating detailed descriptions of physical ports, cables, and connectors covered in the preceding reading.
• Detailed Ethernet standards, cable categories, and network speeds.
• Bluetooth versions, profiles, pairing procedures, and technical specifications.
• Detailed Wi-Fi standards, frequency bands, and wireless network configuration.
• Network architecture, IP addressing, routing, and network protocols.
• Network equipment configuration, including switches, routers, and wireless access points.
• Detailed network security, encryption, and authentication.
• Connection troubleshooting, diagnostic commands, and repair procedures.
• Advanced comparisons of network performance and bandwidth.

Scope Note: The preceding Ports reading focuses on physical interfaces and device compatibility. This reading shifts the focus to how devices communicate through wired and wireless connections. The Skills and Knowledge document specifically identifies wired versus wireless connections, Bluetooth, and Ethernet as the required topics. Wi-Fi should be included only as a brief comparison to help learners distinguish common wireless connection methods. Emphasize basic connection concepts and practical workplace examples without introducing network configuration or troubleshooting. Detailed networking concepts will be developed in Course 3, while connection troubleshooting will be addressed in later support-focused content.

C1M2 Reading: Components of an Operating System

Target Length: 550–700 words (maximum 800)

Prior Knowledge: Learners have been introduced to computer hardware resources, peripherals, and connections. In the preceding What an Operating System Does video, they explored how operating systems manage hardware resources, support applications, and provide ways for users to interact with computers.

Reading Objective: Describe the primary components and functions of an operating system, including resource management, user interfaces, system security, and basic system startup.

Content Outline

1. Understanding Operating System Components

• Briefly reinforce that an operating system manages hardware resources and provides services for applications and users.
• Introduce the kernel as the core component responsible for managing system resources.
• Explain that operating systems provide user interfaces and system services that allow users and applications to interact with hardware.
• Avoid detailed explanations of kernel architecture and user space.

2. Managing Hardware Resources

• Processor (CPU): Coordinates how applications and system processes use processing resources.
• Memory (RAM): Allocates and manages memory needed by running applications.
• Storage (SSD/HDD): Organizes and manages files and data stored on storage devices.
• Input and output (I/O) devices: Manages communication with devices such as keyboards, mice, monitors, and printers.
• Briefly explain that the operating system coordinates these resources to support multiple running applications.

3. Managing Security and Network Connections

• System security: Introduce how operating systems help protect devices and information through user accounts, permissions, and access controls.
• Network connections: Explain how operating systems manage network connectivity so devices and applications can communicate.
• Include simple examples such as signing in to a computer or accessing a shared network resource.

4. User Interfaces

• Explain how operating systems provide interfaces for users to interact with applications and system resources.
• Graphical User Interface (GUI): Uses windows, icons, menus, and other visual elements.
• Command-Line Interface (CLI): Allows users to interact with the system by entering text commands.
• Briefly compare the two interfaces without introducing specific commands or procedures.

5. System Start-up Basics

• Briefly introduce what happens when a computer is powered on before the operating system loads.
• System firmware: Software that initializes hardware during startup.
• POST (Power-On Self-Test): Checks essential hardware during the startup process.
• BIOS/UEFI: Introduce BIOS as legacy firmware and UEFI as the modern standard. Explain that legacy refers to older technology that may still be used or referenced. Clarify that some manufacturers continue using the term BIOS when referring to UEFI.
• Bootloader: Software responsible for loading the operating system.
• Secure Boot: A security feature that helps verify trusted startup software.
• OS kernel: The core operating system component that takes control as startup continues.
• Keep these concepts at an introductory terminology level rather than explaining detailed startup sequences.

6. How Operating Systems Connect Users, Applications, and Hardware

• Explain that the operating system serves as an intermediary between users, applications, and hardware.
• Introduce the relationship between these components without explaining the complete request process.
• Include a simple visual showing the relationship:

User → Application → Operating System → Hardware

– Reinforce that the operating system coordinates hardware resources and provides services that applications rely on.

7. Key Takeaways

• Operating systems manage processing, memory, storage, and input/output devices.
• Operating systems provide security, network services, and user interfaces.
• System startup involves firmware and other components that prepare the computer to load the operating system.
• Operating systems connect users and applications with the computer’s hardware.

Out of Scope Guardrails

• Repeating the general introduction to operating systems from the preceding video.
• Detailed kernel architecture, user space, and operating system internals.
• CPU scheduling algorithms, memory allocation techniques, and detailed process management.
• Detailed file system structures, partitions, and storage configuration.
• Detailed startup sequences, firmware configuration, and Secure Boot implementation.
• Operating system installation, configuration, and administration.
• Detailed security settings, user account management, and permission configuration.
• Network protocols, IP addressing, and network configuration.
• Specific GUI navigation procedures or CLI commands.
• Detailed comparisons of Windows, macOS, Linux, ChromeOS, and mobile operating systems.
• Step-by-step request processing, system calls, APIs, and detailed communication between applications, the operating system, and hardware.

Scope Note: The preceding What an Operating System Does video introduces the operating system’s overall purpose. This reading expands on the specific resources and functions it manages, introduces basic system startup terminology, and establishes the relationship between users, applications, operating systems, and hardware. Keep the explanations at the Remember and Understand level identified in the Skills and Knowledge document. The following Requests to the Operating System reading will demonstrate how a user action moves through an application and operating system to interact with hardware, so avoid explaining that process in detail here.

C1M2 Reading: Requests to the Operating System

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to computer hardware resources and the functions of an operating system. In the preceding Components of an Operating System reading, they explored how operating systems manage processing, memory, storage, input/output devices, security, and network connections. They also learned how operating systems connect users, applications, and hardware.

Reading Objective: Explain how user actions generate requests that pass through applications and the operating system to hardware, and describe how the operating system coordinates resources to complete those requests.

Content Outline

1. Understanding Requests to the Operating System

• Explain that everyday computer activities generate requests that the operating system helps process.
• Introduce how applications rely on operating system services to access hardware resources and perform tasks.
• Reinforce the relationship between users, applications, operating systems, and hardware without repeating their individual functions.

2. How a Request Moves Through a Computer

– Introduce the basic flow of a request:

User → Application → Operating System → Hardware

• User: Initiates an action, such as opening a file, saving a document, or playing a video.
• Application: Interprets the user’s action and requests the resources or services needed.
• Operating system: Coordinates access to hardware resources and manages the requested operation.
• Hardware: Performs the necessary processing, storage, or input/output operations.
• Explain that the results are returned through the operating system and application so the user can see or interact with them.

3. The Operating System at Work Behind the Scenes

• Explain that the operating system coordinates multiple resources to complete a request.
• Briefly connect the roles of CPU, RAM, storage, and input/output devices to the request process.
• Explain that applications generally rely on the operating system rather than directly controlling hardware.
• Reinforce that the operating system manages requests from multiple applications while the computer is running.

4. Following a Request: Opening a Document

• Use one simple example to illustrate the complete process:
  • A user selects a document to open.
  • The application requests access to the file.
  • The operating system coordinates retrieving the file from storage and making its contents available in memory.
  • The CPU processes instructions needed to open and display the document.
  • The application displays the document for the user.
• Include a simple visual showing how the request moves through the system and how the result reaches the user.
• Emphasize the coordination between software and hardware rather than technical implementation details.

5. Why Understanding Requests Matters in IT Support

• Explain how understanding the relationship between applications, operating systems, and hardware helps IT professionals recognize that a single user action may depend on multiple system resources.
• Include a brief example, such as an application taking longer than expected to open a file, to illustrate that the behavior may involve the application, operating system, or hardware.
• Avoid introducing troubleshooting procedures or asking learners to diagnose the issue.

6. Key Takeaways

• User actions generate requests that applications pass to the operating system.
• The operating system coordinates hardware resources and services to complete those requests.
• Understanding request flow helps IT professionals recognize how hardware and software work together during everyday computing tasks.

Out of Scope Guardrails

• Repeating detailed explanations of operating system components and resource management covered in the preceding reading.
• Detailed operating system architecture, kernel internals, and user space.
• System calls, APIs, interrupts, and low-level request handling.
• CPU scheduling algorithms, memory allocation techniques, and process management details.
• Detailed file system operations, storage architecture, and data transfer mechanisms.
• Operating system startup, firmware, BIOS/UEFI, and bootloaders.
• Application development, programming, and operating system APIs.
• Detailed performance analysis, diagnostic tools, and troubleshooting procedures.
• Operating system configuration, administration, and command-line operations.

Scope Note: The preceding Components of an Operating System reading explains what operating systems manage and introduces the relationship between users, applications, operating systems, and hardware. This reading builds on that foundation by demonstrating how those components work together to complete a user request. The Skills and Knowledge document specifically identifies the flow from user to application to operating system to hardware, along with the operating system’s work behind the scenes. Focus on one clear, relatable example rather than multiple technical scenarios. Detailed operating system operations and troubleshooting will be addressed in subsequent courses.

C1M2 Reading: Virtual Machines

Target Length: 500–650 words (maximum 750)

Prior Knowledge: Learners have been introduced to computer hardware resources, operating system components, and how applications interact with operating systems and hardware. They understand that operating systems manage CPU, memory, storage, and input/output resources.

Reading Objective: Explain how virtual machines and hypervisors allow multiple operating systems to share physical hardware resources, and identify common uses, advantages, and limitations of virtualization in IT environments.

Content Outline

1. Understanding Virtual Machines

• Define a virtual machine (VM) as a software-based computer that operates within a physical computer.
• Explain how a VM can run its own operating system and applications while sharing the resources of a physical computer.
• Introduce the terms host (the physical computer or system providing resources) and guest (the operating system running inside a virtual machine).
• Briefly explain that a single physical computer can support multiple virtual machines.

2. How Virtual Machines Work

• Introduce a hypervisor as the technology that creates and manages virtual machines.
• Explain how the hypervisor provides virtual machines with access to physical computing resources.
• Describe how each VM operates as a separate computing environment.
• Include a simple visual showing one physical computer supporting multiple virtual machines through a hypervisor.
• Avoid detailed hypervisor architecture or implementation.

3. Resource Allocation and Virtual Hardware

• Explain how virtual machines use allocated CPU, RAM, storage, and network resources from the host system.
• Introduce the concept of virtual hardware, such as virtual processors, memory, and storage.
• Explain that the physical computer must have sufficient resources to support the host environment and its virtual machines.
• Briefly describe how running multiple VMs can affect available system resources and performance.

4. Common Uses of Virtual Machines in IT Support

• Operating system exploration: Run a different operating system without replacing the computer’s existing operating system.
• Software testing: Test applications or changes in a separate environment.
• IT training and practice: Provide environments where learners and technicians can practice technical tasks.
• Workplace infrastructure: Support multiple virtual servers or computing environments on shared physical hardware.
• Include a simple example of an IT technician using a Linux VM on a Windows computer to explore Linux tools.

5. Advantages and Limitations of Virtual Machines

• Advantages: Efficient use of physical hardware, flexibility, separate computing environments, and the ability to create or restore virtual environments.
• Limitations: VMs share finite physical resources, may perform differently from physical computers, and require appropriate configuration and management.
• Briefly explain that separation between virtual machines can reduce the impact of some changes, but does not guarantee complete security or isolation.

6. Key Takeaways

• Virtual machines allow multiple operating systems and computing environments to run using shared physical hardware.
• Hypervisors manage virtual machines and their access to computing resources.
• Virtualization supports testing, training, and workplace infrastructure but depends on available hardware resources.

Out of Scope Guardrails

• Detailed Type 1 and Type 2 hypervisor architecture and comparisons.
• Step-by-step VM creation, installation, or configuration.
• Specific virtualization platforms, product interfaces, and version-dependent procedures.
• Detailed virtual networking, virtual switches, and network configuration.
• Advanced resource allocation, CPU scheduling, and memory management.
• Containers, Kubernetes, and container orchestration.
• Cloud infrastructure architecture and advanced server virtualization.
• VM troubleshooting, performance tuning, and security hardening.
• Detailed snapshots, cloning, migration, and backup procedures.

Scope Note: The preceding operating system readings explain how operating systems manage hardware resources and coordinate requests from applications. This reading extends those concepts by introducing how multiple operating systems can operate as virtual machines using shared physical hardware. The Skills and Knowledge document identifies hypervisors, resource allocation and architecture, practical IT support use cases, and advantages and limitations as the required areas. Keep the content at the Remember and Understand level, emphasizing conceptual understanding rather than VM configuration. Hands-on use of Windows and Linux virtual machines will be addressed in Course 2.

C1M2 Reading: Mobile Backend Cloud Resources

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to mobile hardware and operating systems. In the preceding Mobile Operating Systems video, they explored how mobile operating systems are designed for battery efficiency, specialized hardware, and different interaction methods, including touch, motion, and voice.

Reading Objective: Explain how mobile devices use cloud computing resources to support processing, data storage, and synchronization beyond their local hardware capabilities.

Content Outline

1. Understanding Mobile Backend Cloud Resources

• Introduce cloud computing as computing resources and services accessed over a network rather than provided entirely by a local device.
• Explain that mobile devices often rely on remote cloud infrastructure to support applications and services.
• Describe how cloud resources complement the limited processing power, storage capacity, and battery resources of mobile devices.

2. Cloud Processing Resources

• Explain how some mobile applications use remote servers to perform processing tasks that would require substantial local computing resources.
• Describe how applications can send requests to cloud services and receive processed results.
• Include a simple example, such as a mobile application using cloud resources to process an image or provide AI-powered functionality.
• Clarify that mobile devices still perform local processing and do not rely on the cloud for every task.

3. Cloud Data Storage

• Explain how cloud services provide remote storage for files, application data, and other information.
• Distinguish between information stored locally on a mobile device and information stored remotely.
• Introduce cloud databases as services that store and retrieve application information, with security controls to protect access.
• Explain how remote storage allows users and applications to access information across devices.
• Include a familiar example, such as photos, documents, or application data stored in the cloud.

4. File and Data Synchronization

• Define synchronization as keeping information consistent across devices and cloud services.
• Explain how changes made on one device can be reflected on other connected devices.
• Include a simple example of editing a document on a smartphone and accessing the updated version on a laptop.
• Briefly explain that synchronization generally requires network connectivity and may be delayed when a device is offline.

5. Cloud Resources in Everyday Mobile Computing

• Use one relatable scenario to demonstrate how local mobile hardware and cloud resources work together.
• For example, a user takes a photo with a smartphone, stores it through a cloud service, and accesses it from another device.
• Identify which activities happen locally and which depend on remote cloud resources.
• Reinforce that mobile operating systems and applications help users access these services.

6. Key Takeaways

• Mobile devices use cloud resources to extend their local computing and storage capabilities.
• Cloud services provide additional processing power and remote data storage, including databases for application information.
• Synchronization helps keep information accessible and consistent across multiple devices.
• Mobile computing often combines local device resources with remote cloud services.

Out of Scope Guardrails

• Repeating mobile operating system concepts covered in the preceding video, including battery optimization, specialized operating systems, and mobile interaction methods.
• Detailed cloud computing architecture, service models, and deployment models.
• Cloud infrastructure configuration, administration, and management.
• Specific cloud provider platforms, pricing, and service comparisons.
• Detailed client-server architecture, APIs, and backend development.
• Database architecture, storage technologies, and data replication mechanisms.
• Detailed AI model architecture or cloud-based AI processing.
• Network protocols, bandwidth calculations, and connectivity troubleshooting.
• Cloud security configuration, identity management, and access control procedures.
• Mobile application installation, configuration, and troubleshooting.

Scope Note: The preceding Mobile Operating Systems video introduces how mobile operating systems support devices with limited hardware and battery resources. This reading builds on that foundation by explaining how mobile devices use remote cloud infrastructure for additional processing power, secure database storage, and file synchronization. These three capabilities are specifically identified in the Skills and Knowledge document. Focus on how cloud resources complement local mobile hardware without introducing detailed cloud architecture or configuration. The following Mobile Software Resources reading will address how mobile applications and operating systems work within constraints such as battery life, variable network connectivity, and smaller interfaces.

C1M2 Reading: Mobile Software Resources

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to mobile hardware and operating systems. In the Mobile Operating Systems video, they explored how mobile operating systems are optimized for battery efficiency, specialized hardware, and touch-based interaction. In the preceding Mobile Backend Cloud Resources reading, they learned how mobile devices use remote cloud services for processing, data storage, and synchronization.

Reading Objective: Describe how mobile operating systems and applications manage software resources within the constraints of battery life, network connectivity, and device interfaces.

Content Outline

1. Understanding Mobile Software Resources

• Define mobile software resources as the operating system, applications, and supporting software services that enable mobile devices to perform tasks.
• Explain how mobile software must operate within the physical limitations of portable devices.
• Introduce three primary constraints: limited battery life, variable network connectivity, and smaller interfaces.

2. Managing Mobile Software Resources

• Explain how mobile operating systems manage applications and system resources to conserve battery power and maintain responsiveness.
• Foreground applications: Introduce applications actively being used and explain why they generally receive priority for system resources.
• Background applications: Explain how mobile operating systems may limit, pause, or suspend background activity to conserve resources.
• Briefly explain that these restrictions can affect when applications perform tasks such as refreshing information or synchronizing data.
• Avoid detailed explanations of operating system scheduling or memory management.

3. Mobile Application Design Considerations

• Battery life: Explain how applications must balance functionality with power consumption.
• Network connectivity: Describe how applications may need to function with intermittent or unavailable network connections.
• Smaller interfaces: Explain how mobile applications are designed for compact screens and touch-based interaction.
• Include a simple example of a mobile application that allows users to view previously downloaded information when temporarily offline.

4. Mobile Applications and Cloud Resources

• Explain how many mobile applications function as lightweight clients that provide the user interface locally while relying on remote servers for some processing and data.
• Briefly connect this concept to the preceding reading on cloud resources without repeating the explanation of cloud infrastructure.
• Include a simple example, such as a mobile banking or document application that displays information locally while retrieving updated data from a remote service.
• Reinforce that some applications work primarily on the device, while others depend more heavily on network connectivity and remote services.

5. Mobile Software in the Workplace

• Explain how mobile software supports common workplace tasks such as communication, accessing documents, and updating information while away from a desk.
• Briefly describe how battery limitations, network availability, and application resource management can affect the user experience.
• Include a simple workplace example of an employee using a mobile application in an area with limited connectivity.
• Emphasize recognizing these software constraints rather than diagnosing or resolving problems.

6. Key Takeaways

• Mobile software operates within constraints related to battery life, network connectivity, and device interfaces.
• Mobile operating systems prioritize active applications and manage background activity to conserve resources.
• Some mobile applications rely on remote cloud services while providing their user interfaces locally.
• Understanding mobile software resources helps IT professionals recognize how mobile devices support everyday workplace tasks.

Out of Scope Guardrails

• Repeating detailed explanations of mobile operating systems, device types, and hardware components covered in preceding assets.
• Detailed cloud computing infrastructure, remote processing, and storage architecture covered in the preceding reading.
• Mobile operating system architecture, process scheduling algorithms, and advanced memory management.
• Detailed differences between Android and iOS resource management.
• Mobile application development, programming, and software architecture.
• Application installation, updates, permissions, and configuration procedures.
• Mobile device management (MDM), deployment models, and organizational policies.
• Detailed wireless networking protocols and configuration.
• Battery optimization procedures and device performance tuning.
• Mobile application troubleshooting and repair procedures.

Scope Note: The preceding Mobile Backend Cloud Resources reading explains how mobile devices use remote processing, secure storage, and synchronization services. This reading shifts the focus to how mobile software operates within device limitations. The Skills and Knowledge document specifically identifies limited battery life, variable network connectivity, smaller interfaces, foreground application prioritization, background application suspension, and lightweight mobile clients that offload processing to remote servers. Keep the emphasis on these concepts without repeating the cloud infrastructure explanations or the general introduction to mobile operating systems. Detailed mobile device configuration, application management, and troubleshooting will be addressed in subsequent courses.

C1M2 Reading: Types of Software

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to computer hardware, operating systems, and applications. In the preceding Mobile Software Resources reading, they explored how mobile operating systems and applications manage resources and operate within device limitations. They also learned how some applications rely on cloud services for additional functionality.

Reading Objective: Distinguish between system software and application software and describe how each supports the operation and use of computing devices.

Content Outline

1. Understanding Software

• Define software as the programs and instructions that tell computing devices what to do.
• Briefly reinforce the relationship between software and hardware.
• Introduce the two primary categories of software: system software and application software.

2. System Software

• Define system software as software that manages computer resources and supports the operation of other software.
• Operating systems: Windows, macOS, Linux, ChromeOS, Android, and iOS.
• Device drivers: Software that allows operating systems to communicate with hardware devices.
• System utilities: Programs that support system maintenance, security, and basic operations.
• Explain that system software often operates in the background without requiring direct user interaction.

3. Application Software

• Define application software as programs designed to help users complete specific tasks.
• Introduce common application categories:
  • Productivity: Word processors, spreadsheets, and presentation software.
  • Communication: Email, messaging, and video conferencing applications.
  • Web browsers: Applications used to access websites and web-based services.
  • Specialized applications: Software designed for specific workplace tasks, such as inventory management or scheduling.
• Explain that applications rely on the operating system and hardware resources to function.

4. How System Software and Application Software Work Together

• Explain how system software provides the environment and services needed for applications to run.
• Include a simple example of a user opening a word processing application:
  • The application provides tools for creating and editing a document.
  • The operating system manages the processing, memory, storage, and input/output resources the application needs.
  • The computer’s hardware performs the underlying operations.
• Reinforce the distinction between software that supports the computer’s operation and software that supports user tasks.

5. Software in the Workplace

• Explain why IT support professionals need to recognize different software categories.
• Include a brief example distinguishing an operating system issue from an issue involving a specific application, without introducing troubleshooting procedures.
• Reinforce that workplace computers typically rely on multiple types of software working together.

6. Key Takeaways

• Software provides the instructions that allow computing devices to perform tasks.
• System software manages computer resources and supports other programs.
• Application software helps users complete specific tasks.
• Both types of software work together to support everyday computing activities.

Out of Scope Guardrails

• Repeating detailed explanations of operating system components and resource management covered in earlier readings.
• Detailed mobile operating system resource management and cloud services.
• Software development, programming languages, and application architecture.
• Detailed operating system installation, configuration, and administration.
• Device driver installation and management procedures.
• Software licensing models, purchasing, and subscription comparisons.
• Detailed software updates, patches, and version management.
• Application installation, configuration, and troubleshooting.
• Advanced software categories, including middleware, virtualization platforms, and development frameworks.

Scope Note: The preceding Mobile Software Resources reading focuses on how mobile operating systems and applications operate within device limitations. This reading broadens the focus to software across computing systems. The Skills and Knowledge document specifically identifies system software and application software as the required categories, with G-H8EJPY IT101 C1M5 Video: Types of Software identified as the starting asset. Emphasize the distinction between these two categories and how they work together without repeating detailed operating system concepts or introducing software management procedures.

C1M2 Reading: Technology Behind Everyday Tasks

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have explored files and folders, accounts, authentication, authorization, and access permissions. In the immediately preceding What Happens Beyond the Device video, they learned how local devices connect to remote resources through networks, services, and supporting infrastructure. The video demonstrated these relationships through an example of editing a shared online document.

Reading Objective: Identify common IT support responsibilities associated with the networks, services, and infrastructure that support everyday technology tasks.

Content Outline

1. Technology Systems Require Ongoing Support

• Reinforce that everyday technology tasks often depend on resources beyond the user’s device.
• Explain that IT professionals help keep the networks, services, and infrastructure supporting these tasks available and functioning.
• Introduce the distinction between using technology and supporting the systems that make it work.
• Briefly connect these responsibilities to familiar workplace activities such as accessing shared files, using online applications, and communicating with coworkers.

2. Supporting Networks

• Explain that network support helps devices maintain access to shared and remote resources.
• Introduce common responsibilities:
  • Checking whether devices are connected to a network.
  • Recognizing when multiple users are experiencing connectivity problems.
  • Helping users access network resources.
  • Reporting or escalating connectivity issues when necessary.
• Example: An employee cannot access a shared company folder because their device has lost network connectivity.
• Emphasize the relationship between network availability and everyday workplace tasks.

3. Supporting Services

• Explain that services provide capabilities that applications and users depend on.
• Introduce common responsibilities:
  • Checking whether a service is available.
  • Helping users access services with their accounts.
  • Recognizing when a problem affects a service rather than an individual device.
  • Communicating service interruptions to users or other IT teams.
• Example: Multiple employees cannot access their organization’s online calendar, even though their devices remain connected to the network.
• Reinforce that an available network does not necessarily mean every service is functioning.

4. Supporting Infrastructure

• Explain that infrastructure includes the physical equipment and systems that support networks and services.
• Introduce common responsibilities:
  • Monitoring or checking the status of infrastructure equipment.
  • Recognizing when infrastructure problems may affect multiple users or services.
  • Performing assigned checks or maintenance tasks using established procedures.
  • Reporting problems to the appropriate support team.
• Example: A problem with a shared network device prevents several employees from accessing workplace resources.
• Emphasize that entry-level IT professionals may assist with infrastructure support without being responsible for configuring or repairing complex systems.

5. Connecting Support Responsibilities to Everyday Tasks

• Use a short workplace scenario that differs from the shared online document example in the preceding video.
• Suggested scenario: An employee cannot access an organization’s web-based scheduling application.
• Identify the different support areas that might be involved:
  • Network: Is the employee’s device connected?
  • Service: Is the scheduling application available?
  • Infrastructure: Are the underlying systems supporting the connection and service operating?
• Explain that different IT teams may be responsible for different parts of the system.
• Reinforce that understanding these relationships helps IT professionals recognize where support may be needed, without requiring learners to diagnose the problem.

6. Key Takeaways

• Everyday technology tasks depend on networks, services, and supporting infrastructure.
• Network support focuses on connectivity and access to shared resources.
• Service support focuses on the availability and accessibility of capabilities users depend on.
• Infrastructure support focuses on the underlying equipment and systems.
• IT professionals may support different parts of a technology system and collaborate when problems affect multiple components.

Out of Scope Guardrails

• Repeating definitions of local resources, remote resources, networks, services, and infrastructure from the preceding video.
• Repeating the shared online document example.
• Detailed network configurations, protocols, addressing, or network architecture.
• Service deployment, administration, or configuration.
• Server installation, data center operations, or infrastructure architecture.
• Detailed troubleshooting workflows, diagnostic tools, or root cause analysis.
• Step-by-step instructions for resolving connectivity or service problems.
• Advanced monitoring platforms, alert management, or incident response procedures.
• Detailed account administration or access permission configuration.
• Introducing requests and responses as a formal system workflow, which is covered in Course 1 Module 3.

Scope Note: The preceding What Happens Beyond the Device video explains how devices, networks, services, and infrastructure work together to complete a task. This reading shifts the focus to the IT support responsibilities associated with those components. The Skills and Knowledge document specifically identifies IT support tasks for networks, services, and infrastructure as the required coverage. Keep the discussion introductory and focused on recognizing responsibilities rather than performing technical procedures. This also establishes a foundation for the more detailed system interactions and problem recognition introduced in Course 1 Module 3.

C1M2 Reading: Module 2 Review

Target Length: 200–300 words

Reading Objective: Summarize the key components of technology systems and their roles in supporting everyday tasks.

Content Outline

Briefly introduce the major concepts covered in Module 2, emphasizing how hardware, software, and connected resources work together.

Key Concepts to Review

• Devices and Form Factors: Different device types and physical designs support different computing needs.
• Hardware Resources and Connections: Processors, memory, storage, peripherals, and connections enable devices to perform tasks.
• Operating Systems and Applications: Operating systems manage hardware resources and provide the environment in which applications run.
• Files, Folders, and Access: Files organize information, while accounts, authentication, and permissions help control access to resources.
• Networks, Services, and Infrastructure: Connected systems provide access to resources and capabilities beyond an individual device.
• IT Support Responsibilities: IT professionals help maintain access to the devices, networks, services, and infrastructure that users depend on.

Out of Scope Guardrails

• No new concepts or terminology.
• No detailed explanations or procedures.
• No extended scenarios or examples.
• Avoid repeating entire lessons.

Scope Note: This is a short recap before the Module 2 assessment. Focus on reinforcing the major concepts rather than reteaching them.

C1M3 Reading: How Work Moves Through the System

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to hardware, operating systems, applications, networks, services, and infrastructure. In the preceding video, From User Action to System Response, they learned the five-step model: user action, request, processing, response, and outcome. The video demonstrated this sequence using an online shopping search.

Reading Objective: Explain how data moves between technology system components and how those components work together to complete tasks.

Content Outline

1. How Data Moves Through a Technology System

• Explain that completing a technology task often requires data to move between different system components.
• Reinforce that applications, devices, networks, services, and infrastructure work together to complete tasks.
• Briefly connect data movement to the five-step model introduced in the preceding video without repeating its definitions.
• Explain that data may move between components within a device or between multiple connected systems.

2. What Happens to Data Along the Way

• Explain that data may undergo different operations as it moves through a technology system:
  • Processed: Data is used to perform calculations, interpret information, or complete an operation.
  • Stored: Data is saved so it can be accessed or used again.
  • Transmitted: Data is sent between components or devices.
  • Returned: Data or results are sent back to the component or application that requested them.
• Emphasize that a single task may involve several of these operations.
• Use brief, familiar examples to illustrate each operation without introducing technical processes or protocols.

3. How System Components Depend on Each Other

• Explain that completing a task may require multiple components to contribute different functions.
• Describe the general roles of:
  • Devices: Provide the hardware used to interact with and perform computing tasks.
  • Applications: Allow users to initiate tasks and interact with information.
  • Networks: Enable data to move between connected devices and resources.
  • Services: Provide capabilities such as retrieving information, storing files, or processing requests.
  • Infrastructure: Provides the underlying equipment and systems that support networks and services.
• Emphasize that components are interconnected and depend on one another to complete certain tasks.
• Reinforce that not every task requires every component.

4. Following Data Through an Everyday Task

• Use a shared online document as an example of how data moves between system components.
• Briefly trace the movement of data:
  • A user opens a shared document through an application.
  • The application retrieves the document from a remote service through a network.
  • The device processes and displays the document.
  • As the user edits the document, the application processes the changes.
  • Updated data is transmitted to the remote service for storage.
  • The application displays the updated document.
• Identify where data is processed, stored, transmitted, and returned.
• Emphasize how multiple components contribute to what appears to be one simple user task.
• Avoid presenting the example as another detailed explanation of the five-step model.

5. Key Takeaways

• Data moves between technology system components as tasks are completed.
• Data may be processed, stored, transmitted, or returned during a task.
• Devices, applications, networks, services, and infrastructure contribute different functions.
• Many everyday technology tasks depend on multiple interconnected components working together.

Out of Scope Guardrails

• Repeating the detailed five-step model from the preceding video.
• Detailed explanations of processors, memory, storage, and operating system resource management covered in Module 2.
• Detailed explanations of local, cloud, and hybrid computing environments, which are covered in the Where the Work Happens reading.
• Detailed request and response terminology and interactions, which are covered in the Requests and Responses reading.
• Network protocols, packet transmission, routing, and addressing.
• Detailed cloud architecture, servers, and infrastructure configurations.
• Troubleshooting procedures, identifying failures, or diagnosing system problems.
• Introducing new technical workflows or models.

Scope Note: The preceding From User Action to System Response video introduces the five-step sequence of a technology task. This reading builds on that foundation by explaining how data moves between system components and what happens to that data along the way. Emphasize processing, storage, transmission, and returning data, along with the dependencies between devices, applications, networks, services, and infrastructure. Reserve detailed explanations of local, cloud, and hybrid environments for Where the Work Happens, and request and response interactions for Requests and Responses. Keep the content at the Remember and Understand level.

C1M3 Reading: Requests and Responses

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have been introduced to the five-step model of how technology systems complete tasks in the From User Action to System Response video. They have also explored how data moves between system components in the How Work Moves Through the System reading. In the preceding Where the Work Happens video, they learned how processing and storage can occur locally, remotely, or through a hybrid approach.

Reading Objective: Explain how applications and services exchange requests and responses to complete technology tasks.

Content Outline

1. Understanding Requests and Responses

• Explain that applications and services communicate by exchanging requests and responses.
• Briefly reinforce the definitions introduced in the From User Action to System Response video:
  • Request: A message asking another system component or service to perform an action.
  • Response: Information returned after the requested action has been processed.
• Emphasize that requests and responses allow different components to work together.
• Explain that these exchanges often happen automatically without the user seeing them.

2. How Applications Send Requests

• Explain that an application may need information or functionality provided by another component or service.
• Describe how an application creates a request that identifies the action or information needed.
• Introduce common purposes for requests:
  • Retrieving information.
  • Saving or updating information.
  • Asking another component or service to perform an operation.
• Explain that requests may be directed to local system components or remote services.
• Avoid introducing technical message formats or communication protocols.

3. How Services Process and Respond to Requests

• Explain that the receiving component or service interprets the request and performs the requested action.
• Describe how a response communicates the result back to the requesting application.
• Explain that responses may contain:
  • Requested information.
  • Confirmation that an action was completed.
  • An indication that the requested action could not be completed.
• Reinforce that the application uses the response to determine what information or result to present to the user.

4. Following a Request and Response Exchange

• Use a familiar example, such as checking the weather through a weather application.
• Trace the interaction:
  • The user opens the weather application and selects a location.
  • The application sends a request for weather information.
  • A remote weather service receives the request and retrieves the requested information.
  • The service sends a response containing the weather data.
  • The application uses the response to display the forecast.
• Emphasize the exchange between the application and service rather than repeating the entire five-step model.
• Briefly explain that similar exchanges support activities such as searching websites, checking account information, and retrieving shared files.

5. Key Takeaways

• Applications and services exchange requests and responses to complete tasks.
• A request asks another component or service to perform an action or provide information.
• A response communicates the result of the requested action.
• Requests and responses can occur between local components or across networks.
• Many everyday technology tasks depend on these exchanges happening behind the scenes.

Out of Scope Guardrails

• Repeating the complete five-step model from the From User Action to System Response video.
• Detailed explanations of local, cloud, and hybrid computing covered in the preceding video.
• Repeating how data is processed, stored, transmitted, or returned from the How Work Moves Through the System reading.
• Network protocols, including HTTP, HTTPS, TCP/IP, and packet structures.
• APIs, endpoints, request headers, response codes, and message formats.
• Detailed client-server architecture or communication mechanisms.
• Authentication and authorization workflows.
• Troubleshooting failed requests, interpreting error codes, or diagnosing connectivity problems.
• Programming examples or instructions for creating requests.

Scope Note: The From User Action to System Response video introduces requests and responses as two steps in a broader technology workflow. The How Work Moves Through the System reading explains how data moves between components, while Where the Work Happens distinguishes local, remote, and hybrid processing and storage. This reading focuses specifically on how applications and services communicate through requests and responses, what those messages accomplish, and how their exchange supports everyday technology tasks. Keep the explanation conceptual and at the Remember and Understand level.

C1M3 Reading: Signals That Something Went Wrong

Target Length: 400–550 words (maximum 700)

Prior Knowledge: Learners have explored how work moves through a technology system, including requests, processing, and responses. In the preceding How System Problems Affect Tasks video, they learned about expected versus actual behavior, symptoms, cascading effects, and how problems can originate at different levels of a system.

Reading Objective: Identify common signals of technology system problems and explain how those signals provide evidence of unexpected system behavior.

Content Outline

1. Recognizing Signals of a Problem

• Briefly reinforce that unexpected behavior can indicate something is not working as intended.
• Explain that technology systems provide different types of signals when problems occur.
• Introduce four common sources of evidence: error messages, warnings, hardware status lights, and logs.
• Emphasize that signals provide clues but do not necessarily identify the underlying cause.

2. Error Messages and Warnings

• Error messages: Notifications indicating that an operation failed or could not be completed.
  • Examples: File cannot be opened, application cannot connect, or access denied.
• Warnings: Notifications indicating a potential problem or condition requiring attention.
  • Examples: Low storage space, low battery, or an unstable connection.
• Explain that the wording and context of a message can help identify what happened.
• Distinguish between an operation that has failed and a warning about a potential problem.

3. Hardware Status Lights

• Explain that physical devices often communicate their operating status through indicator lights.
• Examples:
  • Power lights indicating whether a device is receiving power.
  • Network connection lights indicating connection or activity.
  • Printer status lights indicating normal operation or an error condition.
• Explain that light colors and patterns vary by device and manufacturer.
• Reinforce that status lights provide observable evidence about device conditions.

4. Logs as a Source of Information

• Define logs as records of events and activities generated by operating systems, applications, and devices.
• Explain that logs can record errors, warnings, and routine system events.
• Introduce basic information a log entry might contain:
  • Date and time
  • Event or activity
  • Status or error information
• Include a simple example of an application recording a failed connection attempt.
• Emphasize recognizing the purpose of logs rather than learning how to access or analyze them.

5. Unexpected Behavior as Evidence

• Explain that not every problem produces an error message or warning.
• Examples:
  • An application freezes or closes unexpectedly.
  • A device responds slowly.
  • A file does not save as expected.
  • A connected device stops responding.
• Reinforce the importance of recognizing and describing what is observed.
• Briefly distinguish the observed signal from the underlying cause.

6. Key Takeaways

• Technology systems communicate problems through messages, warnings, indicator lights, logs, and unexpected behavior.
• Different signals provide different types of evidence.
• A signal indicates what was observed but does not always reveal the cause.
• Recognizing these signals helps IT professionals understand and communicate system problems.

Out of Scope Guardrails

• Repeating the detailed discussion of system interruptions, cascading effects, and scope from the preceding video.
• Diagnosing root causes or determining which component has failed.
• Step-by-step troubleshooting procedures.
• Using operating system log viewers or command-line tools.
• Interpreting detailed log entries, error codes, or diagnostic reports.
• Manufacturer-specific hardware indicator patterns.
• Resolving errors, changing configurations, or repairing devices.
• Advanced system monitoring and performance analysis.

Scope Note: The preceding How System Problems Affect Tasks video establishes how interruptions affect technology systems and why symptoms may appear somewhere other than the underlying problem. This reading focuses specifically on recognizing the signals that indicate something went wrong. The Skills and Knowledge document identifies error messages, warnings, hardware status lights, logs, and unexpected behavior as the required content. Keep the emphasis on identifying and understanding these signals rather than diagnosing or resolving problems.

C1M3 Reading: Module 3 Review

Target Length: 200–300 words

Reading Objective: Summarize how technology systems process user requests and recognize how system problems affect tasks.

Content Outline

1. Module Overview

• Briefly reinforce how technology systems work together to complete user tasks.
• Connect the movement of work through a system to recognizing when something goes wrong.

2. Module Key Concepts

• System workflow: User action → Request → Processing → Response → Outcome.
• Requests and responses: How applications and system components communicate to complete tasks.
• Where work happens: Local processing and storage, remote processing and storage, and hybrid approaches.
• System interruptions: How expected behavior can differ from actual behavior.
• Symptoms and scope: How problems can affect different components and different numbers of users.
• Signals of problems: Error messages, warnings, hardware status lights, logs, and unexpected behavior.

3. Connecting the Concepts

• Use a brief example of a user attempting to access a shared online document.
• Reinforce how the request travels through the system, where processing occurs, and what the expected outcome looks like.
• Explain that an unexpected result provides evidence of a possible interruption.

4. Final Takeaways

• Everyday technology tasks depend on multiple connected components.
• Processing and storage can occur locally, remotely, or through a combination of both.
• System problems can produce symptoms in components other than where the problem originated.
• Recognizing observable evidence helps IT professionals understand system behavior.

Out of Scope Guardrails

• Introducing new terminology or concepts.
• Repeating detailed explanations from individual lessons.
• Step-by-step troubleshooting or problem resolution.
• New technical examples requiring additional instruction.

Scope Note: This is a short review of the concepts introduced throughout Module 3, not a new instructional reading. Focus on reinforcing the relationships between system workflows, processing locations, requests and responses, and observable problems.

C1M4 Reading: AI Foundations for the Modern Workplace

Target Length: Maintain existing reading length.

Prior Knowledge: Learners have explored foundational technology systems, including hardware, software, processing, storage, and system interactions. They have also examined how system problems affect user tasks.

Reading Objective: Describe how AI can support IT professionals in everyday workplace tasks while recognizing the importance of human judgment.

Content Outline

1. Introduction to AI in the Modern Workplace

• Keep existing content as written.
• No revisions needed.

2. Use AI as a Collaborative Assistant

• Keep the existing definition of AI and explanation of AI as a digital assistant.
• Replace the highlighted data analytics example with examples relevant to IT support:
  • Summarizing a lengthy support ticket.
  • Explaining an unfamiliar technical error or concept.
  • Drafting clear instructions for a user.
• Preserve the original emphasis on AI helping professionals work more efficiently.

3. How You’ll Work with AI in This Program

• Keep the existing introduction and learning outcomes.
• Replace the highlighted reference to data analytics with:
  • How generative AI tools can support everyday IT and network support tasks.
• Leave the remaining learning outcomes unchanged.

4. Your Unique Skills, Enhanced by AI

• Keep the existing discussion of human judgment, creativity, ethical decision-making, and accountability.
• Replace the highlighted project management reference with an IT support example.
• Explain how AI can assist with routine documentation and communication, allowing IT professionals to focus on:
  • Understanding user needs.
  • Evaluating technical information.
  • Making informed decisions.
• Preserve the existing message that humans remain responsible for oversight and decisions.

5. No Tech Background Needed

• Keep existing content as written.
• No revisions needed.

Out of Scope Guardrails

• Do not rewrite or restructure sections that are not highlighted.
• Do not add new sections or expand the reading.
• Do not introduce additional technical explanations of AI, machine learning, training data, or generative AI.
• Do not duplicate foundational concepts covered in the following Learn Foundational AI Concepts video.
• Do not introduce detailed troubleshooting procedures or advanced AI applications.

Scope Note: This is a targeted adaptation of an existing reading, not a new reading. The writer should preserve the original structure, tone, and content, modifying only the three yellow-highlighted passages to replace data analytics and project management references with relevant IT and network support examples. All unhighlighted content should remain unchanged.

C1M4 Reading: Prompting Best Practices

Target Length: Maintain existing reading length.

Prior Knowledge: Learners have been introduced to foundational AI concepts, AI capabilities, and communicating and collaborating with AI tools.

Reading Objective: Apply prompting best practices to construct clear and effective prompts for introductory IT workplace tasks.

Content Outline

Retain the existing reading’s structure, explanations, and prompting techniques.

1. A Simple Prompting Framework

• Keep the existing persona, task, format, and context framework.
• Replace the client welcome email example with an IT support scenario.
• Suggested example: Draft an email explaining how a new employee can connect to workplace Wi-Fi.
• Demonstrate the four prompting elements using this example.

2. Providing Examples and Multimodal Inputs

• Retain the existing explanations of few-shot prompting and multimodal capabilities.
• Replace the weekly stakeholder update example with a fictional IT support ticket summary.
• Replace the conference flyer example with a fictional application error screenshot.

3. Refining Prompts

• Retain the existing prompting refinement techniques.
• Replace the general project planning example with an IT-related example, such as explaining how a computer connects to a website.
• Emphasize refining the prompt for clarity, audience, and format.

4. Reviewing AI Responses

• Retain the existing human-in-the-loop guidance.
• Reinforce verifying technical information against trusted sources.
• Include a brief reminder not to share sensitive organizational or personal information with unapproved AI tools.

5. Organizing Conversations

• Retain the existing guidance on context windows, chat organization, and reusable prompts.
• No significant changes needed.

Out of Scope Guardrails

• Do not rewrite the existing reading or introduce additional prompting frameworks.
• Avoid repeating foundational AI concepts from preceding videos.
• Do not introduce detailed IT troubleshooting procedures.
• Avoid platform-specific instructions for Gemini or other AI tools.
• Keep examples appropriate for learners with introductory IT knowledge.

Scope Note: This is a targeted revision of an existing reading. Preserve the instructional content and organization, replacing general workplace examples with introductory IT scenarios. The primary goal is to make the prompting examples relevant to the certificate without expanding the reading or introducing new technical skills.

C1M4 Reading: Introduction to AI in IT Support

Target Length: 350–500 words (maximum 600)

Prior Knowledge: Learners have explored foundational AI concepts, AI capabilities, prompting best practices, responsible AI use, and common generative AI tools. They understand that AI can assist with workplace tasks but that human judgment and verification remain essential.

Reading Objective: Identify common ways AI can assist IT support professionals with everyday tasks and explain the limitations of AI-generated technical information.

Content Outline

1. Introduction to AI in IT Support

• Retain the existing introduction describing how AI can help IT support professionals work more efficiently.
• Remove the repeated definition of artificial intelligence.
• Explain that AI can support common IT responsibilities by helping professionals find information, communicate with users, and organize technical details.
• Update the lesson introduction to focus on practical applications of AI in IT support rather than foundational AI concepts.

2. Using AI in Everyday IT Support Work

Replace the existing Support and Maintain AI Systems section with an overview of common applications.

• Researching technical information: AI can help explain unfamiliar terminology, clarify concepts, and summarize technical documentation.
• Supporting user communication: AI can help draft responses to common questions and explain technical information in plain language.
• Organizing support information: AI can summarize fictional support notes, organize issue descriptions, and help prepare documentation.
• Assisting with troubleshooting: AI can suggest possible explanations for symptoms or questions to investigate, which IT professionals must verify before acting.
• Supporting routine tasks: AI can help organize information and prepare drafts for repetitive administrative activities.
• Include brief, familiar IT support examples without introducing detailed technical procedures.

3. Understanding AI’s Role and Limitations

• Explain that AI-generated suggestions may be inaccurate, incomplete, or inappropriate for a particular technical environment.
• Reinforce that IT professionals must verify technical information using trusted documentation and organizational procedures.
• Emphasize that AI supports human decision-making rather than replacing professional judgment.
• Keep this section brief because responsible AI practices have already been covered in Lesson 1.

4. Key Takeaways

• AI can assist IT support professionals with research, communication, documentation, and preliminary troubleshooting.
• AI can help make technical information easier to understand and organize.
• AI-generated information requires human review and verification.
• IT professionals remain responsible for the decisions and actions taken when using AI.

Out of Scope Guardrails

• Repeating foundational AI definitions, capabilities, or prompting techniques covered in Lessons 1 and 2.
• Maintaining AI models, training data, or AI infrastructure.
• Designing, deploying, or integrating AI systems into enterprise environments.
• Implementing cybersecurity defenses for AI systems.
• Detailed troubleshooting procedures, diagnostic commands, or technical problem resolution.
• Advanced AI automation or autonomous IT support workflows.
• Extended discussions of responsible AI practices already covered in Lesson 1.
• Detailed demonstrations of specific AI tools.

Scope Note: This reading introduces practical applications of AI within entry-level IT support work. Retain the existing introduction where appropriate, but replace the Support and Maintain AI Systems section with examples of how IT professionals use AI to assist with everyday responsibilities. The focus should be on recognizing appropriate applications and understanding limitations, not maintaining AI infrastructure or performing technical troubleshooting. Subsequent Lesson 3 assets explore specific applications of AI in IT support, so keep this reading introductory and avoid duplicating those examples in detail.

C2M2 Reading: Operating Systems Review

Asset Type: New reading
Lesson: C2M2 Lesson 1: OS Interfaces
Target Length: 400–500 words

Purpose

Refresh learners’ understanding of operating systems and establish how IT support professionals interact with them to access information, manage devices, and investigate issues.

This reading should build on Course 1’s introduction to operating systems rather than repeat the foundational explanation.

Content Outline

1. Introduction: Operating Systems in IT Support

• Briefly review the role of an operating system in managing hardware, applications, files, settings, and user interactions.
• Explain why IT support professionals need to understand how to navigate operating systems.
• Introduce the idea that operating systems provide tools for viewing information, changing settings, and monitoring device behavior.

2. Common Operating Systems

Briefly revisit the operating systems learners may encounter:

• Windows: Common on workplace desktops and laptops.
• macOS: Used on Apple desktop and laptop computers.
• Linux: Used on desktops, servers, and other technology systems.
• ChromeOS: Used on Chromebooks and other supported devices.
• Mobile operating systems: Android and iOS on smartphones and tablets.

Emphasize that these systems may have different interfaces and tools, but they perform many similar functions.

Avoid detailed comparisons of features, versions, or administrative procedures.

3. Working with an Operating System

Introduce common tasks IT support professionals perform through operating systems:

• View device and system information.
• Access files and folders.
• Review running applications and processes.
• Check system performance.
• View and adjust settings.
• Locate error messages and system information.

Use one or two simple workplace examples, such as checking why a device is running slowly or locating information about its operating system.

Do not explain how to perform these tasks yet.

4. How IT Professionals Interact with Operating Systems

Introduce the two primary ways professionals interact with operating systems:

• Graphical user interface (GUI): Interact through windows, menus, icons, and other visual controls.
• Command-line interface (CLI): Interact by entering text commands.

Explain that both approaches can be used to access system information and perform administrative tasks.

Keep this section brief because the following assets cover GUI and CLI concepts in greater detail.

5. Key Takeaways

• Operating systems manage essential device resources and provide ways to interact with them.
• IT support professionals use operating system tools to access information and support users.
• Different operating systems provide similar capabilities through different tools and interfaces.
• Understanding GUI and CLI interactions prepares professionals to work across operating systems.

Out of Scope

• Detailed operating system architecture.
• Installation, configuration, or updating procedures.
• Specific GUI navigation instructions.
• Command syntax or demonstrations.
• Troubleshooting procedures.
• Detailed performance analysis.
• Operating system version comparisons.

Writer Guidance: Keep this reading introductory and focused on practical relevance. Learners should understand why operating system interfaces and tools matter before encountering the individual GUI tools, command-line commands, and activities later in the module.

C2M2 Reading: The Command Line in Use

Asset Type: Existing reading requiring edits
Target Length: 400–500 words
Lesson: C2M2 Lesson 1: OS Interfaces

Purpose

Compare GUI and CLI interfaces, emphasizing command-line efficiency and command history in IT support.

Content Outline

1. Introduction (40–50 words)

• Briefly connect to the preceding GUI versus CLI video.
• Replace cybersecurity references with IT support.

2. CLI vs. GUI (90–110 words)

Display

• Retain the visual comparison and brief explanation of each interface.
• Avoid repeating definitions from the video.

Function

• Correct the inaccurate claim that GUIs only perform one task at a time.
• Explain that both interfaces support similar tasks, but CLI tools can simplify repetitive operations.

3. Advantages of a CLI in IT Support

Efficiency (110–130 words)

• Compare when GUI or CLI tools may be more efficient.
• Retain the multiple-file example, adapting it to IT support.
• Emphasize efficiency for repetitive tasks and accessing system information.

History File (110–130 words)

• Explain how command history helps technicians review and repeat commands.
• Replace cybersecurity incident examples with an IT support scenario involving reviewing system information.
• Clarify that command history depends on shell configuration and is not a complete activity record.

4. Key Takeaways (40–60 words)

• Both GUI and CLI tools are useful in IT support.
• CLI tools offer advantages for repetitive tasks and command history.
• The appropriate interface depends on the task.

Out of Scope

Specific commands, scripting, advanced troubleshooting, and security incident response.

Writer Guidance: Preserve the existing structure and visuals. Prioritize command-line efficiency and history, correct technical inaccuracies, and use IT support examples. Avoid duplicating the preceding video.

C2M2 Reading: Windows GUI Tools

Asset Type: New reading
Target Length: 500–600 words
Lesson: C2M2 Lesson 2: GUI Tools

Purpose

Introduce common Windows graphical tools used by IT support professionals to locate system information, monitor performance, and investigate device issues.

Content Outline

1. Introduction (50–60 words)

• Explain how Windows GUI tools help technicians access device information and identify potential issues.
• Connect to the GUI concepts introduced in Lesson 1.

2. Common Windows GUI Tools (350–400 words)

Introduce each tool, its purpose, and a practical IT support example.

Windows Settings

• View and manage device, system, and network settings.
• Example: Check a device’s network connection or display settings.

File Explorer

• Navigate files, folders, and storage locations.
• Example: Locate a downloaded file or check available storage.

Task Manager

• View running applications, processes, and resource usage.
• Example: Identify an application consuming excessive CPU or memory.

System Information

• View hardware specifications, operating system details, and system components.
• Example: Confirm device specifications when reviewing software requirements.

Event Viewer

• Access Windows system, application, and security event logs.
• Example: Locate error events associated with an application failure.

3. Choosing the Appropriate Tool (70–90 words)

• Explain that the tool selected depends on the information needed.
• Provide a brief comparison of which tool to use for common support situations.
• Emphasize gathering evidence before making changes.

4. Key Takeaways (40–50 words)

• Windows provides GUI tools for accessing system information and investigating issues.
• Different tools provide different types of information.
• Familiarity with these tools helps technicians gather useful evidence.

Out of Scope

Detailed troubleshooting procedures, advanced configuration, administrative changes, PowerShell commands, and log analysis.

Writer Guidance: Include screenshots or labeled interface examples where helpful. Focus on locating tools, understanding their purpose, and recognizing the information they provide. Keep instructions introductory and avoid version-specific navigation where possible. The following activity will give learners practice using these tools.

C2M2 Reading: macOS GUI Tools

Asset Type: New reading
Target Length: 500–600 words
Lesson: C2M2 Lesson 2: GUI Tools

Purpose

Introduce common macOS graphical tools used by IT support professionals to access system information, monitor performance, manage files, and investigate device issues.

Content Outline

1. Introduction (40–50 words)

• Explain how macOS GUI tools support common IT tasks.
• Connect to the Windows GUI tools reading, noting that different operating systems provide similar capabilities through different interfaces.

2. Common macOS GUI Tools (350–400 words)

Introduce each tool, its purpose, and a practical IT support example.

System Settings

• View and manage device, network, privacy, and user settings.
• Example: Check Wi-Fi connection settings.

Finder

• Navigate files, folders, and storage locations.
• Example: Locate a downloaded file or navigate to a shared folder.

Activity Monitor

• View running processes and CPU, memory, disk, and network activity.
• Example: Identify an application consuming excessive memory.

System Information

• View hardware specifications, software details, and connected devices.
• Example: Confirm hardware specifications before installing software.

Disk Utility

• View storage devices, partitions, and disk information.
• Example: Check whether an external storage device is recognized.

Console

• Access system and application logs.
• Example: Locate error messages associated with an application issue.

3. Choosing the Appropriate Tool (60–80 words)

• Match common IT support situations to the appropriate macOS tool.
• Reinforce the importance of gathering information before making changes.
• Briefly connect equivalent tools across Windows and macOS.

4. Key Takeaways (40–50 words)

• macOS provides GUI tools for managing devices and gathering system information.
• Different tools provide different types of evidence.
• Many macOS tools serve purposes similar to Windows tools, even when their interfaces differ.

Out of Scope

Advanced configuration, detailed troubleshooting procedures, disk repair operations, log analysis, and command-line tools.

Writer Guidance: Include screenshots or labeled interface examples where helpful. Focus on tool purpose, basic navigation, and recognizing useful information. Avoid version-specific instructions where possible. Detailed performance analysis and log interpretation will be covered later in Course 2.

C2M2 Reading: ChromeOS Tools

Asset Type: New reading
Target Length: 400–500 words
Lesson: C2M2 Lesson 2: GUI Tools

Purpose

Introduce common ChromeOS tools used by IT support professionals to view system information, monitor performance, and gather evidence about device issues.

Content Outline

1. Introduction (40–50 words)

• Briefly introduce ChromeOS as an operating system commonly used on Chromebooks.
• Explain how its built-in tools help technicians investigate device issues.
• Connect to the Windows and macOS GUI tools readings.

2. Common ChromeOS Tools (280–330 words)

Introduce each tool, its purpose, and a practical IT support example.

Diagnostics App

• View device health information, including battery, CPU, and memory.
• Run available diagnostic tests.
• Example: Check battery health when a user reports poor battery life.

Task Manager

• View running processes and their resource usage.
• Identify applications or browser processes consuming excessive resources.
• Example: Investigate a Chromebook running slowly.

Internal Chrome URLs

• Introduce internal diagnostic pages accessed through addresses beginning with chrome://.
• Explain that these pages can provide additional system, browser, and diagnostic information.
• Examples: chrome://system for system information and chrome://device-log for device-related events.
• Note that available pages and information can vary by ChromeOS version and device.

3. Choosing the Appropriate Tool (50–70 words)

• Match common device issues to the appropriate ChromeOS tool.
• Distinguish between checking device health, reviewing running processes, and accessing additional system information.
• Reinforce gathering evidence before making changes.

4. Key Takeaways (30–50 words)

• ChromeOS provides built-in tools for investigating device issues.
• Diagnostics, Task Manager, and internal Chrome pages provide different types of information.
• Understanding these tools helps technicians support ChromeOS devices.

Out of Scope

Advanced ChromeOS administration, Google Admin Console, detailed log analysis, command-line tools, and complex troubleshooting procedures.

Writer Guidance: Focus on the three tools identified in the Skills and Knowledge document: Diagnostics app, Task Manager, and internal Chrome URLs. Include screenshots where helpful. Keep examples practical and introductory, with emphasis on identifying and interpreting basic system information. Avoid detailed troubleshooting procedures covered later in Course 2.

C2M2 Reading: Linux Shell Syntax and Commands

Asset Type: New reading
Target Length: 700–800 words
Lesson: C2M2 Lesson 3: Command Line Tools

Purpose

Introduce Linux shell syntax and common commands used by IT support professionals to navigate files, access system information, and perform basic administrative tasks. Demonstrate how AI can assist with understanding commands while emphasizing verification and safe execution.

Content Outline

1. Introduction (50–60 words)

• Explain the role of the Linux shell and Bash.
• Connect to the GUI versus CLI concepts introduced earlier.
• Introduce shell commands and scripts as tools for everyday IT support tasks.

2. Understanding Linux Command Syntax (150–180 words)

• Explain the basic command structure: command, options, and arguments.
• Introduce absolute and relative paths.
• Explain shortcut symbols (~, ., ..) and wildcards (*).
• Introduce sudo and elevated permissions, emphasizing authorized use.

3. Common Linux Commands (180–210 words)

• File navigation and inspection: pwd, ls, cd, cat.
• Help and documentation: man, –help.
• File management: Introduce cp, mv, and mkdir.
• Package management: Briefly explain how Linux package managers install and update software.
• Include simple command examples with explanations of their output.

4. Combining Commands and Basic Automation (120–150 words)

• Introduce pipes (|) and input/output redirection (>, >>).
• Explain how commands can work together to process information.
• Introduce shell scripts as saved sequences of commands used for repetitive tasks.
• Provide a simple IT support example, such as saving system information to a text file.

5. System Performance and Support Tools (100–120 words)

Briefly introduce the purpose of:

• htop and btop: Monitor processes and resource usage.
• ncdu: Explore disk usage.
• fwupd: Manage supported device firmware updates.

Emphasize recognizing tool purposes rather than performing advanced maintenance.

6. Using AI to Understand Linux Commands (60–80 words)

• Explain how AI can help identify commands for common IT support tasks.
• Demonstrate using AI to explain command syntax, options, and expected output.
• Emphasize verifying AI suggestions against command documentation before execution.
• Reinforce caution with commands that modify files, change settings, or require elevated permissions.

Example AI Prompt:

“Explain what ls -la does in Linux, including what each option means. Does this command change anything on the system?”

7. Key Takeaways (40–50 words)

• Linux shell commands provide a text-based way to interact with an operating system.
• Syntax, paths, and permissions affect how commands operate.
• Commands can be combined or placed in scripts to support routine tasks.
• AI can help explain commands, but suggestions must be verified before execution.

Out of Scope

Advanced Bash scripting, complex package management, firmware updates, network diagnostics, detailed troubleshooting, and Linux system administration.

Writer Guidance: Align with the Skills and Knowledge document’s requirements for Bash, command syntax, paths, shortcuts, wildcards, elevation, pipes, redirection, file manipulation, package management, and basic performance tools. Include short, accurate command examples with expected results. Integrate AI as a support resource, not a replacement for understanding command syntax. Keep the emphasis on introductory Linux skills that learners can apply in the following Linux shell activity.

C2M2 Reading: PowerShell Syntax and Commands

Asset Type: New reading
Target Length: 700–800 words
Lesson: C2M2 Lesson 3: Command Line Tools

Purpose

Introduce PowerShell syntax and common commands used by IT support professionals to gather Windows system information, manage processes, and perform basic administrative tasks. Demonstrate how AI can assist with understanding cmdlets while emphasizing verification and safe execution.

Content Outline

1. Introduction (50–60 words)

• Explain PowerShell’s role in Windows administration and IT support.
• Connect to the Linux shell reading, highlighting similarities and differences.

2. Understanding PowerShell Syntax (150–180 words)

• Introduce cmdlets and the Verb-Noun naming convention.
• Explain basic command structure, parameters, and arguments.
• Introduce variables and the PowerShell pipeline (|).
• Explain how Get-Help provides command documentation.

3. Common PowerShell Commands (180–210 words)

Introduce basic cmdlets with short examples:

• System information: Get-ComputerInfo
• Processes: Get-Process, Stop-Process
• Services: Get-Service, Start-Service, Stop-Service
• Software queries: Introduce how PowerShell can retrieve information about installed software.
• User management: Introduce cmdlets for viewing local user accounts.

Emphasize interpreting information before making system changes.

4. PowerShell for IT Support Tasks (120–150 words)

• Explain how PowerShell supports routine system administration.
• Introduce remote management at a conceptual level.
• Describe how commands can support automated diagnostic checks.
• Provide a simple example of using PowerShell to identify a process that is not responding.

5. System Performance and Troubleshooting (100–120 words)

• Explain how PowerShell can retrieve information about running processes, services, and system resources.
• Introduce the use of command output as evidence when investigating device issues.
• Reinforce safe execution and appropriate permissions.

6. Using AI to Understand PowerShell Commands (60–80 words)

• Explain how AI can suggest PowerShell cmdlets for common IT support tasks.
• Demonstrate using AI to explain command syntax, parameters, and expected output.
• Emphasize verifying AI-generated suggestions using Get-Help or official documentation.
• Reinforce caution with commands that modify system settings, stop processes, or require elevated permissions.
• Avoid sharing sensitive system or user information with AI tools.

Example AI Prompt:

“I need to identify which processes are using the most CPU on a Windows computer. What PowerShell cmdlet could help, and how would I interpret the results?”

7. Key Takeaways (40–50 words)

• PowerShell provides command-line tools for Windows administration.
• Cmdlets use a consistent Verb-Noun naming structure.
• Parameters, variables, and pipelines extend command functionality.
• AI can help explain commands, but suggestions must be verified before execution.

Out of Scope

Advanced scripting, complex automation, detailed remote administration, enterprise user management, and advanced troubleshooting.

Writer Guidance: Align with the Skills and Knowledge document’s requirements for PowerShell syntax, pipelines, variables, remote management, system administration, software queries, user management, and automated diagnostic checks. Include short command examples with expected results. Integrate AI as a support resource, not a replacement for understanding PowerShell commands. Keep the emphasis on introductory Windows support skills that learners can apply in the following PowerShell activity.

C2M2 Reading: Command Line Troubleshooting Tools

Asset Type: Existing reading requiring substantial revision
Target Length: 600–700 words
Lesson: C2M2 Lesson 3: Command Line Tools

Purpose

Introduce common Linux and Windows command-line troubleshooting tools used by IT support professionals to gather diagnostic information, investigate system issues, and identify potential causes. Demonstrate how AI can help interpret command output and suggest additional diagnostic checks.

Content Outline

1. Introduction (50–60 words)

• Retain the existing explanation of how command-line tools support troubleshooting.
• Explain how commands help technicians gather evidence about network connectivity, system performance, and device issues.
• Retain the downloadable Command Line Troubleshooting Tools Reference Guide as a supplemental resource.

2. Linux Troubleshooting Commands (180–210 words)

Introduce each command, its purpose, and a practical IT support example.

Network Connectivity

• ping: Test network reachability.
• ip a / ip address show: View network interface and IP address information.

System Logs

• journalctl -xe: Review recent system journal entries for errors and other diagnostic information.

Disk Space

• df -h: View filesystem disk usage and available space.

Include brief examples of the information these commands provide.

3. Windows PowerShell Troubleshooting Commands (180–210 words)

Introduce each command, its purpose, and a practical IT support example.

Network Connectivity

• Test-NetConnection: Test network connectivity and specific port availability.

Services and Processes

• Get-Service: View Windows service information.
• Stop-Service / Start-Service: Stop or start a service.
• Get-Process: View running processes.

System Information

• Get-ComputerInfo: Retrieve Windows operating system and computer information.

Explain the difference between commands that retrieve information and commands that change system behavior.

4. Comparing Linux and Windows Commands (60–80 words)

• Compare commands that serve similar purposes across operating systems.
• Emphasize that command names and output differ, but technicians often investigate similar information.
• Reinforce selecting commands based on the operating system and reported issue.

5. Using AI to Interpret Command Output (80–100 words)

• Explain how AI can help interpret unfamiliar command output.
• Demonstrate asking AI what diagnostic results might indicate.
• Introduce using AI to suggest reasonable next checks.
• Emphasize verifying AI interpretations rather than treating them as confirmed diagnoses.
• Remind learners to remove sensitive system and user information before sharing output with AI tools.

Example AI Prompt:

“A Linux computer is running out of storage. The df -h command shows that the root filesystem is 95% full. Explain what this means and suggest two safe diagnostic checks I could perform next. Do not recommend deleting files or changing system settings.”

6. Key Takeaways (40–50 words)

• Command-line tools provide useful diagnostic information.
• Linux and Windows offer different commands for similar troubleshooting tasks.
• Gathering and interpreting evidence helps technicians identify potential issues.
• AI can support interpretation, but technicians must verify its recommendations.

Out of Scope

Advanced troubleshooting procedures, network configuration changes, detailed log analysis, scripting, automated remediation, and complex system administration.

Writer Guidance: Preserve the existing introductory concept and link to the Command Line Troubleshooting Tools Reference Guide. Focus the revised reading on the Linux and Windows commands identified in the Skills and Knowledge document. Include brief examples of command output where helpful. Avoid repeating syntax instruction from the preceding Linux and PowerShell readings. Integrate AI as a tool for interpreting diagnostic evidence, not automatically resolving problems.

C2M2 Reading: iOS Tools

Asset Type: New reading
Target Length: 450–550 words
Lesson: C2M2 Lesson 4: Mobile OSs

Purpose

Introduce built-in iOS tools that IT support professionals can use to locate device information, review settings, monitor basic device health, and gather information about common mobile device issues.

Content Outline

1. Introduction (40–50 words)

• Explain how IT support professionals use built-in iOS tools to support iPhones.
• Connect mobile operating system tools to the Windows, macOS, and ChromeOS tools introduced earlier.
• Emphasize gathering information before making changes.

2. Common iOS Tools and Settings (300–350 words)

Introduce each tool or settings area, its purpose, and a practical IT support example.

General Settings

• Locate device information, including iOS version, model, and available storage.
• Review software update information.
• Example: Check whether an iPhone meets an application’s system requirements.

Wi-Fi and Cellular Settings

• View network connections and connectivity settings.
• Example: Confirm whether a device is connected to the expected Wi-Fi network.

Privacy & Security

• Review application permissions and privacy settings.
• Explain how permissions affect access to features such as the camera, microphone, and location.
• Example: Check permissions when an application cannot access the camera.

Battery Settings

• Review battery usage and available battery health information.
• Example: Identify applications contributing to excessive battery consumption.

App Settings

• Locate application-specific settings and permissions.
• Example: Review notification settings when a user reports missing alerts.

3. Choosing the Appropriate Tool (60–80 words)

• Match common mobile support issues to the relevant settings area.
• Explain how reviewing settings can help narrow down a reported problem.
• Reinforce that technicians should avoid changing settings without understanding their impact.

4. Key Takeaways (40–50 words)

• iOS provides built-in tools for accessing device information and reviewing system settings.
• Different settings areas help investigate connectivity, application, battery, and permission issues.
• Gathering accurate device information is an important first step in mobile support.

Out of Scope

Advanced mobile device management (MDM), device enrollment, factory resets, detailed troubleshooting procedures, mobile security administration, and third-party diagnostic applications.

Writer Guidance: Focus on the built-in iOS Settings app and its practical use in entry-level IT support. Include screenshots where helpful, but avoid relying on navigation paths that may change between iOS versions. Keep examples introductory and emphasize locating information rather than changing configurations.

C2M2 Reading: Android Tools

Asset Type: New reading
Target Length: 450–550 words
Lesson: C2M2 Lesson 4: Mobile OSs

Purpose

Introduce built-in Android tools that IT support professionals can use to locate device information, review settings, monitor basic device performance, and gather information about common mobile device issues.

Content Outline

1. Introduction (40–50 words)

• Explain how IT support professionals use built-in Android tools to support smartphones and tablets.
• Connect to the preceding iOS Tools reading.
• Note that Android interfaces and available tools can vary by device manufacturer and Android version.

2. Common Android Tools and Settings (300–350 words)

Introduce each tool or settings area, its purpose, and a practical IT support example.

About Phone / About Device

• Locate device model, Android version, and other system information.
• Review available software update information.
• Example: Verify device information before installing an application.

Network & Internet Settings

• View Wi-Fi, mobile network, and connectivity settings.
• Example: Confirm whether a device is connected to the expected Wi-Fi network.

Apps and Permissions

• View installed applications and manage app permissions.
• Review application storage and notification settings.
• Example: Check permissions when an application cannot access the microphone.

Battery Settings

• Review battery usage and available battery information.
• Identify applications consuming significant battery resources.
• Example: Investigate a report of unusually rapid battery drain.

Storage Settings

• View available storage and categories of stored data.
• Example: Check available space when a user cannot install an application.

3. Choosing the Appropriate Tool (60–80 words)

• Match common Android support issues to the appropriate settings area.
• Explain how reviewing device information can help narrow down a reported issue.
• Reinforce gathering information before changing settings.

4. Key Takeaways (40–50 words)

• Android provides built-in tools for reviewing device information, connectivity, applications, battery usage, and storage.
• Android settings and interfaces can vary across devices.
• Understanding these tools helps technicians gather evidence and support mobile users.

Out of Scope

Advanced Android debugging, developer options, Android Debug Bridge (ADB), rooting, factory resets, enterprise mobile device management, and detailed troubleshooting procedures.

Writer Guidance: Focus on built-in Android settings and their practical use in entry-level IT support. Include screenshots where helpful, but acknowledge manufacturer differences rather than relying on one device’s navigation paths. Maintain a structure and level of detail consistent with the iOS Tools reading. Emphasize locating and interpreting information rather than changing configurations.

C2M2 Reading: Module 2 Review

Target Length: 200–300 words

Reading Objective: Summarize how operating system tools provide system information and identify appropriate tools for common IT support tasks.

Content Outline

1. Module Overview

• Briefly reinforce how IT professionals use operating system tools to gather information and investigate device issues.
• Connect GUI and CLI tools to common IT support responsibilities across different operating systems.

2. Module Key Concepts

• Operating system interfaces: GUI and CLI approaches to interacting with operating systems.
• Windows GUI tools: Settings, File Explorer, Task Manager, System Information, and Event Viewer.
• macOS GUI tools: System Settings, Finder, Activity Monitor, System Information, Disk Utility, and Console.
• ChromeOS tools: Diagnostics, Task Manager, and internal Chrome URLs.
• Linux commands: Basic command syntax, file navigation, system information, and administrative tasks.
• PowerShell commands: Cmdlets, parameters, pipelines, and basic Windows administration.
• Command-line troubleshooting: Using commands to gather information about connectivity, processes, services, logs, and disk usage.
• Mobile operating systems: Built-in iOS and Android tools for reviewing device information, settings, permissions, and performance.
• AI-assisted support: Using AI to explain commands and interpret diagnostic information while verifying its suggestions.

3. Connecting the Concepts

• Use a brief example of a user reporting that their computer is running slowly.
• Reinforce how a technician might select an appropriate GUI or CLI tool based on the operating system.
• Explain how the information gathered can help identify potential causes.
• Connect AI to interpreting unfamiliar command output while emphasizing verification.

4. Final Takeaways

• Different operating systems provide tools for accessing similar types of system information.
• GUI and CLI tools support different approaches to completing IT tasks.
• Selecting appropriate tools and interpreting their output helps technicians investigate reported issues.
• AI can assist with understanding technical information, but technicians must verify its recommendations.

Out of Scope Guardrails

• Introducing new tools, commands, or terminology.
• Repeating detailed instructions from individual lessons.
• Step-by-step troubleshooting or problem resolution.
• Advanced system administration or configuration changes.
• New technical examples requiring additional instruction.

Scope Note: This is a short review of the concepts introduced throughout Module 2, not a new instructional reading. Focus on reinforcing the relationships between operating system interfaces, available tools, system information, and practical IT support tasks.

C3M1 Reading: Anatomy of a Connected System

Asset Type: New reading
Target Length: 650–750 words
Lesson: C3M1 Lesson 1: Connected Systems Thinking

Purpose

Explain the three primary components of a connected system: endpoints, network infrastructure, and centralized services. Introduce common network devices and demonstrate how information moves through a connected environment using network traffic, gateway routing, and request and response communication.

Content Outline

1. Introduction: Understanding Connected Systems (50–60 words)

• Build on the Connected Systems video by explaining that connected environments consist of multiple components working together.
• Introduce the three primary components: endpoints, network infrastructure, and centralized services.
• Explain that understanding these components helps IT support professionals recognize how devices access shared resources.

2. The Three Components of a Connected System (150–170 words)

Endpoints

• Define endpoints as devices that connect to a network.
• Provide examples: laptops, smartphones, desktop computers, and printers.

Network Infrastructure

• Explain that network infrastructure provides the physical and wireless connections that enable communication.
• Introduce the role of network hardware in connecting endpoints to other devices and services.

Centralized Services

• Define centralized services as resources accessed by multiple users or devices.
• Provide examples: shared file storage, application servers, databases, and cloud services.
• Explain that centralized services may be hosted locally or remotely.

3. Common Network Devices and Their Roles (140–160 words)

Introduce each device with a simple definition and its primary purpose.

• Switch: Connects devices within a local network.
• Router: Connects different networks and forwards data between them.
• Modem: Provides an interface between a local network and certain types of internet service connections.
• Firewall: Controls network traffic according to defined security rules.
• Wireless access point (WAP): Allows wireless devices to connect to a network.

Include a simple network diagram showing how these devices fit into a connected environment.

Emphasize recognizing the devices and their purposes rather than understanding their internal operations.

4. Network Traffic and Traffic Flow (90–110 words)

• Define network traffic as information transmitted across a network.
• Define traffic flow as the movement of that information between devices and services.
• Explain that data may travel through multiple network devices before reaching its destination.
• Introduce gateway routing as forwarding communication beyond the local network toward another network.
• Use a simple diagram to illustrate the direction of information moving through a connected system.

5. Following a Request and Response (130–150 words)

Use a familiar workplace example: an employee opening a document stored in a cloud service.

• The employee’s laptop sends a request to access the document.
• The request travels through the local network infrastructure.
• A gateway router forwards the request toward the external service.
• The cloud service receives and processes the request.
• The service sends a response containing the requested information.
• The response travels back through the network to the employee’s laptop.

Include a labeled diagram showing the request and response paths.

Reinforce that this example illustrates how endpoints, network infrastructure, and centralized services work together.

6. Understanding Connected System Dependencies (60–80 words)

• Explain that successful communication depends on multiple components functioning together.
• Use a brief example of a shared network connection becoming unavailable.
• Describe how the disruption could prevent multiple endpoints from accessing a centralized service.
• Reinforce the importance of understanding the communication path rather than viewing devices in isolation.

7. Key Takeaways (40–50 words)

• Connected systems consist of endpoints, network infrastructure, and centralized services.
• Network devices enable communication between connected components.
• Network traffic moves between devices and services through request and response exchanges.
• Shared dependencies mean a disruption in one component can affect multiple users.

Out of Scope

Detailed network device configuration, MAC and IP addressing operations, subnetting, packet structure, encapsulation, routing tables, specific network protocols, traffic monitoring, network performance analysis, and troubleshooting procedures.

Writer Guidance: Align with the Skills and Knowledge document’s requirements for endpoints, network infrastructure, centralized services, network traffic, traffic flow, gateway routing, request and response communication, and introductory network device terminology. Build on the Connected Systems video without repeating its standalone versus connected device comparison. Use a consistent diagram throughout the reading to identify components and illustrate how information travels between them. Keep network device explanations at a recognition level and reserve detailed networking operations for later modules.

C3M1 Reading: The OSI Model (G-YAAVQ9)

Asset Type: Existing reading requiring revision
Target Length: 750–850 words
Lesson: C3M1 Lesson 1: Connected Systems Thinking

Purpose

Introduce the Open Systems Interconnection (OSI) model as a seven-layer framework for understanding how devices communicate across networks. Explain the basic function of each layer and introduce foundational networking terminology that learners will encounter in later modules. Connect the OSI model to the movement of information through connected systems without introducing detailed packet processing or troubleshooting procedures.

Content Outline

1. Introduction to the OSI Model (70–80 words)

• Define the OSI model as a conceptual framework that organizes network communication into seven layers.
• Explain why networking professionals use layers to understand the different functions involved in communication.
• Connect the OSI model to the endpoints, network infrastructure, and centralized services introduced in the previous reading.
• Clarify that the OSI model describes communication functions rather than seven separate physical devices.

2. The Seven Layers of the OSI Model (350–390 words)

Introduce each layer, its primary purpose, and foundational terminology.

Layer 7: Application

• Explain that this layer provides network services used by applications.
• Introduce HTTP/HTTPS for web communication, SMTP for email transmission, and DNS for translating domain names into IP addresses.
• Clarify that the application layer is not the application itself.

Layer 6: Presentation

• Explain that this layer addresses how information is formatted and represented.
• Introduce data compression as a way to reduce the amount of information transmitted.
• Briefly mention data encoding and encryption as examples of presentation-related functions.

Layer 5: Session

• Explain how sessions organize and manage communication between applications.
• Introduce the concept of establishing, maintaining, and ending communication sessions.

Layer 4: Transport

• Explain how this layer supports communication between applications on different devices.
• Introduce segmentation as dividing information into smaller units for transmission.
• Define flow control as a mechanism for managing the rate of data transmission.
• Introduce TCP and UDP as transport protocols without explaining their detailed operations.

Layer 3: Network

• Explain that this layer supports communication between different networks.
• Introduce packets as units of data associated with network-layer communication.
• Reinforce the role of IP addresses in identifying destinations across networks.

Layer 2: Data Link

• Explain that this layer supports communication across a local network link.
• Introduce frames as units of data associated with the data link layer.
• Reinforce MAC addresses as identifiers used in local network communication.

Layer 1: Physical

• Explain that this layer represents the physical transmission of data.
• Introduce electrical signals, light signals, and wireless radio signals.
• Connect the layer to cables, fiber-optic connections, and wireless transmission.

Include a labeled diagram showing all seven layers, their numbers, and primary functions.

3. How the Layers Work Together (110–130 words)

• Explain that the layers represent different functions involved in the communication process.
• Use a simple example of a user accessing a website.
• Describe how the application, transport, network, data link, and physical layers contribute different functions to communication.
• Explain that information travels through network connections and is interpreted by the receiving system.
• Reinforce that the layers work together rather than operating as independent systems.

Include a simple visual showing communication between two devices with the seven OSI layers represented on each side.

Avoid explaining encapsulation and decapsulation in detail.

4. Recognizing Common Networking Terms by Layer (100–120 words)

Provide a reference table connecting the terminology introduced in the reading to the appropriate OSI layers.

OSI layer	Foundational terms
7: Application	HTTP, HTTPS, SMTP, DNS
6: Presentation	Data compression, encoding
5: Session	Communication sessions
4: Transport	TCP, UDP, segmentation, flow control
3: Network	IP addresses, packets
2: Data Link	MAC addresses, frames
1: Physical	Cables, fiber, wireless signals

• 
  Emphasize recognizing the terminology and its general relationship to the OSI model.
• Clarify that the terms will be explored in greater detail as learners study network communication.

5. Why the OSI Model Matters in IT Support (70–90 words)

• Explain how the OSI model provides a shared vocabulary for describing network communication.
• Introduce the idea that connectivity depends on multiple communication functions working together.
• Use a brief example contrasting a physical connection problem with an application communication problem.
• Explain how recognizing these differences helps IT professionals communicate technical information.

Avoid introducing formal OSI-based troubleshooting procedures.

6. Key Takeaways (40–50 words)

• The OSI model organizes network communication into seven conceptual layers.
• Each layer represents a different communication function.
• Common networking terms, including protocols, addresses, packets, and frames, relate to different layers.
• The OSI model helps IT professionals understand and describe network communication.

Out of Scope

Detailed encapsulation and decapsulation, packet headers, TCP handshakes, port numbers, routing tables, subnetting, detailed protocol operations, packet analysis, OSI-based troubleshooting procedures, and advanced network configuration.

Writer Guidance: Use the existing The OSI Model reading as the starting point. Align with the Skills and Knowledge document’s requirement to introduce all seven layers and the following terminology: HTTP/HTTPS, SMTP, DNS, data compression, segmentation, packets, frames, flow control, TCP, UDP, and MAC addresses. Provide concise definitions and familiar examples, emphasizing recognition and basic understanding rather than detailed protocol behavior. Use a seven-layer diagram and a terminology reference table to support comprehension. Avoid detailed encapsulation, which is addressed in C3M6, and formal troubleshooting applications, which are developed in later modules.

The reading should establish a foundational mental model of network communication, not require learners to explain exactly how packets are constructed or processed.

C3M1 Reading: Local Area Networks (LANs)

Asset Type: New reading
Target Length: 650–750 words
Lesson: C3M1 Lesson 2: Networked Environments

Purpose

Explain how local area networks (LANs) connect devices within a limited geographic area and support communication within homes, businesses, and organizations. Introduce network ownership and management boundaries, internal and external access, wired and wireless connectivity, and the distinction between communication that remains within a LAN and communication that passes through a default gateway.

Content Outline

1. Introduction to Local Area Networks (60–70 words)

• Define a local area network (LAN) as a network connecting devices within a limited geographic area.
• Provide examples of LANs in homes, offices, schools, and businesses.
• Explain how LANs enable connected devices to communicate and access shared resources.
• Distinguish a LAN’s geographic footprint from the broader networks it may connect to.

2. LAN Boundaries and Organizational Ownership (100–120 words)

• Explain that LANs typically serve a specific location or organization.
• Introduce the concept of an organizational ownership and management boundary.
• Describe how an organization’s IT team may manage its local network infrastructure.
• Explain that an organization can control its LAN without controlling the broader internet.
• Use a small business office as an example of a locally managed network.

3. Network Access: Intranets, Extranets, and the Internet (120–140 words)

Introduce three different access contexts:

Intranet

• Define an intranet as an internal network or collection of resources intended for members of an organization.
• Provide an example of employees accessing an internal company website.

Extranet

• Define an extranet as organizational resources made accessible to authorized external users, such as business partners.
• Provide an example of a supplier accessing a company’s partner portal.

Public Internet

• Explain that the internet connects networks globally and provides access to publicly available services.
• Distinguish internet access from access to private organizational resources.

Clarify that intranets and extranets describe access arrangements, not necessarily separate physical networks.

4. LAN Infrastructure and Connectivity (120–140 words)

Introduce common infrastructure managed within a LAN:

• Switches: Connect wired devices within a local network.
• Cabling: Provides physical connections between network devices.
• Wireless access points: Allow wireless devices to connect to the LAN.
• Routers and gateways: Provide connections between the LAN and other networks.

Explain the two primary connection methods:

• Wired Ethernet: Devices connect using physical network cabling.
• Wireless LAN (WLAN): Devices connect through wireless access points using Wi-Fi.

Include a simple diagram showing wired and wireless endpoints connected to the same LAN.

Emphasize that both connection types can provide access to shared local resources.

5. Local Communication vs. Communication Beyond the LAN (140–160 words)

• Explain that some communication occurs entirely within the local network.
• Use an example of an employee accessing a file server located on the same LAN.
• Introduce the default gateway as the device or network interface used to reach destinations outside the local network.
• Explain that communication destined for another network is forwarded through the default gateway.
• Use an example of an employee accessing a cloud application over the internet.
• Contrast the two communication paths:
  • Local endpoint → LAN infrastructure → local resource
  • Local endpoint → LAN infrastructure → default gateway → external network or service

Include a diagram comparing local communication with communication beyond the LAN.

Keep the explanation conceptual without introducing routing tables or subnet calculations.

6. Why LAN Boundaries Matter in IT Support (60–80 words)

• Explain why IT support professionals need to recognize which devices and resources belong to a local network.
• Reinforce the distinction between locally managed infrastructure and external network services.
• Use a brief example contrasting access to a local printer with access to an internet-hosted application.
• Explain how understanding network boundaries helps technicians describe connectivity issues accurately.

7. Key Takeaways (40–50 words)

• LANs connect devices within limited geographic areas.
• Organizations typically manage their own local network infrastructure.
• Intranets, extranets, and the public internet represent different access contexts.
• LANs support wired Ethernet and wireless connectivity.
• Default gateways enable communication beyond the local network.

Out of Scope

Detailed LAN configuration, VLANs, subnetting, IP address assignment, DHCP configuration, Ethernet standards, Wi-Fi frequency bands and channels, wireless security configuration, routing tables, advanced network segmentation, WAN technologies, and detailed troubleshooting procedures.

Writer Guidance: Align with the Skills and Knowledge document’s requirements for LAN geographic footprint, organizational ownership boundaries, intranets, extranets, public internet access, locally managed infrastructure, direct local communication, default gateway communication, wired Ethernet, and wireless LANs. Build on the basic networking terminology introduced in Lesson 1 without repeating device definitions in detail. Use a consistent small business example to demonstrate LAN ownership, infrastructure, access contexts, and communication paths. Avoid detailed home network configuration, which is addressed in Module 2, and WAN technologies, which are covered in Module 5.

C3M1 Reading: Local Area Networks (LANs)

Asset Type: New reading
Target Length: 600–700 words
Lesson: C3M1 Lesson 2: Networked Environments

Purpose

Introduce local area networks (LANs), their geographic and organizational boundaries, and how devices communicate within a LAN and access external networks.

Content Outline

1. Introduction to LANs (60–70 words)

• Define LANs and their limited geographic footprint.
• Introduce familiar examples: homes, schools, and offices.
• Explain how LANs connect devices and shared resources.

2. LAN Infrastructure and Ownership (100–120 words)

• Introduce switches, cabling, and wireless access points as locally managed infrastructure.
• Explain organizational ownership and IT management boundaries.
• Distinguish infrastructure controlled locally from external networks.

3. Wired and Wireless Connectivity (100–120 words)

• Wired Ethernet: Physical network connections.
• Wireless LAN (WLAN): Devices connecting through Wi-Fi.
• Use a home network with a wired desktop, wireless laptop, and printer to illustrate both connection types.
• Include a simple network diagram.

4. Internal and External Network Access (120–140 words)

• Intranet: Internal organizational resources.
• Extranet: Resources accessible to authorized external partners.
• Public internet: Connectivity to external networks and services.
• Use brief workplace examples to distinguish these access contexts.

5. Local Communication and Default Gateways (150–170 words)

• Explain communication between devices on the same local network.
• Introduce the default gateway as the path to other networks.
• Compare accessing a local printer with accessing a cloud application.
• Include a simple diagram illustrating local versus external communication.

6. Key Takeaways (40–50 words)

• LANs connect devices within a limited geographic area.
• LAN infrastructure can be managed locally.
• Wired and wireless devices can share a LAN.
• Intranets, extranets, and the internet represent different access contexts.
• Default gateways enable communication beyond the local network.

Out of Scope

LAN configuration, VLANs, subnetting, DHCP, Ethernet and Wi-Fi standards, wireless configuration, routing tables, WAN technologies, and detailed troubleshooting.

Writer Guidance: Use a simple home network to illustrate LAN connectivity and communication paths. Introduce brief workplace examples only where needed to explain organizational ownership, intranets, and extranets. Keep the focus conceptual and avoid detailed home network hardware or configuration topics covered in Module 2.

C3M1 Reading: Internet for Businesses

Asset Type: New reading
Target Length: 550–650 words
Lesson: C3M1 Lesson 2: Networked Environments

Purpose

Introduce how businesses connect their local networks to the internet and compare three common internet connection technologies: Dedicated Internet Access (DIA), Fiber-to-the-Premises (FTTP/PON), and cable broadband (DOCSIS).

Content Outline

1. Introduction to Business Internet Connectivity (60–70 words)

• Explain how businesses use internet service providers (ISPs) to connect their local networks to the internet.
• Build on the LAN and default gateway concepts from the previous reading.
• Introduce the connection between an organization’s network and the ISP.

2. How Internet Connectivity Reaches a Business (100–120 words)

• Explain the basic connection path: ISP infrastructure → business premises → local network.
• Introduce the role of provider equipment and the connection point between the ISP and the business.
• Distinguish the ISP-managed connection from locally managed network infrastructure.
• Include a simple diagram of the connection path.

3. Common Business Internet Connection Types (230–260 words)

Dedicated Internet Access (DIA)

• Explain dedicated connectivity and its use in business environments.
• Introduce predictable performance and service-level agreements (SLAs).

Fiber-to-the-Premises (FTTP/PON)

• Explain how fiber-optic infrastructure delivers internet connectivity to a building.
• Introduce passive optical networks (PON) as a common fiber delivery method.
• Clarify that this is typically a shared provider network rather than dedicated connectivity.

Cable Broadband (DOCSIS)

• Explain how cable internet uses coaxial cable infrastructure.
• Introduce DOCSIS as the technology supporting data transmission over cable networks.
• Explain that bandwidth is typically shared among customers in the provider’s service area.

4. Comparing Business Internet Connections (100–120 words)

• Compare the three connection types based on:
  • Dedicated versus shared infrastructure.
  • General performance and reliability considerations.
  • Business needs and service expectations.
• Include a simple comparison table.
• Emphasize that availability and service characteristics vary by provider and location.

5. Key Takeaways (40–50 words)

• ISPs connect business networks to the internet.
• Internet delivery technologies differ in infrastructure and service characteristics.
• DIA provides dedicated connectivity, while FTTP/PON and cable broadband commonly use shared provider infrastructure.
• Businesses select connectivity based on availability and operational needs.

Out of Scope

Detailed ISP architecture, fiber installation, DOCSIS versions, optical networking equipment configuration, bandwidth calculations, circuit provisioning, WAN protocols, internet connection troubleshooting, and advanced service-level agreement analysis.

Writer Guidance: Focus on how internet connectivity reaches a business and the basic differences among DIA, FTTP/PON, and cable broadband. Use a simple office connection diagram rather than a complex enterprise network. Avoid specific speeds, pricing, and provider examples that may become outdated. Keep the discussion introductory, with more detailed WAN technologies reserved for Module 5.

C3M1 Reading: Cloud Networks

Asset Type: Existing video converted to reading
Target Length: 450–550 words
Lesson: C3M1 Lesson 2: Networked Environments

Purpose

Explain how cloud networks connect users to remotely hosted resources and how cloud connectivity differs from traditional on-premises networking.

Content Outline

1. Introduction to Cloud Networks (60–70 words)

• Define cloud networks and their relationship to cloud computing.
• Explain how organizations access remotely hosted applications, storage, and services.
• Connect to the previous readings on LANs and business internet connectivity.

2. On-Premises vs. Cloud Networks (100–120 words)

• Compare locally hosted and remotely hosted resources.
• Explain how cloud providers operate infrastructure in remote data centers.
• Clarify that organizations still need local network infrastructure to access cloud services.

3. How Cloud Connectivity Works (130–150 words)

• Trace a basic path: endpoint → LAN → internet → cloud-hosted service.
• Explain how users access shared applications and data from different locations.
• Use a familiar example, such as opening a document stored in the cloud.
• Include a simple diagram showing local and cloud connectivity.

4. Cloud Network Resources (90–110 words)

• Introduce remote computing, storage, and networking resources.
• Explain how cloud providers make these resources available to organizations.
• Briefly introduce on-demand access without explaining pricing or resource management.

5. Key Takeaways (40–50 words)

• Cloud networks connect users to remotely hosted resources.
• Cloud providers operate infrastructure outside an organization’s local environment.
• Local networks and internet connectivity provide access to cloud services.
• Cloud connectivity supports access to shared applications and data across locations.

Out of Scope

Virtualization, multi-tenancy, cloud resource management, cloud pricing, scalability, elasticity, detailed cloud architecture, cloud network configuration, and cloud security administration.

Writer Guidance: Convert the existing Cloud Networks video into a concise reading, retaining its explanation of cloud-hosted resources and the distinction between traditional and cloud environments. Remove outdated adoption statistics, unsupported cost-saving claims, and cybersecurity-specific language. Emphasize connectivity and the relationship between local networks and cloud services. Reserve virtualization, cloud management, and benefits for the following Cloud Computing reading.

C3M1 Reading: Local and Cloud-Based Systems

Asset Type: New reading, draft in progress
Target Length: 700–850 words
Lesson: C3M1 Lesson 2: Networked Environments

Purpose

Compare local and cloud-based infrastructure, introduce how cloud resources are hosted and managed, and explain foundational cloud technologies and benefits.

Content Outline

1. Local vs. Cloud-Based Systems (100–120 words)

• Define on-premises infrastructure and cloud-hosted systems.
• Compare infrastructure location, ownership, and management responsibilities.
• Include a simple visual comparing the two environments.

2. Cloud Service Providers and Data Centers (110–130 words)

• Define cloud service providers (CSPs) and data centers.
• Introduce remotely hosted computing, storage, and networking resources.
• Explain how CSPs maintain physical infrastructure.

3. Virtualization and Multi-Tenancy (150–170 words)

• Virtualization: Multiple virtual machines (VMs) can run on shared physical hardware.
• Hypervisor: Software that enables and manages VMs.
• Multi-tenancy: Multiple customers share infrastructure while maintaining logically separated resources.
• Retain the existing virtualization diagram.

4. Managing Cloud Resources (100–120 words)

• Compare responsibilities for on-premises and cloud infrastructure.
• Introduce cloud management through web consoles, APIs, and command-line interfaces (CLIs).
• Explain that organizations remain responsible for managing their cloud resources.

5. Benefits and Considerations (180–220 words)

• Remote access: Access resources from different locations with appropriate connectivity and authorization.
• Cost: Reduced upfront hardware investment, but ongoing service costs.
• Reliability and availability: Redundancy helps reduce the impact of failures.
• Scalability: Add resources to support growth.
• Elasticity: Adjust resources as demand changes.
• Note that benefits depend on service configuration and organizational needs.

6. Key Takeaways (40–50 words)

• Local and cloud systems differ in location, ownership, and management.
• CSPs provide remotely hosted infrastructure.
• Virtualization and multi-tenancy enable shared computing resources.
• Cloud systems offer flexibility and potential operational advantages.

Out of Scope

Cloud deployment models, detailed virtualization architecture, VM configuration, cloud networking configuration, provider-specific services, cloud security administration, pricing calculations, and advanced high-availability architecture.

Writer Guidance: Use the existing draft as the foundation. Preserve the virtualization, multi-tenancy, management, and cloud benefits sections while simplifying technical detail. Avoid repeating the connectivity explanations from Cloud Networks. Keep comparisons balanced and avoid implying that cloud services always cost less or that on-premises systems cannot support remote access.

C3M1 Reading: Cloud Computing and Software-Defined Networks

Asset Type: New reading, draft in progress
Target Length: 700–850 words
Lesson: C3M1 Lesson 2: Networked Environments

Purpose

Introduce common cloud service models, hybrid and multi-cloud environments, and how software-defined technologies support network management.

Content Outline

1. Cloud Service Models (250–290 words)

• SaaS: Ready-to-use applications accessed over a network.
• PaaS: Managed platforms for developing and deploying applications.
• IaaS: Virtualized computing, storage, and networking infrastructure.
• Explain how provider and customer responsibilities differ across models.
• Include a comparison table with simple examples.

2. Additional Cloud Service Models (80–100 words)

• NaaS: Network capabilities delivered as a managed service.
• XaaS: General term for technology resources delivered as services.
• Keep explanations conceptual without introducing specific vendor solutions.

3. Hybrid and Multi-Cloud Environments (130–150 words)

• Hybrid cloud: Combines on-premises infrastructure with cloud services.
• Multi-cloud: Uses services from multiple cloud providers.
• Explain why organizations might use these approaches.
• Include a simple comparison diagram.

4. Software-Defined Networking and Virtualization (160–190 words)

• SDN: Uses software-based control to manage network behavior.
• NFV: Runs network functions, such as routing or firewalls, as software rather than dedicated appliances.
• Explain how these technologies provide flexibility in managing network resources.
• Use a simple example of centrally managing network settings.

5. Key Takeaways (40–50 words)

• SaaS, PaaS, and IaaS provide different levels of managed services.
• Hybrid and multi-cloud environments combine infrastructure and services.
• SDN and NFV support software-based network management.
• Cloud service models affect how responsibilities are divided.

Out of Scope

Cloud provisioning, provider-specific configuration, SDN controllers and architecture, NFV implementation, cloud routing configuration, advanced cloud security, service pricing, and cloud migration planning.

Writer Guidance: Use the existing draft as the foundation. Preserve the required terminology while reducing technical complexity and product-specific examples. Emphasize recognizing service models, understanding basic management responsibilities, and distinguishing SDN from NFV. Avoid repeating virtualization and data center explanations from Local and Cloud-Based Systems.

The draft describes NFV as replacing physical network hardware. That’s somewhat misleading. NFV allows certain network functions to run as software, but the underlying physical infrastructure is still necessary.

I’d also revise the statement suggesting an IT technician can manage an entire cloud network with just a few clicks. That sounds like it oversimplifies the complexity of cloud network administration.

C3M1 Reading: Anatomy of Network Environments

Asset Type: New reading
Target Length: 550–650 words
Lesson: C3M1 Lesson 2: Networked Environments

Purpose

Compare the components and data flow of home, small business, and enterprise networks, illustrating how network environments increase in size and complexity.

Content Outline

1. Introduction to Network Environments (60–70 words)

• Explain how network environments vary in size, complexity, and purpose.
• Introduce home, small business, and enterprise networks.
• Reinforce that all environments use endpoints, network infrastructure, and services.

2. Home Networks (100–120 words)

• Identify common components: endpoints, router, Wi-Fi, and internet connection.
• Illustrate data flow from a home device through the local network to an external service.
• Use a familiar example, such as accessing a website.

3. Small Business Networks (110–130 words)

• Identify additional components: switches, wireless access points, and shared resources.
• Explain how infrastructure supports multiple employees and business applications.
• Illustrate data flow between an employee device, network infrastructure, and a shared service.

4. Enterprise Networks (130–150 words)

• Explain how larger networks connect departments, buildings, and locations.
• Introduce additional infrastructure and centralized services.
• Illustrate data flow across interconnected network components to reach shared resources.
• Emphasize how multiple users and services depend on shared infrastructure.

5. Comparing Network Environments (90–110 words)

• Compare components, connections, and data flow across the three environments.
• Explain how increasing scale introduces additional infrastructure and dependencies.
• Include three simplified diagrams showing components and data paths using consistent visual conventions.

6. Key Takeaways (40–50 words)

• Home, small business, and enterprise networks share foundational components.
• Network size and complexity influence infrastructure and connections.
• Data flows through connected components to reach local and remote services.
• Larger environments introduce additional dependencies.

Out of Scope

Detailed enterprise architecture, VLANs, subnetting, routing protocols, network configuration, troubleshooting procedures, and formal network diagram interpretation.

Writer Guidance: Build progressively from a familiar home network to small business and enterprise environments. Include a simple data flow example for each environment, emphasizing the relationships between endpoints, infrastructure, and services. Use simplified diagrams to support understanding without teaching formal network mapping. Avoid repeating detailed device definitions from Lesson 1 or introducing advanced networking concepts covered later in the course.

C3M1 Reading: Network Components, Devices, and Diagrams

Asset Type: New reading
Target Length: 500–600 words
Lesson: C3M1 Lesson 2: Networked Environments

Purpose

Introduce common network devices, their basic functions, and how network topology icons and diagrams represent these components and their connections.

Content Outline

1. Introduction to Network Components (50–60 words)

• Explain why networks require different devices to support communication.
• Introduce network diagrams as visual representations of devices and connections.

2. Common Network Devices (220–250 words)

• Routers: Connect different networks and direct traffic between them.
• Switches: Connect devices within a local network.
• Wireless access points: Provide wireless connectivity to a network.
• Modems: Connect local equipment to certain types of internet service connections.
• Compare the basic functions of these devices using familiar examples.

3. Network Topology Icons and Diagrams (180–210 words)

• Introduce common network topology icons for routers, switches, access points, and modems.
• Briefly identify additional symbols learners may encounter, including endpoints, servers, firewalls, and cloud services.
• Explain how lines represent connections between devices.
• Include a simple labeled diagram with a symbol legend.
• Reinforce that symbols may vary between diagrams and tools.

4. Key Takeaways (40–50 words)

• Network devices perform different communication functions.
• Routers, switches, access points, and modems support network connectivity.
• Network topology icons represent devices and connections.
• Diagrams provide a visual representation of network structure.

Out of Scope

Detailed device configuration, routing protocols, VLANs, subnetting, advanced network topologies, network troubleshooting, creating network diagrams, and detailed network map interpretation.

Writer Guidance: Align with the Skills and Knowledge document’s requirements for routers, switches, access points, modems, and network topology icons and diagrams. Use the existing Network Components, Devices, and Diagrams reading (G-JJ8WLR) as the primary starting point, with Hubs and Switches (G-D4DODC) and Routers (G-J1RB4O) as supplemental resources. Focus on device recognition and basic functions. Reserve interpreting device relationships and tracing data flow for the following Network Maps video. Focus on recognizing network devices, their basic functions, and their visual representations. Introduce diagram legends and explain that symbols may vary. Reserve interpreting connection types, tracing data paths, identifying shared dependencies, and recognizing potential connectivity issues for the following Network Maps video.

C3M1 Reading: Network Mapping Diagrams

Asset Type: New reading
Target Length: 600–750 words
Lesson: C3M1 Lesson 2: Networked Environments

Purpose

Explain how to create network mapping diagrams that represent connections between devices, network infrastructure, internet access, and cloud services. Prepare learners to create a basic network diagram in the following activity.

Content Outline

1. Introduction to Network Mapping (60–80 words)

• Explain how network mapping diagrams document connected environments.
• Distinguish interpreting an existing diagram from creating one.
• Introduce the process of identifying components and representing their relationships.

2. Identifying Components to Include (130–150 words)

• Endpoints: Computers, mobile devices, and other connected devices.
• Network infrastructure: Routers, switches, wireless access points, and firewalls.
• Internet connectivity: Connections between local networks and external services.
• Local resources: Servers, shared storage, and other internal services.
• Cloud resources: Cloud applications, storage, and infrastructure.

3. Representing Cloud Tools and Services (140–170 words)

• Software as a Service (SaaS): Show cloud-hosted applications accessed by users.
• Cloud storage: Represent remotely hosted storage resources.
• Infrastructure as a Service (IaaS): Represent cloud-hosted infrastructure such as virtual servers.
• Cloud infrastructure and security: Show relevant cloud network and security components at a conceptual level.
• Explain how cloud services connect to local devices and infrastructure through the internet.

4. Creating a Basic Network Mapping Diagram (160–190 words)

• Identify the devices, services, and infrastructure in an environment.
• Group components into local network, internet, and cloud environments.
• Select appropriate symbols and labels.
• Draw connections between components.
• Use a legend to explain symbols and connection types.
• Review the diagram to ensure the relationships and communication paths are clear.
• Include a progressively developed example showing a small business network connected to cloud services.

5. Key Takeaways (40–50 words)

• Network mapping diagrams represent devices, infrastructure, and services.
• Local and cloud resources can be included in the same diagram.
• Symbols, labels, and connections communicate component relationships.
• Clear diagrams help IT professionals understand connected environments.

Out of Scope

Advanced network topology design, configuring network devices, subnetting, VLANs, routing protocols, detailed cloud architecture, diagramming software tutorials, and troubleshooting procedures.

Writer Guidance: Build directly on the preceding Network Maps video. Avoid repeating detailed explanations of network symbols, device functions, and connection types. Focus on applying those concepts to construct a simple diagram. Include one progressively developed example that starts with local devices and infrastructure, then adds internet connectivity, SaaS, cloud storage, IaaS, and cloud infrastructure or security components. Use consistent symbols and clear labels. Keep the example conceptual rather than requiring technical configuration or knowledge of specific cloud platforms.

Instructional alignment: The previous video teaches learners to interpret network diagrams. This reading teaches them to construct a diagram, preparing them for the following network mapping activity.

C3M1: Module 1 Review

Content Outline

Introduction: Congratulate learners on completing Module 1 and briefly reinforce how networks connect devices, infrastructure, and services to support communication and data flow.

Module 1 Key Concepts

• Networked Systems: Networks connect devices and systems to exchange information and access shared resources.
• Connected Components: Endpoints, network devices, infrastructure, and services work together to support communication.
• OSI Model: The OSI model organizes network communication into seven layers to help explain how data moves between systems.
• Local Area Networks (LANs): LANs connect devices within a limited area, such as a home, office, or building.
• Internet Connectivity: Internet service providers connect local networks to external networks and services.
• Local and Cloud-Based Systems: Local systems use resources within an organization’s environment, while cloud systems provide access to remotely hosted resources.
• Cloud Computing: Cloud service models include SaaS, PaaS, IaaS, and NaaS. Hybrid and multi-cloud environments combine different cloud resources, while software-defined networking uses software to manage network behavior.
• Network Environments: Home, small business, and enterprise networks use similar foundational components but differ in size, complexity, and infrastructure.
• Network Devices: Routers, switches, wireless access points, and modems perform different functions to support network connectivity.
• Network Maps and Diagrams: Network diagrams use symbols, labels, and connections to represent devices, infrastructure, services, and data flow.
• Network Dependencies: Understanding how components connect helps identify shared resources and potential areas of connectivity disruption.

Out of Scope Guardrails

• Do not introduce new concepts or detailed technical explanations.
• Do not include device configuration, troubleshooting procedures, or advanced networking concepts.
• Do not reference the upcoming module quiz.