SAS Institute A00-251 Administering SAS Viya 3.5 Exam Practice Test

According to the official SAS Viya 3.5 documentation, all SAS Viya microservices are self-contained, lightweight pieces of software that do one thing and depend on other processes as little as possible. You can find this information in the SAS Viya 3.5 Administering Guide page 40.

SAS Viya microservices are self-contained, lightweight pieces of software that do one thing and depend on other processes as little as possible. They are designed to be modular, independent, and easy to deploy, manage, and scale. Each microservice is responsible for a specific functionality, and they are loosely coupled, allowing them to be deployed, updated, and scaled independently.

According to the official SAS Viya 3.5 documentation, the My Credentials option in the Security menu of SAS Environment Manager allows a user to manage their own external account. You can find this information in the SAS Viya 3.5 Administering Guide page 125.

When a table is loaded in a distributed (MPP) CAS server, the controller distributes the rows of the table to the worker nodes. This allows for parallel processing of the data, which can improve performance. The controller also ensures that a redundant copy of the rows is available for fault tolerance. This means that if a worker node fails, the data can still be accessed from another worker node.

According to the SAS Documentation for the MPP Loader procedure, the default behavior is that the controller distributes the rows to the worker nodes and ensures a redundant copy of the rows is available for fault tolerance. This is stated in the documentation as follows: "By default, the MPP Loader procedure distributes the table rows among the worker nodes and ensures that two copies of the rows exist. This provides fault tolerance should one of the worker nodes fail."

To add workers that persist only until the CAS server restarts, you should use the deploy-casworker.yml playbook. This playbook will create new workers, configure them and apply any necessary hotfixes. The workers will be destroyed when the CAS server is restarted, so you will need to run the playbook again if you want them to persist after the restart.

In a programming-only SAS Viya deployment, the web application SAS Studio is available. SAS Studio is a web-based application that provides a workspace for SAS programmers to access, manage, and analyze data, as well as creating, running and debugging SAS programs. This application is designed for data scientists, statisticians, and programmers who need to perform advanced analytics tasks, including data visualization, data exploration, and data modeling.

According to the official SAS Viya 3.5 documentation, the CLI command to restart the SAS Logon service is sas-admin service restart saslogon. You can find this information in the SAS Viya 3.5 Administering Guide page 22.

Global caslibs are special kinds of caslibs that allow the sharing of in-memory data between CAS sessions. Global caslibs are defined in the SAS Viya configuration file and are persisted in the CAS server. Any user who is logged in to a SAS Viya application can access global caslibs, and they are not deleted when the CAS server is stopped.

A global caslib is a caslib that is available to all CAS sessions, regardless of the user who is logged in to the SAS Viya application. Global caslibs are useful for sharing data between different CAS sessions, and can be used to improve performance by keeping frequently used data in memory. Global caslibs are defined in the CAS configuration file and are available to all CAS sessions as soon as the CAS server is started.

In a distributed SAS Viya environment, the SAS Configuration Server (Consul server) must be started first. The Consul server is the foundation of the SAS Viya environment and provides service discovery and configuration management for all other servers and services. It is responsible for maintaining the configuration information and state of the SAS Viya environment, including the location and status of all servers and services.