In SAS Viya, a data engineer uses the following CAS action call: cas.table.save(table={name='MYMODEL', caslib='MODELS'}, name='mymodel.sashdat', caslib='MODELS'); What does this accomplish?
Select an answer to reveal the explanation.
Short Explanation
Here's the deal — table.save writes the in-memory CAS table to a SASHDAT file in the caslib's backing store, so you can load it later. It doesn't make a SAS7BDAT export, register a model, or create a session.
Full Explanation
The correct behavior is that table.save persists the in-memory CAS table MYMODEL to a SASHDAT file in the MODELS caslib backing store, making it available for future sessions. The SAS7BDAT export option is wrong because the native CAS file format here is SASHDAT, not SAS7BDAT. The Model Manager registration option is wrong because table.save writes data to disk, not to the Model Manager registry. The new session option is wrong because this action persists data, not create sessions.