When exporting a SAS package file using SAS Data Integration Studio, where can it be saved?

Question

Options

• Ain metadata
• Bon any machine that SAS Data Integration Studio can write to
• Cin a SAS catalog
• Donly on the machine where SAS Data Integration Studio is running

• B
  95% (35)
• C
  3% (1)
• D
  3% (1)

Explanation

When exporting a SAS package file in SAS Data Integration Studio, the destination is any machine the application can write to - including network shares, mapped drives, or remote file systems - because package files are simply files on a filesystem, not metadata objects. Option A is wrong because metadata stores repository objects (jobs, tables, etc.), not exported package files themselves. Option C is wrong because SAS catalogs store SAS-specific entries like formats and macros, not package exports. Option D is wrong because it unnecessarily restricts the destination to the local machine, which contradicts the tool's design for sharing packages across environments. Memory tip: Think "package = portable file" - if SAS DI Studio has write permission to a path, it can drop the package there, just like saving any file to any accessible location.

No community discussion yet for this question.