Study guide

15.4 Local, Network, and Cloud Computing and Storage; How Binary Data Are Stored

Praxis Computer Science 5652

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Praxis 5652 Exam Overview and ETS Pseudocode

1.1 Praxis 5652 Test Facts, Scoring, and Registration 1.2 Official ETS Pseudocode Notation and Tracing Strategy

2 Chapter 2: Impacts of Computing: Innovation, Access, and Effects

2.1 Computing for Creativity, Problem Solving, Communication, and Innovation 2.2 Equal Access, the Digital Divide, and Accessibility 2.3 Beneficial and Harmful Effects of Computing Innovations

3 Chapter 3: Impacts of Computing: Intellectual Property, Ethics, Privacy, and Security

3.1 Intellectual Property: Copyright, Open Source, and Creative Commons 3.2 Ethical and Unethical Computing Practices and Their Implications 3.3 Privacy, Security, Data Collection, and Local vs. Cloud Storage

4 Chapter 4: Algorithms and Computational Thinking: Abstraction, Decomposition, Number Bases, and Representation

4.1 Abstraction and Abstraction Hierarchies 4.2 Decomposition, Pattern Recognition, and Developing Algorithms 4.3 Number Bases: Binary, Octal, Decimal, and Hexadecimal 4.4 Algorithm Formats: Natural Language, Flowcharts, Pseudocode, and Tracing

5 Chapter 5: Algorithms: Efficiency, Limits of Computing, and Randomization

5.1 Algorithm Efficiency: Linear, Quadratic, Exponential, and Logarithmic Growth 5.2 Limits of Computing: Unsolvable Problems, Intractability, and Heuristics 5.3 Randomization, Random vs. Pseudorandom Numbers, and Scaling to a Range

6 Chapter 6: Algorithms: Searching, Sorting, and Recursion

6.1 Searching Algorithms: Linear Search and Binary Search 6.2 Sorting Algorithms: Tracing, Comparisons, Correctness, and Efficiency 6.3 Recursion: Base Cases, Tracing, Errors, and Iterative Equivalents

7 Chapter 7: Programming: Variables, Data Types, Strings, and Expressions

7.1 Variables, Data Types, and Type Conversion 7.2 Strings and String Operations 7.3 Operators, Precedence, Expressions, and Formulas 7.4 Boolean Expressions, Truth Tables, and Boolean Algebra

8 Chapter 8: Programming: Selection, Iteration, and Writing Code

8.1 Sequence and Selection: if, else, Chained and Nested Conditions 8.2 Iteration: for, while, do … while, and repeat … until Loops 8.3 Reading, Completing, and Modifying Code

9 Chapter 9: Programming: Procedures, Arrays, and Data Structures

9.1 Procedures, Parameters, Return Values, Nested Calls, and Scope 9.2 Arrays, Lists, and Two-Dimensional Arrays 9.3 Stacks, Queues, and Dictionaries (Maps)

10 Chapter 10: Programming: Correctness, Errors, Testing, and Code Quality

10.1 Program Correctness: Preconditions, Postconditions, Invariants, and Testing vs. Proof 10.2 Error Types and Debugging Techniques 10.3 Choosing Useful Test Cases: Boundaries, Partitions, Coverage, and Regression 10.4 Extensibility, Modifiability, and Reusability: Constants and Parameterization 10.5 Documentation, Code Reviews, Peer Feedback, and End-User Feedback

11 Chapter 11: Programming: Events, Usability, Input Validation, and APIs

11.1 Event-Driven Programming, Asynchronous Events, and Concurrency 11.2 Usability, Meaningful Error Messages, and Input Validation vs. Verification 11.3 Libraries and APIs: Reading Definitions, Making Calls, and Weighing Trade-offs

12 Chapter 12: Programming: Languages, Tools, Paradigms, and Object-Oriented Design

12.1 Low- and High-Level Languages, Compilers and Interpreters, and IDEs 12.2 Programming Paradigms: Procedural, Object-Oriented, and Others 12.3 Classes, Objects, Instance Variables, Methods, and Encapsulation 12.4 Inheritance, Polymorphism, and Overloading vs. Overriding

13 Chapter 13: Data: Bits, Encoding, Compression, and Encryption

