Foundations of Mobile Computing

Introduction and Context

Mobile computing is the study and practice of computing in environments where users, devices, data, and services may move while communication occurs through wireless or intermittently connected networks. It combines computer systems, wireless communication, distributed systems, networking, human–computer interaction, security, and increasingly artificial intelligence.

Traditional computing often assumes that a computer remains in a fixed location, has relatively stable power, and communicates over a reliable network. Mobile computing relaxes all three assumptions. A smartphone may change its point of attachment to the network, lose connectivity in a tunnel, operate on battery power, and access services through several heterogeneous networks. Consequently, mobile computing is not merely “computing with a smaller computer”; it is a systems discipline concerned with mobility, uncertainty, resource constraints, and context.

Mobile computing supports activities such as mobile banking, navigation, emergency response, industrial monitoring, telemedicine, field engineering, logistics, connected vehicles, and remote learning. Its importance has increased with the convergence of cellular networks, Wi-Fi, Bluetooth, satellite systems, cloud platforms, edge computing, sensors, and intelligent software.

Learning Objectives

After completing this chapter, a learner should be able to:

1. Define mobile computing and distinguish it from related concepts.

2. Explain the historical evolution of mobile computing.

3. Analyze the characteristics, constraints, and design implications of mobile systems.

4. Apply layered, client–server, and distributed reference models to mobile applications.

5. Evaluate practical use cases, risks, governance issues, and contemporary developments.

6. Select appropriate architectural and operational practices for mobile applications.

1. Fundamental Terminology

1.1 Mobility

Mobility is the ability of a user, device, application, or service to change location or network attachment while retaining some degree of communication and functionality. Mobility can occur at several levels:

• User mobility: a person accesses services from different locations or devices.
• Device mobility: a physical device changes its location.
• Network mobility: an entire network, such as a vehicle network, changes its point of attachment.
• Session mobility: an active application session continues while connectivity changes.
• Service mobility: a service or its execution state moves between hosts or edge locations.

Mobility is not identical to portability. Portability concerns whether software or hardware can be used across platforms or locations; mobility concerns movement during or between use.

1.2 Wireless Communication

Wireless communication transfers information without a continuous physical conductor between communicating endpoints. Important wireless technologies include cellular networks, wireless local-area networks, personal-area networks, satellite links, and short-range identification systems. Wireless is a communication property, whereas mobile computing is a broader computing paradigm. A fixed sensor using Wi-Fi is wireless but not necessarily mobile; a mobile device may temporarily use a wired docking connection.

1.3 Mobile Device

A mobile device is a computing device designed to operate while being carried or transported. Examples include smartphones, tablets, wearable computers, vehicle computers, handheld terminals, ruggedized field computers, and some sensor nodes. Relevant properties include processing capability, memory, display, sensors, battery capacity, radio interfaces, operating system, and security hardware.

1.4 Mobile Application

A mobile application is software designed to provide functionality through a mobile device or mobile network. It may execute locally, communicate with cloud services, use nearby devices, or combine all three. A modern mobile application is commonly a distributed system rather than a self-contained program.

1.5 Context Awareness

Context is information characterizing the situation of an entity, such as location, time, identity, device state, network quality, activity, environmental conditions, and nearby objects. A context-aware system uses such information to adapt behavior. For example, a navigation application may reduce data quality when bandwidth is low, present larger controls while a user is walking, or provide an alert when the user approaches a defined location.

Context adaptation must be governed carefully. Location and behavioral data can reveal sensitive personal information, and inaccurate context can cause unsafe or discriminatory decisions.

1.6 Handoff and Roaming

A handoff, or handover, is the transfer of an active connection or service from one access point, cell, or network path to another. It may be horizontal, between technologies of the same type, or vertical, between different technologies such as Wi-Fi and cellular networks.

Roaming is the ability to obtain network service outside the user’s home network or normal coverage area, often through agreements between network operators. Handoff emphasizes continuity of an active connection; roaming emphasizes use of a visited network or service domain. They may occur together but are conceptually distinct.

1.7 Disconnection and Intermittent Connectivity

A mobile system may experience complete disconnection, temporary loss of coverage, high delay, variable throughput, or asymmetric communication. Applications therefore need techniques such as local caching, replication, queued operations, synchronization, conflict resolution, and graceful degradation.

1.8 Pervasive and Ubiquitous Computing

These terms overlap but are not exact synonyms for mobile computing.

