Question 11 — AZ-104 Practice Exam 5
For each feature statement, drag it to the appropriate boxes in the Correct Match column.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Available across the entire tenant | [Gap 1] |
| Supports Boolean, Integer, and String | [Gap 2] |
| Allows single value or multiple values | [Gap 3] |
| Permits user-defined free-form or predefined lists | [Gap 4] |
| Assignable to directory-synced users from on-prem AD | [Gap 5] |
| Can include a text description | [Gap 6] |
- On-prem synced users assignable
- RBAC role definition
- Tenant-wide availability
- Attribute description field
- Data types supported
- Multiplicity supported
- Value policy options
Correct answers
- Gap 1: Tenant-wide availability
- Gap 2: Data types supported
- Gap 3: Multiplicity supported
- Gap 4: Value policy options
- Gap 5: On-prem synced users assignable
- Gap 6: Attribute description field
Explanations
Correct Matches
Tenant-wide availability – Custom security attributes are available tenant-wide, so the capability applies across your directory.
Data types supported – They support Boolean, Integer, and String data types.
Multiplicity supported – Attributes support single value or multiple values.
Value policy options – Values can be user-defined free-form or chosen from predefined lists.
On-prem synced users assignable – You can assign custom security attributes to directory-synced users from on-premises AD.
Attribute description field – Each attribute can include a description to document its purpose.
Unused Item(s)
RBAC role definition – RBAC roles control permissions; they aren’t custom security attributes.