A client recently purchased the Smart Content Service and is considering using the Enhanced Smart Tagging feature. As part of the process, the client recently created a new tagging taxonomy that has…

Question

Options

• AAdd sample assets to a new folder, tag assets in folder, then enable Smart Tagging via the folder
• BAdd sample assets to a new folder, tag assets in folder, then run the Smart Tags Training workflow
• CEnable Smart Tagging via the folder properties for a single folder of assets, then run the Smart
• DEnable Smart Tagging via the folder properties for a single folder of assets

• A
  3% (1)
• B
  16% (6)
• C
  73% (27)
• D
  8% (3)

Explanation

Option C is correct because demonstrating Enhanced Smart Tagging on a subset of assets requires two distinct steps in the proper sequence: configuring Smart Tagging at the folder level to scope the operation to just that subset, then running the Smart Tags Training workflow so the AI model learns the custom taxonomy and can auto-tag assets within that folder.

Why the distractors are wrong:

• A enables Smart Tagging after manually tagging assets but skips the Smart Tags Training workflow entirely - the model never learns the custom taxonomy, so it can't apply smart tags automatically.
• B manually tags assets and runs the training workflow but never enables Smart Tagging via folder properties, which is required to associate the training scope with that specific folder subset.
• D only enables Smart Tagging on the folder without ever running the training workflow - the AI model has no knowledge of the new taxonomy and cannot function with it.

Memory tip: Think "Configure, then Train" - folder properties configure where Smart Tagging applies (the subset), and the Training workflow trains the model on the custom taxonomy. Skipping either step breaks the feature; swapping the order loses the folder scoping that limits it to a demo subset.

No community discussion yet for this question.