• Mobile computing emphasizes computing while users, devices, or services move.
• Wireless computing emphasizes communication through radio or other wireless media, whether or not anything moves.
• Pervasive computing emphasizes the integration of computing into everyday environments and activities, often through many devices.
• Ubiquitous computing is a closely related vision in which computing is embedded throughout the environment and becomes unobtrusive or “invisible” to the user.
• Internet of Things (IoT) emphasizes identifiable physical objects equipped with sensing, processing, communication, and software capabilities.
• Nomadic computing emphasizes users who move between locations and use available computing resources, even when sessions do not remain continuously connected.

A smart-home thermostat illustrates the distinction. It may be wireless and pervasive but stationary. A field engineer’s tablet is mobile computing even if only one device is involved. A fleet of connected vehicles combines mobility, wireless communication, IoT, edge computing, and distributed systems.

2. Evolution of Mobile Computing

2.1 Foundations: Portable and Time-Sharing Systems

Early computing was dominated by centralized mainframes and fixed terminals. Portable calculators, terminals, and early personal computers introduced the possibility of carrying computational resources, but communication was generally wired and mobility was limited.

The development of packet-switched networking established a foundation for distributed communication. Instead of reserving a fixed communication path, packet networks divide data into units that may travel through shared infrastructure. This approach supports bursty data traffic and enables hosts to communicate across interconnected networks.

2.2 Cellular and Portable Computing

The development of cellular telephony introduced geographical reuse of radio spectrum through cells and enabled users to communicate while moving. Early cellular systems primarily supported voice. Subsequent generations progressively added digital transmission, messaging, packet data, multimedia, broadband access, and improved support for machine communication.

Portable computers and personal digital assistants demonstrated that computing could be performed away from fixed offices. Their limitations included low processing power, small storage, short battery life, and expensive or slow wireless links. These constraints stimulated research into mobile databases, disconnected operation, adaptive protocols, and mobile agents.

2.3 Smartphone and Platform Convergence

Smartphones combined telephony, general-purpose operating systems, cameras, positioning, sensors, application platforms, and Internet access. Application stores and software development kits created large ecosystems involving device manufacturers, network operators, cloud providers, developers, advertisers, and users.

The smartphone also changed the security model. A single device may contain identity credentials, payment instruments, health information, photographs, location history, and access to enterprise systems. Security consequently became a full lifecycle concern involving hardware, operating systems, applications, networks, cloud services, and user behavior.

2.4 Cloud, Edge, and Intelligent Mobile Systems

Cloud computing provides elastic remote storage and processing. However, sending all data to a distant cloud can introduce latency, bandwidth costs, privacy risks, and dependence on connectivity. Edge computing places computation closer to data sources or users, such as at a base station, local gateway, enterprise site, or roadside unit.

Contemporary mobile systems increasingly use machine learning for speech recognition, recommendation, computer vision, anomaly detection, and predictive maintenance. Processing may be divided among the device, edge infrastructure, and cloud. This division is sometimes called cloud–edge–device orchestration or offloading. It must account for latency, energy, privacy, model accuracy, connectivity, and computational capability rather than assuming that the cloud is always superior.

3. Characteristics of Mobile Computing

3.1 Location and Movement

Location can influence service discovery, routing, access control, user interfaces, and data relevance. Movement introduces changing connectivity, changing neighboring devices, and changing environmental conditions. A mobile system must distinguish actual movement from inaccurate positioning and must tolerate rapid changes in network attachment.

3.2 Resource Constraints

Mobile devices typically have less energy, cooling capacity, storage, and radio power than data-center systems. Although high-end devices are powerful, resource constraints remain important because workloads, battery conditions, and network environments vary.

Energy is consumed by processors, displays, sensors, memory, and especially radio communication. Energy-aware design may use batching, adaptive sampling, local processing, compressed data, efficient protocols, and controlled background activity.

3.3 Variable Network Performance

Wireless channels are affected by distance, interference, obstacles, fading, congestion, mobility, and spectrum sharing. Consequently, bandwidth, packet loss, delay, and jitter may change over time. An application that works in a laboratory with stable Wi-Fi may fail in a crowded railway station or a rural area.

Performance should therefore be treated as a range of operating conditions rather than a single nominal value. Applications should use timeouts carefully, retry with bounded backoff, support resumable transfers, and communicate state clearly to users.

3.4 Heterogeneity

