System Administration Part I - SAS 9.2 Platform Administration

The explanation for the given correct answer is that SAS Pooled Workspace Server is indeed configured by default to use server side pooling. Server side pooling allows multiple users to share a single workspace server, which can increase efficiency and optimize resource usage. This configuration is beneficial in environments where there are multiple users accessing the SAS environment simultaneously.

SAS Server Manager in SAS Management Console is a plug-in because it is an additional component or extension that adds specific functionality to the SAS Management Console. It is designed to manage SAS servers and provides a centralized interface for administrators to monitor and control server activities. As a plug-in, it integrates seamlessly with the SAS Management Console and enhances its capabilities for server management.

SAS Management Console is a Java client. This means that it is a software application that is written in the Java programming language and can be run on any device that has Java installed. As a Java client, SAS Management Console provides a user interface for managing and administering SAS software deployments. It allows users to perform tasks such as configuring servers, managing user access and permissions, and monitoring system performance. Being a Java client also means that SAS Management Console is platform-independent and can be used on different operating systems.

The correct answer is "SAS Trusted User." This user is considered special because they have additional privileges and permissions within the SAS system. They are trusted to perform certain tasks and have access to specific resources that regular users do not have. This user is typically responsible for managing and administering the SAS environment, ensuring its security and stability.

The new Server Manager in SAS Management Console does not have the task of deleting server logs. The Server Manager is responsible for tasks such as quiescing, stopping, pausing, resuming, and validating servers. It also allows users to test connections to servers and view information about current connections and processes. However, deleting server logs is not listed as one of its tasks.

The "sas.servers" server in the list could be used to generate a bootstrap script to start and stop SAS servers on Unix and Z/OS. This server is specifically designed for managing SAS servers and would have the necessary functionality to generate the bootstrap script needed for starting and stopping the servers.

The correct answer is SAS Deployment Manager. SAS Deployment Manager is a tool used to manage and update SAS deployments. It allows users to update hostnames references in a SAS EBI deployment, ensuring that the correct hostnames are used for communication between different components of the deployment. The other options listed (SAS Deployment Wizard, SAS Update utility, SAS Universal Update Driver) do not specifically mention updating hostnames references and are not the correct tools for this task.

The correct answer is omaconfig.xml. This file contains the SAS Metadata Server configuration settings. It is responsible for storing and managing the metadata configuration information for the SAS environment.

AdminUsers.txt should be secured specifically due to security considerations. This file likely contains sensitive information such as usernames and passwords of admin users. Securing this file helps prevent unauthorized access and protects the confidentiality of this sensitive information.

The correct answer is False. The SAS Metadata supports three types of repositories, which are Foundation Repository, Stored Process Repository, and OLAP Server Repository.

In SAS 9.2, it is not necessary to define dependencies between repositories because SAS 9.2 uses a metadata server that automatically manages dependencies between repositories. This means that when one repository is updated or changed, the metadata server will automatically update any other repositories that are dependent on it. This eliminates the need for manually defining dependencies and ensures that changes made in one repository are reflected in all other repositories.

The default Configuration directory name, if not customized during install, is "Config".

The given correct answer is true because the Update Hostnames Reference Tool is specifically designed to work in situations where virtualization, ghosting, and cloning are involved. These processes often involve creating multiple copies or instances of a system, and the tool helps in updating the hostnames of these copies to avoid conflicts and ensure proper network communication.

A SAS In-Process Server is responsible for scheduling jobs from certain web applications. It allows these web applications to schedule and manage the execution of jobs within the SAS environment. This server helps in automating the execution of tasks and ensures that jobs are executed at the specified time intervals or based on certain triggers. It provides a seamless integration between web applications and the SAS system, allowing for efficient job scheduling and management.

The correct answer is "File In memory." When using a journal file with a Metadata Server, the file is stored in memory. This means that the data from the journal file is loaded into the server's memory for faster access and processing. Storing the file in memory allows for quicker retrieval and updating of metadata, improving the overall performance and efficiency of the server.

The default journal file's size on a 32-bit and Z/OS operating system is 200 MB.

During migration from SAS 9.1.3 to SAS 9.2, the defined dependencies between repositories and the associations between metadata objects are not eliminated. Therefore, the correct answer is False.

A SAS Metadata Server could not be started without the Repository Manager. The Repository Manager is responsible for managing the metadata repository, which stores all the metadata information for SAS applications and resources. Without the Repository Manager, the metadata server would not be able to access or manage the metadata repository, making it impossible to start the server.

The SAS Web Management Console is used by administrative users to communicate with the Content Table Server. This server is responsible for managing and storing metadata about SAS content, such as reports, data sets, and stored processes. The Web Management Console allows users to perform administrative tasks such as managing users, groups, and roles, as well as configuring server settings and monitoring server activity.

The default journal file size on a 64-bit operating system is 500 MB. This means that the journal file, which is used for recording changes made to a file system, can store up to 500 MB of data before it needs to be cleared or resized. This size is typically sufficient for most systems, but it can be adjusted if needed.

The APPData directory in SAS Configuration Directory is used for SAS Content Server and BI Dashboard. This directory stores the necessary files and data for the BI Dashboard application to function properly. It allows users to create, customize, and share interactive dashboards and reports using data from various sources.

The SAS Metadata Server does not remain in memory during a server pause or stop. When the server is paused or stopped, the SAS Metadata Server is unloaded from memory, and all active connections and sessions are terminated. This allows for system resources to be freed up and allocated to other processes.

The given statement is false. The most common components of a SAS Application server are SAS Workspace Server, SAS Stored Process Server, and SAS Metadata Server. SAS Batch Server and SAS Pooled Workspace Server are not typically part of the SAS Application server.

A SAS Content Server is not used by the Shared Services components of the midtier.