What is a description of a Cisco UCS Director script module?

Question

Options

• Afunction to convert internal workflow tasks into Python scripts
• Bplace to store custom workflow scripts, jars, and custom lists of values for use in custom workflow tasks
• Cplace to store external scripts that are not related to Cisco UCS Director
• Dplace to store imported scripts, Bash, and custom Python code for use in custom workflow tasks

• A
  2% (1)
• B
  93% (39)
• C
  5% (2)

Explanation

A script module in Cisco UCS Director is a container (library) used to organize and store custom workflow scripts, JAR files, and custom lists of values that power custom workflow tasks - making B correct. It acts as a reusable asset repository that custom tasks can reference during workflow execution.

Why the others are wrong:

• A is incorrect because a script module doesn't convert workflow tasks into Python scripts - that describes workflow automation in reverse; tasks invoke scripts, not the other way around.
• C is incorrect because script modules are specifically tied to UCS Director workflows, not external unrelated scripts.
• D is a tempting distractor but is wrong in the details: script modules do not store "imported scripts, Bash, and custom Python code" in that combination - Bash and Python aren't the defining content types; JARs and custom value lists are.

Memory tip: Think of a script module as a module shelf in a library - it's where you store and organize reusable custom scripts and resources (including JARs and value lists) so your custom workflow tasks can grab what they need off the shelf.

No community discussion yet for this question.