Mobile environments contain diverse devices, operating systems, screen sizes, sensors, network technologies, security capabilities, and accessibility requirements. Interoperability requires documented interfaces, portable data formats, capability detection, standards-based protocols, and systematic testing across representative conditions.

3.5 Dynamic Topology

In an infrastructure network, devices may join or leave, change addresses, or move between access points. In an ad hoc or opportunistic network, devices may communicate directly without fixed infrastructure. Routing and service discovery must therefore handle topology changes and incomplete knowledge.

3.6 Human and Social Context

Mobile systems are used during walking, driving, working, waiting, and social interaction. Attention is limited, and unsuitable notifications can create safety hazards. User interface design must consider touch accuracy, visibility, accessibility, cognitive load, language, and environmental noise.

3.7 Security Exposure

Wireless transmission can be intercepted, devices can be lost, applications can be installed from untrusted sources, and APIs can expose sensitive data. Mobile security requires authentication, authorization, encryption, secure key storage, software updates, application isolation, logging, privacy controls, and incident response.

4. Reference Models for Mobile Systems

Reference models provide abstractions for analyzing systems. They are not complete implementations; rather, they help assign responsibilities and identify interfaces.

4.1 Layered Model

A useful mobile computing stack contains the following conceptual layers:

1. Physical and radio layer: antennas, spectrum, modulation, coding, and signal transmission.

2. Link and access layer: framing, medium access, error detection, local retransmission, and association with an access network.

3. Network layer: addressing, routing, mobility support, and packet forwarding.

4. Transport layer: end-to-end delivery, congestion control, reliability, and multiplexing.

5. Middleware and service layer: discovery, synchronization, caching, session management, identity, location services, and data adaptation.

6. Application layer: business logic, user interfaces, analytics, and domain services.

7. Human and policy layer: usability, privacy, governance, safety, and organizational rules.

Layering reduces complexity because each layer exposes services through defined interfaces. However, strict layering can be inefficient in mobile environments. For example, an application may need network-quality information to select video quality, and an energy manager may need application priorities. Such controlled cross-layer interaction should be explicit, secure, and measurable rather than an accidental dependence on implementation details.

4.2 Client–Server Model

In a client–server system, a client requests services and a server provides resources or processing. A mobile client may contain the user interface, local cache, sensors, and some business logic, while servers provide authentication, durable storage, coordination, and intensive computation.

Common arrangements include:

• Thin client: most computation and data management occur remotely.
• Thick or rich client: substantial logic and data are held locally.
• Three-tier architecture: presentation, application logic, and data management are separated.
• Backend-as-a-service: common identity, storage, messaging, and analytics are provided as managed services.

A mobile client should not assume that every request will reach the server immediately. Offline-first design treats local operation as a normal state. Changes can be recorded in an operation log and synchronized later. If two replicas modify the same record, the system needs a conflict policy, such as last-writer-wins, field-level merging, version-based rejection, or domain-specific reconciliation. The correct policy depends on the meaning and risk of the data; blindly using last-writer-wins can destroy important information.

4.3 Distributed-System Model

A mobile application is often a distributed system: components execute on multiple devices and communicate through a network with no perfectly shared clock or guaranteed delivery. Important consequences include:

• partial failure, where one component fails while others continue;
• variable delay and possible message loss;
• inconsistent replicas and stale data;
• changing membership and identity;
• difficult debugging and observability;
• security boundaries between administrative domains.

Designers should define consistency requirements explicitly. A stock-trading or emergency dispatch system may require strong ordering and confirmation. A social-media feed or weather display may tolerate stale data. This is a business and safety decision as much as a technical one.

4.4 Edge–Cloud–Device Model

A contemporary reference model divides responsibilities among:

• Device: sensing, immediate interaction, local inference, and operation during disconnection.
• Edge: low-latency processing, aggregation, local control, and privacy-sensitive preprocessing.
• Cloud: large-scale storage, global analytics, model training, coordination, and long-term management.

Placement should be selected using criteria such as latency, energy, bandwidth, privacy, availability, cost, and regulatory constraints. A safety-critical control loop should not depend exclusively on a distant cloud connection.

5. Design Principles for Mobile Applications

5.1 Design for Disconnection

Applications should indicate whether data is local, synchronized, pending, or conflicted. They should preserve user work, support retry, and avoid duplicate effects. Idempotent operations—operations that can safely be repeated without changing the result beyond the first application—are particularly useful for unreliable communication.

