Which statement is true regarding SAS packages created in SAS Data Integration Studio?

Question

Options

• ASAS packages are used to import and export SAS applications.
• BSAS packages are used to import and export stand-alone SAS programs.
• CSAS packages are used to import and export third-party metadata.
• DSAS packages are used to import and export SAS metadata.

• B
  4% (1)
• C
  4% (1)
• D
  92% (22)

Explanation

SAS packages in SAS Data Integration Studio are specifically designed to import and export SAS metadata - the repository objects like jobs, tables, transformations, and source/target definitions stored in the SAS Metadata Server. This makes D correct.

• A is wrong because SAS packages don't handle "SAS applications" as a distinct category - application deployment is a separate concept.
• B is wrong because stand-alone SAS programs (.sas files) are flat files managed through the filesystem, not packaged via the metadata layer.
• C is wrong because SAS packages are specific to the SAS metadata ecosystem; third-party metadata would require different tools or ETL processes.

Memory tip: Think of the word "package" as wrapping up your SAS metadata - just like shipping a box of blueprints (metadata = the design/structure), not the physical goods themselves. When you move a DI Studio job between environments, you're moving metadata, not raw code or external data.

No community discussion yet for this question.