PRACTICE QUESTIONS AND ANSWERS TESTED
AND APPROVED NWELY MODIFIED 2025/2026
LATEST
You can run the following Analytics operations on documents indexed by a
conceptual index:
-- ANSWER--Analytics categorization sets
Clustering
Concept searching
Keyword expansion
Find similar documents
Securing an Analytics index -- ANSWER--If you want to apply item-level or
workspacelevel security to an Analytics index, you must secure both the
Analytics Index object and the Search Index object for that particular index.
Restricting a group from viewing an Analytics Index does not restrict them from
searching on the index unless access to the corresponding Search Index is also
restricted.
If you're applying item-level security from the Search Indexes tab, you may
need to create a new view and add the security field to the view.
Page 1 of 100
,Analytics index console operations -- ANSWER--Once you save the Analytics
index, the Analytics index console appears. From the Analytics index console,
you can perform the following operations:
Populating the index
Monitoring population/build status
Retrying exceptions
Viewing conceptual index document exceptions
Showing population statistics
Showing index statistics
Population statistics and index statistics are only available for conceptual
indexes.
Populating the index -- ANSWER--To populate the Analytics index on the full
set of documents, click Run on the Analytics Index console, then choose Full
from the modal that appears. This adds all documents from the data source and
training data source to the readyto-index list. Document "preprocessing" also
occurs to clean up text. This includes the following:
Numbers and symbols are ignored.
All words are made lowercase.
Page 2 of 100
,Filters found under Advanced Settings are applied (for example, email header
filter).
Once population is complete, the index builds.
If you have access to SQL, you can change the priority of any Analytics index-
related job
(index build, population, etc.) by changing the value on the Priority column in
the ContentAnalystIndexJob database table for that index. This column is null
by default, null being the lowest priority. The higher you make the number in
the Priority column, the higher priority that job becomes. When you change the
priority of a job while another job is in progress, Analytics doesn't stop the in-
progress job. Instead, the job will finish before starting on the new highest
priority.
Incremental population -- ANSWER--Once population is complete, you have
the option to populate incrementally to account for new or removed documents
from the data source and training data source on the ready-to-index list. To
perform an incremental build, click Run on the console, then choose
Incremental from the modal that appears.
If, after building your index, you want to add any documents that were
previously excluded from training back into the training data source document
pool, you must disable the Optimize training set field on the index and perform
another full population. An incremental population does not re-introduce these
previously excluded documents.
Page 3 of 100
, Incremental population automatically triggers a rebuild of the classification
index.
Documents greater than 30 MB -- ANSWER--Analytics indexes automatically
suppress documents greater than 30 MB before sending them to the Analytics
engine. Suppressed large documents will appear in the Document Exceptions.
You can also view suppressed documents from the Document list by using the
Excluded from Training and Excluded from Searchable Set choices on the
Analytics Index Document field.
Building the index -- ANSWER--Once population is complete, the index will
build automatically. During this phase, training data source documents and
Latent Semantic Indexing (LSI) are used to build the concept space based on the
relationships between words and documents. Data source documents are
mapped into the concept space, and stop words (very common words) are
filtered from the index to improve quality.
Please note that the index is unavailable for searching during this phase.
If an Analytics index goes unused for 15 days, it is automatically disabled to
conserve server resources. It then has a status of Inactive and is not available for
use until it is activated again. This setting is determined by the
MaxAnalyticsIndexIdleDaysentry in the Instance setting table. The default
value for this entry can be edited to change the number of maximum idle days
for an index.
Page 4 of 100