5.2 Adapt to Capability and Conditions

The application should detect screen size, sensor availability, operating-system capabilities, battery state, network quality, and accessibility preferences. Adaptation may involve changing image resolution, reducing synchronization frequency, selecting a nearby service, or postponing nonurgent work.

5.3 Protect Data Throughout Its Lifecycle

Security should be applied during collection, transmission, processing, storage, sharing, backup, and deletion. Data minimization is preferable to collecting information merely because it might be useful later. Sensitive data should have defined retention periods and access policies.

5.4 Separate User Experience from Connectivity Assumptions

A user interface should communicate progress and uncertainty without exposing unnecessary technical detail. “Saved on this device; waiting for connection” is more useful than a generic error. Critical actions should have confirmation and recovery mechanisms.

5.5 Measure Realistic Quality of Experience

Technical metrics such as throughput and latency are necessary but insufficient. Evaluation should also consider task completion, interruption rate, perceived responsiveness, battery impact, accessibility, error recovery, privacy expectations, and safety. Testing should include weak networks, handoffs, low battery, overloaded servers, incorrect location, and clock differences.

6. Applications and Professional Relevance

Mobile computing has broad applications:

• Healthcare: remote consultation, patient monitoring, electronic records, and ambulance coordination.
• Transportation: navigation, fleet tracking, traffic management, and connected vehicles.
• Manufacturing: worker guidance, asset tracking, predictive maintenance, and augmented inspection.
• Banking and commerce: mobile payments, authentication, customer service, and location-aware offers.
• Education: field learning, collaborative classrooms, and access to digital resources.
• Public safety: disaster assessment, emergency communication, and responder coordination.
• Agriculture: soil sensing, crop monitoring, weather advisories, and precision application.
• Enterprise operations: inventory, sales-force automation, field service, and secure remote access.

For managers, mobile computing raises decisions about total cost of ownership, device procurement, network contracts, application lifecycle, support, data governance, vendor dependence, and workforce policies. For engineers, it raises decisions about architecture, protocols, testing, security, energy, observability, and fault tolerance.

7. Illustrative Case: Mobile Emergency-Response Coordination

Background

Consider an illustrative emergency-response system used after a major flood. Field teams carry rugged tablets with cameras, positioning, maps, and short-range radios. A regional command center operates cloud services, while local gateways provide edge connectivity when the public network is congested.

Problem

Responders must record victims, damaged infrastructure, supply needs, and hazards. Connectivity is intermittent, location readings may be inaccurate, and some information is sensitive. Duplicate or stale reports can misdirect scarce resources.

Analysis

The system is mobile, wireless, context-aware, and distributed. It must support user and device mobility, handoff, local operation, synchronization, role-based access, and auditability. A cloud-only design would be unsuitable because network access cannot be assumed during the most critical events. A fully local design would make regional coordination difficult.

Approach and Solution

The tablet stores encrypted local records and a signed operation log. Forms are designed for rapid use with gloves and limited attention. Photos are compressed locally, while high-resolution originals are uploaded when bandwidth permits. The edge gateway aggregates reports, performs basic validation, and provides local maps. The cloud maintains regional coordination and long-term analysis.

Each report has a status such as locally saved, submitted, acknowledged, or conflict pending. Synchronization uses record versions and domain rules. For example, two reports about a damaged bridge are not simply overwritten; they are linked for review, with timestamps, locations, authors, and evidence retained. Emergency commands received by a device require authentication and are logged. Access is restricted according to responder role, and sensitive victim data is minimized.

Outcome

The architecture allows responders to continue recording information during disconnection and provides command staff with progressively synchronized situational awareness. It does not eliminate uncertainty: positioning errors, inaccurate observations, and conflicting reports remain possible. Therefore, the system presents confidence indicators and preserves human decision authority.

Learning Points

1. Offline operation is a core mode, not an exceptional error state.

2. Edge processing can reduce latency and dependence on wide-area connectivity.

3. Conflict resolution must reflect domain meaning and safety consequences.

4. Security and privacy must be designed into workflows, not added after deployment.

5. Human judgment remains essential when sensor and network information is incomplete.

8. Limitations, Risks, and Governance

Mobile systems can increase inclusion, but they can also deepen digital divides through device cost, data charges, poor coverage, inaccessible interfaces, or language barriers. Dependence on location and behavioral data may enable surveillance. Personalized services can produce unfair treatment when models infer sensitive characteristics or perform poorly for underrepresented groups.