13.1 Bits and Bytes: Why Binary, Storage Calculations, and Signed Integers 13.2 Encoding Text, Images, and Sound 13.3 Lossless and Lossy Compression: Run-Length Encoding, Huffman Coding, and Media Formats 13.4 Encoding vs. Encryption, Symmetric and Public-Key Encryption, and Their Trade-offs

14 Chapter 14: Data: Analysis Tools, Simulation, Storage, and Collection

14.1 Analyzing Data with Spreadsheets: Cleaning, Transforming, and Visualizing 14.2 Simulation and Modeling 14.3 Files, Databases, and Storage Requirements: Scale, Redundancy, and Backup 14.4 Collecting, Aggregating, and Generating Data: Public Data Sets, Surveys, Sensors, and Crowdsourcing

15 Chapter 15: Computing Systems: Hardware, Operating Systems, and Computing Environments

15.1 Hardware Components and the Fetch–Decode–Execute Cycle 15.2 Operating Systems, Software Components, and Resource Issues 15.3 Embedded Systems, the Internet of Things, and Types of Computing Systems 15.4 Local, Network, and Cloud Computing and Storage; How Binary Data Are Stored

16 Chapter 16: Networks, the Internet, the Web, and Cybersecurity

16.1 Network Types and Wired and Wireless Communication 16.2 Network Hardware and Layered Network Models (OSI and TCP/IP) 16.3 Network Performance: Bandwidth, Latency, Load, and Estimating Needs 16.4 How the Internet Works: Protocols, IP Addressing, DNS, URLs, and Reliability 16.5 The Web: HTTP, HTML and Markup Languages, Browsers, Servers, and Clients 16.6 Cybersecurity: The Five Pillars, Strong Passwords, Security Strategies, and Trade-offs

15.4 Local, Network, and Cloud Computing and Storage; How Binary Data Are Stored

Key Takeaways Explain This Topic AI

Local computing and storage run on the user's own device: fast and usable offline, but limited to that device's capacity and vulnerable to its loss.

Network (on-premises) computing uses an organization's own servers over its local network, centralizing files, backups, and control, but it requires the organization to buy and maintain the equipment.

Cloud computing delivers servers, storage, and software over the Internet on demand; it scales easily and supports collaboration but depends on connectivity and on the provider's security and policies.

Cloud service models: IaaS provides virtual machines and storage, PaaS provides a managed platform for deploying code, and SaaS provides complete applications used through a browser or app.

Hard drives and tape store bits magnetically, SSDs and USB drives store them as trapped charge in flash memory cells, and CDs, DVDs, and Blu-ray discs store them as reflective marks read by a laser.

Last updated: September 2026

What this competency asks

ETS asks you to be familiar with trade-offs between local, network, and cloud computing and storage :

Identify advantages and disadvantages in terms of performance, cost, security, reliability, and collaboration .

Identify means of storing binary data .

Section 3.3 introduced the privacy side of local versus cloud storage. This section compares the options as computing systems.

Three places to compute and store

  • Model Where it runs Example
  • Local On the user's own device Editing a video with software on a laptop; saving files to its SSD

Network (on-premises) On servers the organization owns, reached over its local network A school file server; a district's student-information server in its own data room

Cloud On a provider's data centers, reached over the Internet Google Workspace or Microsoft 365; cloud storage; renting virtual servers

Comparing them on ETS's five criteria

Criterion Local Network (on-premises) Cloud

Performance Fastest for large local files; no network delay; limited by one device's hardware Fast on the local network; limited by the organization's servers Huge capacity on demand; each access limited by Internet bandwidth and latency

Cost Up-front device cost; no subscription High up-front cost for servers, plus ongoing staff, power, and maintenance Pay as you go or by subscription; little up-front cost; can grow expensive at scale

Security Full control; risk of theft or loss and weak personal practices Organization controls policies; needs skilled IT staff Providers invest heavily in security; data sit with a third party; shared responsibility; account compromise is a major risk

Reliability A single device fails; backups are up to the user Depends on the organization's redundancy and backups Providers replicate data across data centers; outages still happen; requires Internet access

Collaboration Hard; files must be copied and sent Good within the organization Excellent: real-time co-editing from anywhere

Hybrid designs are common: work locally, synchronize to the cloud, and keep sensitive systems on-premises.

Worked decisions

Scenario Best fit Deciding criterion

