|Exam Name||:||Alfresco Content Services Certified Engineer (ACSCE)|
|Questions and Answers||:||87 Q & A|
|Updated On||:||Click to Check Update|
|PDF Download Mirror||:||ACSCE-5X Brain Dump|
|Get Full Version||:||Pass4sure ACSCE-5X Full Version|
Which tasks would require a restart of the Alfresco server to apply the changes? (Choose two.)
Deploying a new content model via a *-context.xml file.
Deploying a new content model into Data Dictionary/Models.
Deploying a new workflow through the Activiti workflow console.
Making configuration changes in alfresco-global properties.
Making configuration changes via JMX.
Select the element that will allow any node to be included as part of a peer association:
Which one of the following statements about aspects is TRUE?
Aspects can only be applied to "cm:content".
An aspect can have a type as a parent.
An aspect may not include associations.
Aspects can inherit from other aspects.
When testing an Alfresco Content Services extension under high levels of concurrency, you notice that some transactions are failing due to locking issues with the database. What is an appropriate way to resolve this?
Manually unlock the offending records and start the testing again.
Directly use Alfresco’s database connection pool and write your own SQL.
Use the RetryingTransactionHelper to retry code that fails due to locking.
Rewrite the queries used by your application to reduce the chance of the lock.
What does it mean when it is said in Solr indexing that the index is "eventually consistent"?
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.
You have been tasked to develop a solution that will notify an external system when updates are made to certain documents. These documents can be of any type and the content authors will make the decision if the document needs this "notification" functionality. Select the simplest combination steps that will implement this solution.
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 notificationrequest 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.
How should Smart Folders be identified and recognized?
Smart Folders should be recognized by their type smf:smartFolder
Smart Folders should be recognized by parent-child type used smf:contains
Smart Folders should be recognized by their aspect smf:smartFolder
Smart Folders should be recognized by the special node reference used.
Smart Folders cannot be recognized as they are not different from any other cm:folder.
If an object is moved to a different folder, what will happen to the node’s security permissions?
It will inherit the ACL from the new parent folder.
It will inherit the ACL from the user who is moving it.
It will inherit the system wide ACL.
It will keep its old ACL.
Which of the following is not an Alfresco-supplied subsystem category?