Important governance practices include informed consent where appropriate, purpose limitation, data minimization, transparent privacy notices, access control, retention limits, audit trails, breach response, and compliance with applicable data-protection and sector regulations. Organizations should distinguish consent from coercion, particularly in employment, education, and healthcare contexts.

Safety is critical in vehicular, medical, industrial, and emergency applications. Designers should identify hazards, define fail-safe states, maintain human override, validate updates, and avoid presenting uncertain automated outputs as facts. Artificial intelligence used on mobile devices should be evaluated for data quality, bias, adversarial manipulation, model drift, energy consumption, explainability appropriate to the risk, and secure model updates.

Other limitations include battery degradation, electronic waste, fragmented platforms, proprietary ecosystems, unreliable positioning, network congestion, software supply-chain vulnerabilities, and the environmental cost of manufacturing and operating large infrastructures.

9. Contemporary Developments and Future Direction

Current mobile computing research and practice are shaped by several developments:

• 5G and evolving cellular systems: improved capacity, lower latency in suitable conditions, network slicing concepts, and support for large device populations.
• Edge intelligence: machine-learning inference near sensors and users.
• Federated and privacy-preserving learning: training or adaptation using distributed data while attempting to reduce central collection.
• Extended reality: mobile and wearable systems that combine spatial sensing, graphics, and real-time interaction.
• Connected vehicles and intelligent transport: cooperative perception, roadside infrastructure, and distributed control.
• Energy harvesting and ultra-low-power systems: extending operation for sensors and wearables.
• Digital twins: continuously updated computational representations of physical assets or processes.
• Satellite–terrestrial integration: extending coverage to remote or disaster-affected areas.

These developments do not remove foundational constraints. They make architecture, governance, interoperability, and evidence-based evaluation more important. A new radio standard or AI model cannot compensate for poor requirements, unsafe defaults, weak identity management, or an inappropriate consistency model.

Chapter Summary

Mobile computing enables computing and communication in the presence of movement, wireless access, changing context, limited resources, and intermittent connectivity. Its terminology includes mobility, roaming, handoff, context awareness, disconnection, edge computing, pervasive computing, ubiquitous computing, and IoT. These concepts overlap but emphasize different system properties.

The field evolved from fixed and portable computing through cellular data and smartphones to cloud–edge–device systems and intelligent mobile applications. Key characteristics include dynamic location, heterogeneous devices and networks, variable performance, battery constraints, distributed operation, human-context dependence, and significant security and privacy exposure.

Layered, client–server, distributed, and edge–cloud–device models help analyze responsibilities and trade-offs. Effective designs support offline operation, synchronization, conflict resolution, adaptive behavior, secure data handling, accessibility, observability, and graceful failure. Mobile computing is central to healthcare, transport, enterprise, emergency response, commerce, education, and industrial systems, but its benefits must be balanced against safety, privacy, equity, environmental, and governance risks.

Key Terms

Mobility: Ability of a user, device, network, session, or service to change location or attachment.

Wireless communication: Transfer of information through a medium without a continuous physical conductor.

Mobile device: A portable computing device intended to operate while being carried or transported.

Mobile application: Software that provides functionality through a mobile device or mobile network.

Context awareness: Use of situational information to adapt system behavior.

Handoff: Transfer of an active connection or service between access points, cells, or network paths.

Roaming: Obtaining service through a visited network outside the normal home network.

Intermittent connectivity: Connectivity characterized by temporary loss, variable delay, or changing throughput.

Pervasive computing: Integration of computing into everyday environments through many cooperating devices.

Ubiquitous computing: A vision of computing embedded throughout the environment and made unobtrusive.

Internet of Things: Networked physical objects with sensing, processing, communication, and software.

Layered architecture: Organization of system functions into abstractions with defined interfaces.

Client–server model: Architecture in which clients request services and servers provide resources or processing.

Distributed system: Components executing on multiple computers and communicating over a network.

Edge computing: Processing performed near data sources or users to reduce latency or dependence on distant resources.

Offline-first design: Design approach treating local operation and later synchronization as normal behavior.

Replication: Maintenance of multiple copies of data or service state.

Conflict resolution: Rules for reconciling incompatible updates to replicated data.

Context adaptation: Modification of system behavior in response to device, network, user, or environmental conditions.

