ACSCE-5X Alfresco Content Services Certified Engineer Questions and Answers

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.

The server will refuse to start up and you must review the alfresco.log.

There are no effects upon nodes that have the “xyz” property.

You can still access values for property “xyz”, but it is a residual property.

The values for “xyz” disappear as though they never existed.

Exclusive

Parallel

Inclusive

Fork

Join

region

family

type

url

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.

JMX -> subsystem instance -> subsystem default -> Alfresco global properties

Alfresco global properties -> subsystem default -> subsystem instance -> JMX

JMX -> Alfresco global properties -> subsystem instance -> subsystem default

Alfresco global properties -> JMX -> subsystem instance -> subsystem default

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.

select * from cmis:item

select * from sys:base

select * from rule:rule

select * from bpm:package

select * from cm:person

template

node.template

node.document

document

document.template

Setting the labels for fields on the “Search” dialog.

Enabling and defining Smart Folder Templates.

Changing the FreeMarker template that controls the display of a field.

Grouping fields into sets on the “Edit Metadata” page.