Operating Systems

The Unix architecture is layered with hardware at the base, then the kernel (innermost software layer that directly manages hardware), then the shell (user interface), then application programs at the outermost layer. The kernel is between hardware and all other software, making it the innermost software layer.

UNIX is inherently a multi-user operating system designed from the beginning to support multiple simultaneous users and processes. This is a fundamental characteristic that distinguishes UNIX from single-user systems like MS-DOS. The statement is false.

Mobile Web Applications run within a browser sandbox and have limited access to device hardware compared to native applications. Features like offline mode, location lookup, camera access, and file system access either require specific HTML5 APIs (which may not be universally supported) or are completely unavailable in web environments. Native apps have full access to these capabilities through platform SDKs.

Object Identification in QTP/UFT is used to define and configure the properties used to uniquely identify objects during test execution. It does not retrieve runtime values - for that, you would use methods like GetROProperty to retrieve runtime object properties.

SCAN is a JCL (Job Control Language) statement that performs syntax checking on the JCL itself. It scans for errors without executing the job, helping catch issues before actual processing. The other options are incorrect - SCAN is not for previous jobs, syntax errors, or doing nothing.

OSH (Orchestrate Shell) operators in DataStage are instances of C++ classes that inherit from the APT_Operator base class. This base class provides the framework for all operator functionality. APT_dump is a debugging tool. The OSH operators are not related to Unix CLI or system DLLs.

System software manages computer hardware and provides platform for applications. Operating systems (like Windows, macOS, Linux) are the primary example of system software - they manage memory, processes, files, and peripheral devices. Application software runs on top of system software to perform specific user tasks.

System accounts are designated for automated system services, processes, and daemons rather than human users. Neither ordinary users, system administrators, nor security administrators should log in directly to system accounts; instead, humans must use their own personal accounts.

Columns of an access matrix represent objects, and the list of permissions for a given object across all subjects is called an Access Control List (ACL). In contrast, rows represent subjects and correspond to capability lists. Triples represent (subject, object, rights) entries, and properties are unrelated attributes.

If a client needs a persistent connection to a service, it can call the Context.bind Service method, while onResume is called right after onStart if your activity is the foreground activity on the screen.

onPostExecute runs on the main UI thread, allowing direct updates to UI elements without needing additional thread synchronization. This is different from doInBackground which runs on a background thread and cannot touch UI components.

The return value from doInBackground is automatically passed as a parameter to onPostExecute, allowing the background result to be processed on the UI thread. This is the standard AsyncTask flow pattern.

Both Handler class and onPostExecute() can execute code after background work completes. Handlers provide flexible timing control while AsyncTask's onPostExecute is specifically designed for post-background UI updates.

onStartCommand() is called when a service is explicitly started using startService(). Binding with bindService() triggers onBind() instead. The two initiation methods have different lifecycle callbacks.

Service onCreate() is called whether the service is started via startService() or bound via bindService(). It's the initialization callback that runs once per service instance, unlike onStartCommand() which can run multiple times.