Alfresco ACSCE-5X actual dump : Alfresco Content Services Certified Engineer

You have created a Dashlet for Alfresco Share and deployed your files to the correct directory. You have then refreshed the Share web scripts, but the number of web scripts stays the same. Which of the following options could be causing this?

• A. Share needs to be restarted, refreshing web scripts is not enough.
• B. The cache on the browser needs to be cleared.
• C. You are using Internet Explorer; you should be using Firefox.
• D. Your files do not adhere to the standard naming convention.
• E. You did not register the dashlet with the data dictionary.

What is the difference between nodeService and NodeService in Alfresco Content Services?

• A. The NodeService bean does not exist.
• B. The upper case bean is an AOP proxy, and injects auditing, security, and other features into the underlying service.
• C. There is no difference, these two beans are identical.
• D. The lower case bean is an AOP proxy, and injects auditing, security, and other features into the underlying service.

Which of the following correctly describes the behavior of CMIS properties?

• A. Properties are explicitly ordered.
• B. Properties are untyped.
• C. Properties can be shared between objects.
• D. Properties can be single or multi-valued.

Choose the correct priority order in which Alfresco Content Services will load subsystem settings:

• A. JMX -> Alfresco global properties -> subsystem instance -> subsystem default
• B. Alfresco global properties -> JMX -> subsystem instance -> subsystem default
• C. Alfresco global properties -> subsystem default -> subsystem instance -> JMX
• D. JMX -> subsystem instance -> subsystem default -> Alfresco global properties

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.

• A. 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.
• B. 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.
• C. 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.
• D. 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.