The purpose of change management in SAS Data Integration Studio is to manage:

Question

Options

• Ametadata objects across metadata servers
• Bmetadata objects within a logged on user's personal folder
• Cmetadata objects within a metadata server
• Dmetadata objects within a logged on user's Checkouts Tree

• A
  5% (1)
• C
  95% (19)

Explanation

Change management in SAS Data Integration Studio is scoped to a single metadata server, allowing teams to track, version, and control modifications to metadata objects (jobs, tables, transformations, etc.) within that server's repository. Option A is wrong because change management does not span across multiple metadata servers - it operates within one. Option B is wrong because personal folders are just organizational containers, not the scope of change management governance. Option D is a tempting distractor because the "Checkouts Tree" is a real change management concept (it holds objects you've checked out), but it's a mechanism within the system, not the overall scope being managed.

Memory tip: Think of a metadata server as a single "library" - change management tracks who borrowed which books and what edits they made inside that one library, not across a library network (A), not in someone's personal bag (B), and not just in the checkout slip file (D).

No community discussion yet for this question.