A SAS administrator has performed the "Clear Projects" action to remove the lock on a SAS Data Integration Studio job called "Create Tables" that some user has checked out in their project…

Question

Options

• AIt will become empty and all new and checked out metadata objects will revert to the not checked
• BIt will only contain the new metadata objects. All checked out metadata objects will revert to the
• CIt will become empty and the DI job called "Create Tables" will no longer be in a checked out
• DIt will become empty and will not be accessible until the administrator grants permissions for it to

• B
  4% (2)
• C
  94% (46)
• D
  2% (1)

Explanation

Performing Clear Projects in SAS Data Integration Studio completely empties the targeted user's project repository, which simultaneously releases the checkout lock on any objects held there - so the "Create Tables" job is no longer in a checked-out state and is available again to other users. This is exactly what option C describes.

Why the distractors fail:

• A is wrong because it implies objects "revert" to a non-checked-out state while still being accessible, but the project is entirely emptied - nothing is preserved or reverted, it's simply gone.
• B is wrong because it claims new (not-yet-promoted) objects remain in the project; in reality, the entire project is cleared, including any newly created objects.
• D is wrong because Clear Projects does not alter permissions - the repository becomes empty, but the user retains their existing access rights and can continue using it immediately.

Memory tip: Think of "Clear Projects" as a full reset, not a selective undo - it's a nuclear option that wipes the project entirely clean, which as a side effect drops all locks. If an option says anything remains in the project after this action, it's wrong.

No community discussion yet for this question.