In SAS Viya, CAS action sets provide the interface to CAS analytics capabilities. A developer calls cas.simple.summary() in Python via swat. What is a CAS action set, and how does it differ from a SAS procedure?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal — b is correct because CAS action sets (e.g., simple, regression, decisionTree, deepLearn) are server-side libraries of distributed analytics functions that execute in parallel across CAS worker nodes on in-memory data. They are invoked via the CAS language (CASL), PROC CAS, or through client APIs like swat (Python) or the R client.
Full explanation below image
Full Explanation
B is correct because CAS action sets (e.g., simple, regression, decisionTree, deepLearn) are server-side libraries of distributed analytics functions that execute in parallel across CAS worker nodes on in-memory data. They are invoked via the CAS language (CASL), PROC CAS, or through client APIs like swat (Python) or the R client. SAS procedures run on the SAS compute server, reading data from disk or SAS libraries sequentially. The distributed in-memory execution on CAS workers is the key differentiator enabling CAS action sets to scale to large datasets efficiently. A is wrong; action sets are not macros and do not run in the DATA step. C is wrong; execution architecture is fundamentally different. D is wrong; action sets are not Python class wrappers around SQL.