Emerging and Digital Technologies: Revision and References
Shared revision, practice questions, answer explanations and references from the original module.
By Akhilesh Saini
Module CA-10 — Consolidated quick revision
The table below is for last-minute recognition. Its short phrases supplement rather than replace the explanations above.
| Exam clue | Concept | Qualification to remember |
|---|---|---|
| Ready-to-use hosted application | SaaS | Customer still manages permitted access and data |
| Hosted development/deployment environment | PaaS | Customer develops/configures application |
| Virtual compute, storage and network | IaaS | Customer commonly manages guest OS/apps |
| Capacity expands and contracts | Rapid elasticity | Availability and cost are not automatically guaranteed |
| Shared infrastructure across users | Resource pooling | Tenants require appropriate isolation |
| Exclusive cloud for an organization | Private cloud | May be hosted off premises |
| Two interacting cloud infrastructures | Hybrid cloud | Distinct from 'any online app plus local laptop' |
| Broad intelligent computer behavior | AI | Not every automation is AI |
| Models learn patterns from data | ML | No universal guarantee of correctness |
| Multi-layer neural-network learning | Deep learning | A subset of machine learning |
| Training with labeled targets | Supervised learning | Training differs from inference |
| Discover groupings without per-item labels | Unsupervised learning | Not the same as a supervised classifier |
| Creates new text, images or code | Generative AI | Generated facts may be invented |
| Connected physical devices with sensors/actuators | IoT | Can use local gateways rather than direct public access |
| Measures a physical quantity | Sensor | Different from actuator |
| Performs a physical action | Actuator | Different from sensor |
| Processes near the device | Edge computing | Often complements cloud processing |
| Shared coordinated records | Distributed ledger | Not all DLT systems use blocks |
| Cryptographically linked record batches | Blockchain | Tamper resistance ≠ truth of entries |
| Network agreement over accepted updates | Consensus | Method varies by network |
| On-ledger programmatic logic | Smart contract | Not automatically a legal contract |
| Printed optical matrix pattern | QR code | Decoded by camera/scanner |
| Short-range contactless radio | NFC | Commonly associated with 13.56 MHz |
| Indian instant interbank payment ecosystem | UPI / NPCI | Payment system, not a kind of QR image |
| Ordinary incoming UPI credit | No recipient UPI PIN approval | Verify account record instead |
| Programmatic software interface | API | Separate from a GUI |
| Structured API text format | JSON | Not encryption or a database |
| Common read request | HTTP GET | Governed by the service's API contract |
| API request not found | HTTP 404 | Distinct from authentication failure |
| Hypervisor / VMM | Manages virtual machines | Uses physical resources |
| OS inside a VM | Guest OS | Not the same as physical host OS |
| Bare-metal / hosted hypervisor | Type 1 / Type 2 | Architectural categories |
| Shared-kernel isolated app environment | Container | Distinct from conventional guest-OS VM |
| VM checkpoint | Snapshot | Not automatically an independent durable backup |
Seven final self-checks
- Cloud: SaaS supplies an app, PaaS supplies an application platform, and IaaS supplies infrastructure; responsibility still exists at every level.
- AI: AI is broader than ML. Model training is distinct from inference, and an articulate generated answer may still be wrong.
- IoT: Sensors measure; actuators act; controllers, gateways and networks connect the physical and digital worlds.
- Blockchain: Blocks can be cryptographically linked and accepted through consensus; their presence does not prove input facts are true.
- Digital payments: QR codes are optical, NFC uses proximity radio, and UPI is a payment system. Distinguish receiving from authorizing a debit.
- APIs: An API is a software contract linking client request and service response; access control and error handling remain necessary.
- Virtualization: Hypervisors create VMs on physical hosts; VMs conventionally run guest operating systems, while containers usually share a kernel.
Sources and further reading
The lesson explanations and all 84 MCQs are original teaching material. The following primary technical/official resources support important definitions and offer optional further reading. Product operations, security recommendations and payment application interfaces can change, so check current provider guidance for any real transaction or system.
- NIST — The Definition of Cloud Computing (SP 800-145) — cloud essential characteristics, SaaS/PaaS/IaaS and deployment models.
- NIST — Artificial Intelligence Glossary — AI terminology and boundaries.
- NIST — AI Risk Management Framework — trustworthy use, risks, oversight and limitations (optional deeper reading).
- NIST — Internet of Things Glossary — connected physical devices and core concepts.
- NIST — IoT Cybersecurity Program FAQs — IoT devices, sensors/actuators and systems.
- NIST — Blockchain Technology Overview (NISTIR 8202) — block structure, hashes, consensus, limitations and use cases.
- NFC Forum — NFC Technology — proximity radio and contactless interaction.
- NPCI — UPI Frequently Asked Questions — UPI function, PIN authorization and safety basics.
- MDN — Introduction to Web APIs — programmatic interfaces.
- MDN — HTTP Overview — client/server exchange, methods and responses.
- Microsoft Learn — Virtual Machines and Hyper-V Overview — host, guest and hypervisor concepts.
- Red Hat — What is Virtualization? — virtualization and hypervisor fundamentals.