Open Source Essentials Free Sample Questions

Dynamic linking relies on shared libraries (.so files on Linux) where the operating system loader maps the read-only text (code) segment of the library into physical memory only once, sharing pages across multiple independent process virtual address spaces. In contrast, static linking copies the entire library code into each executable binary, duplicating that memory footprint across each running daemon process. While static linking avoids runtime library missing dependencies, it wastes significant RAM and Flash storage when multiple running programs use the same library.

Both Java and Python compile human-readable source code into an intermediate, architecture-neutral representation called bytecode (.class files in Java, .pyc files in Python). This bytecode is then executed inside a runtime virtual machine (such as the JVM or CPython VM), which translates the bytecode into CPU-specific machine instructions on the fly or via Just-In-Time (JIT) compilation. This contrasts with purely native ahead-of-time compilation (like C/C++ or Rust) and pure direct interpretation.

In a thin client architecture, the endpoint device handles user display and input, while computational logic, business rules, and storage occur primarily on a centralized server or remote infrastructure. This dramatically simplifies maintenance, patch management, and security, because sensitive financial data is not persisted on the endpoint and hardware failure at the branch requires mere physical swapping without data migration. Fat clients, conversely, perform heavy processing locally and require decentralized client-side software management.

In a monolithic architecture, all functional modules share the same runtime and database connections, meaning failure or resource exhaustion in one component (e.g., inventory) crashes the entire system. Decomposing into microservices decouples components into independently scalable services with dedicated data stores, interacting via standardized, stateless RESTful APIs. This isolates faults and allows specific high-demand services to scale horizontally.

In an IaaS deployment, the customer configures the database application, manages access privileges, ensures data integrity, and handles encryption at rest and in transit. The cloud provider only supplies raw compute instances and block storage volumes without inspecting or managing software workloads inside the guest OS.

Under the cloud Shared Responsibility Model for IaaS, the cloud provider manages physical hardware, hypervisors, and data center facilities. The customer retains full ownership and operational responsibility for the guest operating system (patching, configuration), user access controls, networking security groups, installed runtime environments, and application data.

Under the FSF Free Software Definition: Freedom 0 is the freedom to run the program as you wish for any purpose; Freedom 1 is the freedom to study how the program works and change it (access to source code is a prerequisite); Freedom 2 is the freedom to redistribute copies to help others; and Freedom 3 is the freedom to distribute copies of your modified versions to others.