Scenario: A Citrix Administrator changed all contractor user IDs to begin with the prefix 'con-'. Currently, SmartControl is used to restrict all contractor user access to peripherals. Which syntax…

Question

Options

• AUSER.IS_MEMBER_OF("con-")
• BUSER.NAME.STARTSWITH("con-")
• CUSER.NAME.CONTAINS("con-")
• DUSER.ATTRIBUTE("con-")

• A
  2% (1)
• B
  92% (46)
• C
  4% (2)
• D
  2% (1)

Explanation

USER.NAME.STARTSWITH("con-") is correct because it precisely matches usernames that begin with the prefix "con-", which is exactly what the administrator configured. In Citrix SmartControl policy expressions, STARTSWITH is the proper method for matching string prefixes, allowing the policy to target all contractor accounts without false positives.

Why the distractors fail:

• A. USER.IS_MEMBER_OF("con-") - This checks group membership, not username format. "con-" is a naming prefix, not a group name.
• C. USER.NAME.CONTAINS("con-") - This would match any username containing "con-" anywhere (e.g., "jconner", "accounting"), producing unintended matches beyond just contractors.
• D. USER.ATTRIBUTE("con-") - This references an LDAP/AD attribute by name, not a string operation on the username itself; "con-" is not an attribute name.

Memory tip: Think of it like a word search - STARTSWITH anchors to the beginning of the string (like a prefix tag on a badge), while CONTAINS searches anywhere in the string. When an admin enforces a naming prefix convention, always reach for STARTSWITH.

No community discussion yet for this question.