Mobile security: Protection of mobile devices, data, applications, communications, identities, and services.

Review Questions

Short Answer Questions

1. Define mobile computing and explain how it differs from wireless computing.

2. What is the difference between handoff and roaming?

3. List four characteristics that make mobile systems different from fixed systems.

4. Define context awareness and give one example.

5. What is meant by offline-first design?

Long Answer Questions

1. Explain the evolution of mobile computing from portable systems to cloud–edge–device architectures.

2. Discuss the layered reference model for mobile computing and explain why cross-layer interaction may sometimes be necessary.

3. Compare thin-client, rich-client, and three-tier mobile architectures.

4. Explain the effects of mobility, heterogeneity, intermittent connectivity, and battery constraints on application design.

5. Discuss security, privacy, safety, and governance challenges in mobile computing.

Analytical / Application Questions

1. Design a reference architecture for a mobile healthcare application that must operate during network outages. Justify placement of functions on the device, edge, and cloud.

2. Two field workers update the same inspection record while disconnected. Propose a conflict-resolution strategy and explain why simple last-writer-wins may be inappropriate.

3. Evaluate whether a smart-building sensor network should be classified as mobile computing, wireless computing, pervasive computing, IoT, or a combination. Justify your answer using the distinctions in this chapter.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes mobile computing from wireless computing?

A. Mobile computing always uses cellular networks, while wireless computing uses Wi-Fi only.

B. Mobile computing emphasizes movement and changing operating conditions, while wireless computing emphasizes the communication medium.

C. Mobile computing requires cloud processing, while wireless computing requires local processing.

D. Mobile computing is limited to smartphones, while wireless computing includes all computers.

Correct Answer: B. Mobile computing emphasizes movement and changing operating conditions, while wireless computing emphasizes the communication medium.

Question 2

What is the primary purpose of a handoff?

A. To encrypt stored user data

B. To transfer an active connection between access points or network paths

C. To compress application data before transmission

D. To replace a mobile device battery

Correct Answer: B. To transfer an active connection between access points or network paths

Question 3

Which feature is most directly associated with offline-first design?

A. Assuming every request reaches a server immediately

B. Disabling local storage to prevent stale data

C. Supporting local operation and later synchronization

D. Using only wired network connections

Correct Answer: C. Supporting local operation and later synchronization

Question 4

Which layer is primarily responsible for routing and addressing?

A. Physical and radio layer

B. Network layer

C. Application layer

D. Human and policy layer

Correct Answer: B. Network layer

Question 5

A stationary smart thermostat communicating through Wi-Fi is best described as which of the following?

A. Wireless, but not necessarily mobile

B. Mobile, but not wireless

C. Neither wireless nor pervasive

D. A handoff protocol

Correct Answer: A. Wireless, but not necessarily mobile

Question 6

Why can edge computing be advantageous for a mobile application?

A. It guarantees unlimited battery capacity.

B. It can reduce latency and dependence on a distant cloud.

C. It eliminates all security requirements.

D. It prevents devices from changing location.

Correct Answer: B. It can reduce latency and dependence on a distant cloud.

Question 7

Which issue is a consequence of distributed operation in mobile systems?

A. All components always share an identical clock.

B. Partial failure can occur while other components continue operating.

C. Network delay is always constant.

D. Data replicas cannot become inconsistent.

Correct Answer: B. Partial failure can occur while other components continue operating.

Question 8

Why is last-writer-wins potentially unsafe for emergency-response records?

A. It always requires a wired network.

B. It may overwrite valuable conflicting evidence without considering domain meaning.

C. It prevents all forms of encryption.

D. It can only be used for numeric data.

Correct Answer: B. It may overwrite valuable conflicting evidence without considering domain meaning.

Question 9

Which practice best supports mobile security throughout the data lifecycle?

A. Collecting all available location data indefinitely

B. Using access control, encryption, retention limits, and auditability

C. Relying solely on the user’s screen lock

D. Removing authentication when connectivity is poor

Correct Answer: B. Using access control, encryption, retention limits, and auditability

Question 10

Which statement about pervasive computing is most accurate?

A. It focuses only on high-speed cellular radio.

B. It emphasizes computing integrated into everyday environments through many devices.

C. It requires every device to be physically carried by a user.

D. It is identical in meaning to roaming.

Correct Answer: B. It emphasizes computing integrated into everyday environments through many devices.