ACSCE-5X Sample Questions Answers

Use Luke to check the index for the document UUID, then check the index state of that UUID.

Look at the list of registered transformers to make sure the mime type of the uploaded document is transformable to text.

Verify the content model to make sure it was properly loaded into the repository.

Inspect the current upload script, we need to manually add the indexing for new mime types there.

Use FTS query language for defining the smart folder search.

Use CMIS query language for defining the smart folder search.

If you use WebDAV or CIFS only queries returning cm:content and subtypes should be used.

Don’t create filing rules that don’t match the query criteria for the folder.

Use Lucene query language for defining the smart folder search.

The fade delay in milliseconds for the action in the user interface.

The index id of the icon to be used for the action.

The index id of the action item in the data dictionary.

The ordering of the items in the action items in the display.

Dictionary.

Authentication.

Audit.

Search.

template

node.template

node.document

document

document.template

Aspects.

Types.

Constraints.

Rules.

Associations.

There is no difference, these two beans are identical.

The upper case bean is an AOP proxy, and injects auditing, security, and other features into the underlying service.

The lower case bean is an AOP proxy, and injects auditing, security, and other features into the underlying service.

The NodeService bean does not exist.

On the first login by the “admin” user.

Prior to installing Alfresco Content Services.

During the initial startup of the Alfresco Content Services repository.

During installation before the application server starts.

Define a datalist with the required properties and assign the datalist to each type or aspect through an association.

Define a global type which holds the common properties, then define an association from each type requiring the properties back to the global type.

Define and use the same property names in the different types that need those fields.

Define a base type which holds the common properties and have all the types that need those fields inherit from the base type.

Create an aspect and apply it as a mandatory aspect to all the types which need the properties.

helloworld

/example/test/helloworld

/example/test/helloworld.html

/example

NodeService

DictionaryService

ContentService

ModuleService

The index will only be consistent after a server restart.

The index will become consistent when there are no more transactions to index.

The index becomes consistent once a day when the index job runs.

The index can only be consistent when the Lucene index job eventually runs.

The path of the node is specified by the assocQName.

The path of the node contains the value of the cm:name property specified in the properties.

The name of the node and the path can be different.

By convention, the path and the name of the node should be kept consistent.

The property map must contain more than one value.

NodeService

PropertyService

NodePropertyService

DictionaryService

It depends on how the transformation was configured.

It is replaced by the transformed content item.

It is versioned and updated.

It remains untouched.

Mark a method in the extension with an @Auditable annotation.

Open a connection to the database and write the audit information to the audit tables.

Inject AuditComponent into the extension and call recordAuditValues.

Use the Alfresco REST API to record an audit event.

Call the Java Audit Service.

Returns a complete read only list of all associations.

Returns the list of all associations which can be changes and modified.

Returns the list of child associations which are read only.

Returns the list of child associations which can be changes and modified.

select * from cmis:item

select * from sys:base

select * from rule:rule

select * from bpm:package

select * from cm:person

Properties can be single or multi-valued.

Properties can be shared between objects.

Properties are untyped.

Properties are explicitly ordered.

url.templateArgs

url.args

arguments

args

Define a new “notify” aspect with a “multi” peer association. Create and register a policy behavior that, when content is updates, users can associate their content via this aspect. As associations are being made, the external notification request will be triggered.

Define a new “notify” aspect with no properties. Create and register a policy behavior that, if this aspect is present, will make the external notification request. Users can simply add this aspect to their content item.

Extend cm:content to provide an additional “notify” property. Create a policy behavior that will look at the “notify” property and, if set, make the external notification request. Users simply create cm:content items.

Extend sys:base to provide an additional “notify” property. Create a new policy that will look at the “notify” property and, if set, make the external notification request. Users can simply call an action against their content item.

A new class extended the BaseProcessorExtension class and a bean definition specified the name “qsvc”.

A class named “qsvc” extended the BaseProcessorExtension class and a bean with a parent of “qsvc” deployed this class.

A class named “qsvc” extended the BaseProcessorExtension class and a bean deployed this class.

A class extended the ScriptAPI class and a bean definition deployed this class.

LENGTH

REGEX

MINMAX

LIST

MAX