Refer to the exhibit. When Cisco UCS is configured, which filter must be added to the str_filter string to retrieve all discovered compute blades with two CPUs? `` from ucsm sdk.ucshandle import…

Question

from ucsm sdk.ucshandle import UcsHandle

handle = UcsHandle(hostname, username, password, port=80)
handle.login()
for blade in handle.query_classid("computeBlade",
 filter_str=" "):
 print(blade)
handle.logout()

Options

• A(num_of_cpus eq 2) and (discovery eq complete)
• B(num_of_cpus.x2 type-sum') and (discovery, 'complete1, type='sum')
• C(num_of_cpus eq <2) and (discovery eq more)
• D(num_of_cpus. '2', type-eq') and (discovery, 'complete', type='eq')

• A
  89% (31)
• B
  9% (3)
• D
  3% (1)

Explanation

Option A uses the correct UCS Python SDK filter syntax, which follows the pattern (attribute eq value) - num_of_cpus eq 2 filters for blades with exactly two CPUs, and discovery eq complete ensures only fully discovered (not mid-discovery) blades are returned, which is the standard UCS filter string format.

Option B is wrong because type='sum' is an aggregation operator, not an equality check - it would attempt to sum values, not filter for a specific count, and the syntax itself is malformed. Option C fails because eq <2 is not valid UCS SDK syntax; comparison operators like less-than require lt, not <, and discovery eq more is not a recognized discovery state. Option D is closest to valid syntax but reverses the argument order - the SDK expects (attribute eq value) not (attribute, value, type='eq'), which is not how query_classid filter strings work.

Memory tip: Think of UCS filter strings like plain English: (thing eq value) - attribute first, operator (eq, lt, gt) in the middle, value last, and always use and/or to chain conditions. If an answer uses commas and type= keywords inside the condition tuple, it's likely a distractor mimicking object-oriented syntax rather than the actual string format.

No community discussion yet for this question.