A photographer edits 200 GB of raw images while traveling with unreliable Wi-Fi Local, with a cloud backup whenever a connection is available Performance and offline access

District policy requires student records to stay on servers the district controls, and it has an IT staff Network (on-premises) Security and control

A new app might have 100 users or 100,000 users next month Cloud (IaaS or PaaS) Cost and scalability: pay only for what is used

  • Students in three schools co-write one lab report Cloud (SaaS) Collaboration
  • Cost: up front versus ongoing

Local and on-premises systems are mostly capital expenses : hardware is bought up front. The cloud is mostly an operating expense : the customer pays each month for what it uses. With illustrative numbers (not real prices), suppose an on-premises server costs $9,000 up front plus $2,400 a year for power, space, and maintenance, and a comparable cloud server costs $500 a month, or $6,000 a year.

  • After On-premises total Cloud total
  • 1 year $11,400 $6,000
  • 2 years $13,800 $12,000
  • 3 years $16,200 $18,000

The costs break even when 9,000 + 2,400t = 6,000t, so t = 2.5 years. The cloud wins for short-lived, small, or unpredictable workloads because it can scale down. Owning can cost less for a steady, heavy load over many years, once staff time is added to the comparison.

Reliability in numbers

Providers state availability as the percentage of time a service is up. A year has 8,760 hours, so 99% availability allows 87.6 hours of downtime a year, 99.9% allows 8.76 hours, and 99.99% allows about 53 minutes. Each additional nine cuts the allowed downtime by a factor of 10.

A cloud service also needs the school's own Internet link. If the link is up 99.5% of the time and the provider 99.9%, both must work at once: 0.995 × 0.999 ≈ 0.994, or about 99.4%. The weakest link in the chain limits the whole system.

Cloud computing in more detail

The U.S. National Institute of Standards and Technology (NIST) describes cloud computing as on-demand network access to a shared pool of configurable computing resources (networks, servers, storage, applications, and services) that can be provisioned rapidly with minimal management effort.

Service models

Model Provider manages Customer manages Examples

IaaS (infrastructure as a service) Physical hardware, networking, virtualization Operating system, runtime, applications, data Virtual machines such as AWS EC2 and Azure VMs

PaaS (platform as a service) Everything through the runtime and operating system The application code and data Google App Engine, Heroku

SaaS (software as a service) The entire application Only its use, and the user's own data and settings Google Workspace, Microsoft 365, learning management systems

Deployment models

Public cloud: shared infrastructure from a provider, available to many customers.

Private cloud: cloud-style infrastructure dedicated to one organization.

Hybrid cloud: a mix, for example public cloud for the website and private systems for sensitive records.

Scalability and elasticity: cloud resources can be added or removed quickly as demand changes. A school's registration site can handle a surge on the first day of sign-ups, then scale back down.

Shared responsibility for security

Moving to the cloud moves some security work to the provider, but never all of it.

Model Provider secures Customer still secures

IaaS Data centers, hardware, network, virtualization Operating system updates, applications, firewall settings, accounts, data

PaaS Everything through the runtime Application code, accounts, access to data

SaaS The whole application User accounts, passwords and multifactor authentication, sharing settings, and what data is uploaded

A secure data center does not help if a teacher reuses a leaked password or shares a gradebook with "anyone with the link."

Means of storing binary data

Every storage medium needs a physical property with two distinguishable states.

Medium How a bit is stored Characteristics Typical use

Hard disk drive (HDD) Direction of magnetization on spinning platters Large, cheap per GB; slower; moving parts Bulk storage, backups

Magnetic tape Magnetization along a long tape Very cheap per GB; sequential access only Long-term archives

Solid-state drive (SSD), USB flash, SD card Electric charge trapped in flash memory cells Fast, silent, shock-resistant; cells wear out after many writes Laptops, phones, portable storage

Optical disc (CD, DVD, Blu-ray) Pits and lands on a reflective surface, read by a laser Portable and inexpensive; low capacity; slow Distributing media; some archives

RAM (DRAM) Charge in tiny capacitors that must be refreshed constantly Very fast; volatile Working memory for running programs

Cache (SRAM) State of transistor circuits (flip-flops) Fastest memory outside registers; volatile CPU caches

Everything that is nonvolatile keeps data without power: magnetic, flash, and optical media. RAM and cache are volatile (Section 15.1).