After creating a stored process from a SAS Data Integration Studio job, how can you test the stored process to make sure it runs correctly?

Question

Options

• AExecute the stored process in SAS Data Integration Studio.
• BExecute the stored process in SAS Management Console.
• CExecute the stored process using the SAS Add-In for Microsoft Office or SAS Enterprise Guide.
• DExecute the stored process using SAS Display Manager's Stored Process Test window.

• A
  4% (1)
• B
  4% (1)
• C
  82% (23)
• D
  11% (3)

Explanation

Option C is correct because after publishing a stored process from SAS Data Integration Studio, the standard way to execute and test it is through client applications designed to run stored processes - SAS Enterprise Guide and the SAS Add-In for Microsoft Office both provide interfaces to browse the metadata repository, find the stored process, run it with parameters, and inspect the output. Option A is wrong because SAS Data Integration Studio is an ETL design tool, not a stored process execution client - you build and deploy from it, not test stored processes in it. Option B is wrong because SAS Management Console is an administration tool for managing metadata, users, and servers; it doesn't execute stored processes. Option D is wrong because SAS Display Manager has no dedicated "Stored Process Test window" - this is a fabricated distractor. Memory tip: Think of the workflow as "build → deploy → test": you build in DI Studio, deploy to the metadata server, then test through an end-user client like Enterprise Guide or the Office Add-In - the same tools your end users would run it from.

No community discussion yet for this question.