Alfresco Certified Administrator Practice Test. Form A

This Practice Test is designed to assist in the preparation to take the ACA exam.

This test has the same length as the Certification Exam and the conditions for testing such as time as also similar.

Architecture

Which one of the following services is available under a Community Support Package ? Select One.

Alfresco Support Handbook:

http://docs.alfresco.com/support/concepts/su-welcome.html

Support Comparison Matrix

 

Community

Starter/Business

Enterprise

Authorized Support Contacts

0

2

3

Documentation

Forums

Certified Binaries

 

Critical Alerts

 

Knowledge Base

 

Access to Phone/Web Support

 

Service Packs

 

M-F Customer Business Hour Support

 

24x7 Severity One Coverage

 

 

  • Critical Alerts
  • Knowledge base
  • Forums
  • Service Packs

Which of the following tools, allows to review which AMPs have been deployed in a customized Alfresco One instance?

Alfresco Module Packages are used to package Alfresco customizations and extensions for deployment. Use the Module Browser page to view all the AMPs that have been applied to Alfresco.

Click Admin Tools then Module Browser.

The Module Browser page shows a list of all the module packages that are either pre-configured in an out-of-the-box Alfresco installation or applied by the user, along with the description and version number.

  • Module Browser
  • Module Management Tool
  • Category Manager
  • Tag Manager

An user has delete a file. To which store will the file's metadata be moved into?

The Working Store (workspace://SpacesStore) contains the metadata for all active/live nodes in the Repository. This store is implemented using a database (RDBMS). 

The Content Store contains the physical files uploaded to the Repository and is located in the {Alfresco install dir}/alf_data/contentstore directory on the filesystem by default, but can also be configured to use other storage systems, for example, Amazon S3. It is also possible to define content store policies for storing files on different storage systems, effectively defining more than one physical content store. 

Whenever a node is deleted, the metadata for the node is moved to the Archive Store (archive://SpacesStore), which uses the configured database. The physical file for a deleted node is moved (by default after 14 days) to the {Alfresco install dir}/alf_data/contentstore.deleted directory, where it stays indefinitely. However, a clean-up job can be configured to remove the file at a certain point in time (referred to as eager clean-up).

When the versionable aspect is applied to a node, a version history is created in the Version Store(workspace://lightWeightVersionStore). Versioned node metadata is stored in the database and files remain in the {Alfresco install dir}/alf_data/contentstore directory. Versioning is not applicable to folder nodes.

The System Store is used to save information about installed Alfresco extension modules.

 

Source: http://docs.alfresco.com/5.1/concepts/dev-repository-concepts.html

  • The Archive Store
  • The Working Store
  • The Content Store
  • The System Store

Which one of the following Solr indexes is used for searching deleted content?

There are two cores or indexes in Solr:
  • WorkspaceStore: used for searching all live content stored at alfresco/solr4 within the Solr search server.
  • ArchiveStore: used for searching content that has been marked as deleted at alfresco/solr4 within the Solr search server.

Source: http://docs.alfresco.com/5.1/concepts/solr-overview.html

  • WorkspaceStore
  • DeletedStore
  • ArchivedStore
  • ContentdeletedStore

Which one of the following APIs can be use to develop Share Extensions? Select One.

On the platform (server side) you can add Java code and JavaScript code to extend the platform with new custom functionality such as Java Services, Repository Web Scripts, Actions, Scheduled jobs and more. These extensions are embedded in the Platform application and run in the same JVM as the Alfresco Platform. When developing platform extensions you use the Public Java APIand the Repository JavaScript API and Repository Freemarker Template API.

On the web client side you can extend Alfresco Share with new pages, dashlets, document library actions and more. These extensions are embedded in the Share web application and run in the same JVM as Alfresco Share. When developing Share extensions you use the Aikau Widget and Services Reference/API and the Spring Surf API.

Finally, you can also build stand-alone applications and web clients that talk to the Alfresco Repository remotely. These integrations will use the REST API.

Source: http://docs.alfresco.com/5.1/concepts/dev-api-intro.html

  • Java API
  • Repository JavaScript API
  • Repository FreeMarker Template API
  • Spring Surf API

After installing Alfresco Office Service an user can't directly archive emails into Alfresco using Microsoft Outlook©. Select one possible cause for this behavior.

Alfresco Outlook Integration allows you to use email and repository management without having to leave Microsoft Outlook.

Features of Alfresco Outlook Integration include the ability to directly archive emails into Alfresco, full metadata support, full search, tagging and workflow capabilities, and the ability to attach files and view archived emails in your inbox.

 

Source: http://docs.alfresco.com/outlook2.1/concepts/Outlook-overview.html

  • The Alfresco Outlook Integration is not installed
  • The Alfresco Office Services AMP file is missing
  • Protected view is deactivated in Office.
  • SSL is enabled

When using Google Docs to edit a document stored in Alfresco, an user can't use the Edit in Google Docs action but current open documents being edited will still be available using the Resume editing in Google Docs. What is the reason for this behavior?

Google Docs integration allows you to use Google Docs to edit document content stored in Alfresco, as an alternative to the online and offline editing capabilities in Alfresco Share.

When you use the setup wizards to install Alfresco, the Google Docs integration feature is applied and enabled for supported content in an Alfresco installation. 

If you install Alfresco manually, you need to apply the Google Docs AMP files separately to enable the feature.

The following properties can be configured for Google Docs integration in the alfresco-global.properties file: 

googledocs.enabled

Enables the Google Docs functionality. By default, this property is set to true. If you set this option to false, the Edit in Google Docs action will not be available. Documents that are currently being edited will still be available using the Resume editing in Google Docs action until they are saved or discarded.

googledocs.idleThresholdSeconds

Sets the idle time threshold in seconds. Additional Google users that you invite to collaborate on the document will be considered to be 'idle' after this period. The period is measured from the time when the user last made a change to the document. When saving documents back to Alfresco, or discarding changes, you must confirm that you want to disconnect any non-idle users before the action completes.

You can also set these properties in the Admin Console. See Google Docs™ Console

 

Source: http://docs.alfresco.com/5.1/concepts/googledocs-intro.html

 

  • The property googledocs.enabled is set to true.
  • The property googledocs.enabled is set to false.
  • The setup wizard was used to install Alfresco.
  • An AMP was used to deploy the Google Docs integration

A disaster occurs in a non-clustered environment, your Solr sharded indexes are lost. When recovering you find out that you cannot recover indexes from the backup. A cause for that might be:

  • Index backup is disable when Sharding is used.
  • Index backup file is corrupted

Which of the following Solr Core templates causes less duplication of the index, and therefore the index is more compact?

  • rerank
  • vanilla
  • without_suggest
  • tst

Alfresco One 5.1.1 with the Solr subsystem does not include any transactional indexing. What does that imply?

  • Alfresco and the database and indexes in perfect sync at all times
  • The Solr indexes are eventually consistent
  • Transactions are indexed right away.
  • The indexing behavior of each property is set in the content model.
  • By default, they properties are indexed atomically.

Which of the following features applies to Subsystem available in Alfresco One?

  • The same template spring configuration cannot be used with different parameters in different instances.
  • The subsystem does not have JMX-based server configuration capabilities
  • You do not need unique bean names if you use multiple instances of the same subsystem.
  • Implementation specifics are visible because beans are available in a private container
  • A subsystem binds its configuration settings to bean declarations

Which of the following features is not supported on Alfresco Community version?

  • Share
  • Enterprise Admin Console
  • Outlook Integration
  • Cloud Sync
  • Admin Tools

Managing the installation

What is the default encryption algorithm use to securely store passwords in Alfresco One?

Alfresco uses cryptographic password hashing technique to securely store passwords. 

All versions of Alfresco prior to Alfresco One 5.1.1 used the MD4 (Message Digest 4) and SHA256 hash algorithms (mainly to support NLTM and CIFS) to store critical data. But this is no longer considered a secure approach as the hashed password is very easy to decrypt. As an improvement, Alfresco One 5.1.1 can now use Bcrypt to store passwords but this is configurable. By default, the system uses MD4 to allow users to use MD4 hashed passwords for NTLM and CIFS authentication.

Bcrypt is an adaptive hash function based on the Blowfish symmetric block cipher cryptographic algorithm. It is incredibly slow to hash input compared to other functions, but this results in a much better output hash. Alfresco One 5.1.1 is configured to use a strength of 10 to provide a good compromise of speed and strength.

With Bcrypt, the hashing algorithm (also called an encoder) can be configured by setting the system.preferred.password.encodingproperty in the alfresco-global.properties file. The supported values for this property are:

  • md4
  • sha256
  • bcrypt10

If you provide a different value, the Alfresco repository won't start.

  • Bcrypt
  • md4
  • sha256
  • blowfish

Which of the following functions are provided by an authentication subsystem to Alfresco One?

An authentication subsystem provides the following functions to Alfresco:

  • Password-based authentication for web browsing, Microsoft SharePoint protocol, FTP, and WebDAV
  • CIFS file system authentication
  • Web browser, Microsoft SharePoint protocol, and WebDAV Single Sign-On (SSO)
  • User registry export (the automatic population of the Alfresco user and authority database)

Source: http://docs.alfresco.com/community/concepts/auth-subsystem-intro.html

  • SMB file system authentication
  • Password protected access using Share UI
  • User registry export (the automatic population of the Alfresco user and authority database)

When using an authentication subsystem there is no need to edit the web.xml file. Why?Select one.

The main benefits of the authentication subsystem are:

  • Subsystems for all supported authentication types are pre-wired and there is no need to edit template configuration.
  • There is no danger of compatibility issues between sub-components, as these have all been pre-selected. For example, your CIFS authenticator and authentication filter are guaranteed to be compatible with your authentication component.
  • Common parameters are shared and specified in a single place. There is no need to specify the same parameters to different components in multiple configuration files.
  • There is no need to edit the web.xml file. The web.xml file uses generic filters that call into the authentication subsystem. The alfresco.war file is a portable unit of deployment.
  • You can swap from one type of authentication to another by activating a different authentication subsystem.
  • Your authentication configuration will remain standard and, therefore, more manageable to support.
  • Authentication subsystems are easily chained

Source: http://docs.alfresco.com/5.1/concepts/auth-subsystem-intro.html

 

  • The web.xml file uses generic filters that call into the authentication subsystem.
  • The web.xml file is not longer used when an authentication subsystem is implemented
  • The web.xml file is protected
  • The web.xml file no longer contain the <security-constraint> section.

When setting up CIFS on a Windows server, why do requests aimed at Alfresco CIFS will fail if port 445 is left open?

CIFS on Windows works only with NetBIOS. 

The process CIFS uses on a supported Windows installation is:

  • The client sends a request to the CIFS server.
  • If the client wants to access a path that starts with the Windows server name, then the CIFS request will be handled by Windows CIFS.
  • If the path starts with the Alfresco CIFS server name, then the CIFS request will be handled by Alfresco CIFS.

The dispatching is made at the Windows-level by the NetBIOS Windows DLLs, however this dispatching is not available with native CIFS (port 445). 

If you leave port 445 open, requests aimed at Alfresco CIFS are routed to Windows CIFS and will fail. A CIFS client does not know in advance if a CIFS server listens on NetBIOS ports (137, 138, 139) or native CIFS port (445). It typically sends two connections requests: one to the NetBIOS ports and one to the native CIFS port. The faster request wins and, as native CIFS is typically faster, the connection is likely to fail.

Note:The Java CIFS code that Alfresco supports on Linux is not supported on Windows.

The drawback of using CIFS on a Windows server is performance degradation.

The supported process of using CIFS on Windows forces the clients to use NetBIOS to talk to Alfresco. NetBIOS is a protocol that is much less efficient and more chatty than the more recent native CIFS (port 445) protocol. An Alfresco CIFS setup on Windows will suffer performance issues when compared to a Linux/Unix system due to this chattiness.

Source: http://docs.alfresco.com/5.1/concepts/fileserv-subsystem-info.html

  • A CIFS client does not know in advance if a CIFS server listens on NetBIOS ports or native CIFS port.
  • A CIFS client only sends request to CIFS ports.
  • CIFS on Windows works only with NetBIOS.
  • An Alfresco CIFS setup on Windows will always suffer performance issues.

Which one of the following properties will only take effect on non-Windows servers, where the Java-based SMB implementation is used?

Java-based SMB properties 

The following properties will only take effect on non-Windows servers, where the Java-based SMB implementation is used.

cifs.broadcast

Specifies the broadcast mask for the network.

cifs.bindto

Specifies the network adapter to which to bind. If not specified, the server will bind to all available adapters/addresses.

cifs.tcpipSMB.port

Controls the port used to listen for the SMB over TCP/IP protocol (or native SMB), supported by Win2000 and above clients. The default port is 445.

cifs.ipv6.enabled

Enables the use of IP v6 in addition to IP v4 for native SMB. When true, the server will listen for incoming connections on IPv6 and IPv4 sockets.

cifs.netBIOSSMB.namePort

Controls the NetBIOS name server port on which to listen. The default is 137.

cifs.netBIOSSMB.datagramPort

Controls the NetBIOS datagram port. The default is 138.

cifs.netBIOSSMB.sessionPort

Controls the NetBIOS session port on which to listen for incoming session requests. The default is 139.

cifs.WINS.autoDetectEnabled

When true causes the cifs.WINS.primary and cifs.WINS.secondary properties to be ignored.

cifs.WINS.primary

Specifies a primary WINS server with which to register the server name.

cifs.WINS.secondary

Specifies a secondary WINS server with which to register the server name.

cifs.disableNIO

Disables the new NIO-based CIFS server code and reverts to using the older socket based code.

Source: http://docs.alfresco.com/5.1/concepts/fileserv-CIFS-javaprops.html

 

  • cifs.broadcast
  • cifs.serverName
  • cifs.sessionTimeout
  • cifs.serverName

Which one of the following conditions applies to the Alfresco CIFS server name (cifs.serverName) on Windows host?

cifs.serverName

Specifies the host name for the Alfresco CIFS server. If Alfresco is installed on a Windows server, the name of the machine must not exceed 14 characters and must be unique on the network. Use the special token ${localname} in place of the local server's host name and you can generate a unique name by prepending/appending to it, for example, ${localname}A. The combined ${localname} value must not exceed 15 characters.

On Windows systems, the value of this property must be different from the server's host name, it should resolve to the same IP address as the server, and must be different from any other host name on the network.

Source: http://docs.alfresco.com/5.1/concepts/fileserv-CIFS-props.html

  • The value of this property must be the same as the server's host name,
  • The name of the server must not exceed 16 characters
  • The value of this property should resolve to the same IP address as the host server
  • Use the special token ${localname} in place of the local server's

Which one of the following operations can NOT be performed using JMX ?

The Java Management Extension (JMX) interface allows you to access Alfresco through a standard JMX console that supports JMX Remoting (JSR-160). This lets you:

  • Manage Alfresco subsystems
  • Change log levels
  • Enable or disable file servers (FTP/CIFS)
  • Set server read-only mode
  • Set server single-user mode
  • Set server maximum user limit, including ability to prevent further logins
  • Count user sessions/tickets
  • User session/ticket invalidation

Source: http://docs.alfresco.com/5.1/concepts/jmx-intro-config.html

  • Enable or disable file servers (FTP/CIFS)
  • Set server single-user mode
  • Manage Alfresco subsystems
  • Debug JavaScript extensions

You can control the logging levels of classes within your module (deployed AMP) without having to modify the main log4j.properties file. Where in the class path shall these module's log4.properties file be stored?

Each module can have its own Apache Log4j properties file.

Each module can have its own log4j.properties file, which is placed in the same directory as module.properties. The collection oflog4j.properties files within all modules installed into the alfresco.war act collectively to augment/override the Alfresco webapp's global WEB-INF/classes/log4j.properties file.

You can control the logging levels of classes within your module without having to modify the main log4j.properties file; this also allows the logging configuration of a module to be handled cleanly by the Module Management Tool.

Given that {module.id} denotes the value of module.id set in module.properties, your log4j.properties file should be put in the following position within the source code directory structure of your module:

config/alfresco/module/{module.id}/log4j.properties

At deployment time, this file will be copied to:

WEB-INF/classes/alfresco/module/{module.id}/log4j.properties

Source: http://docs.alfresco.com/5.1/concepts/dev-extensions-modules-module-log4j.html

 

  • WEB-INF/classes/alfresco/extension/
  • $TOMCAT_HOME/shared/classes/alfresco/extension/
  • WEB-INF/classes/alfresco/module/{module.id}
  • WEB-INF/classes/alfresco/extension/module/{module.id}

When using the SDK which of the following files will contain the minimum configuration information necessary to display new properties defined in a custom content model?

  • Share UI Configuration:

 share-amp/src/main/resources/META-INF/share-config-custom.xml

  • Share UI Localization:

 share-amp/src/main/amp/config/alfresco/web-extension/messages/content-model.properties

  • Share UI Localization Deployment (Bootstrap) :

share-amp/src/main/amp/config/alfresco/web-extension/custom-slingshot-application-context.xml

Source: http://docs.alfresco.com/5.1/references/dev-extension-points-content-model-configure-ui.html

  • share-amp/src/main/alfresco/resources/META-INF/share-config-custom.xml
  • share-amp/src/main/amp/config/alfresco/web-extension/messages/content-model.properties
  • share-amp/src/main/amp/config/alfresco/web-extension/custom-slingshot-application-context.xml
  • share-amp/src/main/resources/META-INF/share-config-custom.xml

How is incoming unauthenticated e-mail handled by Alfresco? Select two.

Groups and permissions for email 

An email arriving at the Alfresco email server is unauthenticated. An authentication group, EMAIL_CONTRIBUTORS, must exist to allow permissions to be handled at a high level by the administrator.

When an email comes into the system, the only identification is the sender's email address. The user is looked up based on the email address.

  • If a matching user is not found, then the current user is assumed to be unknown, if unknown exists
  • If unknown does not exist, then the email is rejected as authentication will not be possible
  • If the user selected is not part of email contributor's group, then the email is rejected

The current request's user is set and all subsequent processes are run as the authenticated user. If any type of authentication error is generated, then the email is rejected. The authentication will also imply that the authenticated user may not have visibility of the target node, in which case the email is also rejected. Effectively, this means that the target recipient of the email does not exist, at least not for the sender.

The current default server configuration creates the EMAIL_CONTRIBUTORS group and adds the admin user to this group.

Source: http://docs.alfresco.com/5.1/concepts/email-groupspermissions.html

  • The e-mail is inmediatly rejected
  • If the sender's email address is not part of email contributor's group, then the email is rejected
  • If a matching sender's e-mail is not found, then the current user is assumed to be unknown, if unknown exists
  • If the recipient's e-mail is not part of email contributor's group, then the email is rejected
  • If a matching recipient's e-mail is not found, then the current user is assumed to be unknown, if unknown exists

Which of the following components of Alfresco One are non clusterable

Clusterable components

  • Share
  • Alfresco
  • Content store
  • Database

Non-clusterable amd replicable components

  • Transformation Server
  • Solr index
  • Solr 4 index

Source: http://docs.alfresco.com/5.1/concepts/alfresco-components.html

  • Solr 4 index
  • Content store
  • Database
  • Transformation Server
  • Share

Encryption is enable in an existing content store. What would be the state of the existing content vs new content added to the store? Select One.

Content encryption overview 

Use this information to understand Alfresco's implementation of content encryption using the Encrypted content store. 

Important:Once you make the decision to use Encrypted content store for content encryption, it is irrevocable. This is because when a document is written to this content store, it is encrypted. If you decide to revert to an unencrypted content store, the content cannot be decrypted.

Important:If Encrypted content store is enabled on an existing or upgraded Alfresco installation, only new content will be encrypted but any existing content will not be encrypted.

Alfresco cryptography process

The Encrypted content store provides content encryption at rest capability. This is done by scrambling plain text into cipher text (encryption) and then back again (decryption) with the help of symmetric and asymmetric keys. 

When a document is written to the Encrypted content store, the Encrypted content store uses symmetric encryption to encrypt the document before it is written to the wrapped content store. A new symmetric key is generated each time a document is written to the content store. This means that every document in the system is encrypted with a different symmetric key. Further more, asymmetric encryption (such as RSA) is used to encrypt/decrypt those symmetric encryption/decryption keys. The asymmetric encryption uses a master key which is selected from a set of configured master keys.

Alfresco uses a set of master keys, which are:

  • selected in a random fashion
  • stored in a password-protected keystore
  • can be retired, in the event of key theft or as part of a standard key retirement process. For more information, see Encryption-related JMX operations.

The repository knows which master key was used to encrypt a given symmetric key so that when a user reads a particular document, the repository can decrypt the symmetric key (using that master key) and then use the decrypted symmetric key to decrypt the document content.

Important:Alfresco does not store the master key you provide. Instead, we access it from the keystore. If Alfresco cannot access that key, it cannot decrypt the content. So, make sure you maintain the master key and Alfresco has access to it. Otherwise, you will not be able to read the content.

Source: http://docs.alfresco.com/5.1/concepts/encrypted-overview.html

  • Existing content is inaccessible and new gets encrypted.
  • All content existing and new gets encrypted.
  • Only new content will be encrypted but any existing content will not be encrypted.
  • Content stores can only be encrypted upon creation.

Which of the following tools helps install and manage modules packaged as AMP files?

Using the Module Management Tool (MMT) 

 

The Module Management Tool (MMT) helps install and manage modules packaged as AMP (Alfresco Module Package) files. These AMP files are applied to a target WAR file, for example, alfresco.war or share.war.

The MMT supports the following: installation of AMP files including upgrades to later versions, uninstallation of installed modules, and listing of currently installed modules.

Modules are packaged and installed as AMP files. An AMP file relates to a specific module and version. During the installation of an AMP file the module and version are taken into consideration.

The MMT program, alfresco-mmt.jar, is available in the bin directory of the Alfresco installation. 

Source: http://docs.alfresco.com/5.1/concepts/dev-extensions-modules-management-tool.html

 

  • The Java Foundations API
  • The Alfresco War file
  • The Admin Enterprise Console
  • The Module Management Tool (MMT)

Which one of the following installers is recommended when deploying Alfresco One in a clustered environment? Select one.

Installing 

 

This information helps you install Alfresco, additional software, and modules. The Alfresco products have different installers, so you should be aware of what installers are shipped with your product.

Alfresco One ships with three installers:

  • Alfresco One Installer: this is appropriate for the majority of users, and installs everything you require to run Alfresco. It corresponds to the installer used in previous versions of Alfresco.
  • Alfresco One Platform Installer: this installs the Alfresco repository, all required third party components (for example, ImageMagick), and links to a variety of developer and admin resources. If you have a clustered environment, you might want to use the Platform installer across these servers.
  • Alfresco One Share Installer: this installs Alfresco Share only, with its own Tomcat instance and the Share Services AMP. You might want to use the Share installer to connect to one or more repositories (that you have installed using the Platform installer).

    Note:Use the Share installer to connect to a repository that you installed using the Platform installer only. Other setups are not supported.

Alfresco Community Edition is designed to be deployed on a single server. As a result, it is shipped with a single Alfresco Community Edition Installer, which contains both the Alfresco Platform and Alfresco Share components. This is the same approach that is used in previous versions of Alfresco.

Depending on your system, you can install Alfresco using one of the following methods: 

  • Using a setup wizard, which contains the required software and components you need for evaluating Alfresco
  • Using a standard WAR file to deploy Alfresco in a production environment

Source: http://docs.alfresco.com/5.1/concepts/master-ch-install.html

 

  • Alfresco One Installer
  • Alfresco One Platform Installer
  • Alfresco One Share Installer
  • Alfresco war

Which one of the following is a content store provided by Alfresco?

  • NFS Content Store
  • Deleted Content Store
  • Caching Content Store
  • S3 Content Store

In order to configure Alfresco One to use LDAP server for authentication, which property should be specified to add a new authenticator?

  • ldap.settings
  • external.auth
  • authentication.chain
  • authentication.chain
  • ldap.out

Which of the following applications may be used to install AMP files?

  • install-module.sh
  • alfresco.mmt.jar
  • amptool.jar
  • alfresco-install.sh

Which one of the following conditions would be the cause of a failed user attempt to create a Smart Folder?

Smart Folders organize your content so that you can store files across your organization, but view them based on information requirement, not location.

Stored searches are shown in a folder tree, so that when a user opens a folder, a query is run and the results are displayed in a list. Files are also automatically classified when they are uploaded.

Smart Folders are installed as a core part of Alfresco, so there is no separate AMP file to install or upgrade. The Smart Folders function is disabled by default, and can be enabled in your alfresco-global.properties file by specifying smart.folders.enabled=true.

Folders are differentiated by icon:

  • Physical folder: Physical folder icon
  • Smart folder: Folder with a magnifying glass representing a Smart Folder

Using Smart Folders in this way helps you to manage your information; for example, where you have a number of sources of information, in a variety of folders. Content that might be related to, but not directly involved in your work is also retrieved, depending on the search criteria.

The Smart Folder structure is created by associating a Smart Folder Template with an Alfresco physical folder. Multiple Smart Folder structures can be defined in a single template. For every Smart Folder, the template defines a folder name, search, and filing criteria, along with other properties. New templates are typically defined and added by business analysts, and created by administrators.

The folder structure can be personalised by user, for example, if you create a folder called My Files, you can populate it with files relevant to each user.

Source: http://docs.alfresco.com/5.1/concepts/sf-intro.html

  • Smart Folders can only be created by Site Administrators.
  • The Smart Folder AMP has not be installed.
  • The Smart Folders function is disabled by default.
  • The site manager needs to create a template first.

An administrator wants to set server read-only mode but when attempting using JConsole to access the JMX Interface, it does not work. Which of the following situations may be an explanation to this problem?

By default, you can reconfigure Alfresco by shutting down the server, editing the relevant property in the configuration files, and then restarting the server. There are some support operations that can be performed on-demand at runtime without needing to restart the server.

The Java Management Extension (JMX) interface allows you to access Alfresco through a standard JMX console that supports JMX Remoting (JSR-160). This lets you:

  • Manage Alfresco subsystems
  • Change log levels
  • Enable or disable file servers (FTP/CIFS/NFS)
  • Set server read-only mode
  • Set server single-user mode
  • Set server maximum user limit - including ability to prevent further logins
  • Count user sessions/tickets
  • User session/ticket invalidation

Remote JMX functionality is disabled by default in Alfresco. You can enable JMX by setting the alfresco.jmx.connector.enabled property in thealfresco-global.properties file.

To enable the JMX server:

  1. Open the alfresco-global.properties file.
  2. Set the following property: alfresco.jmx.connector.enabled=true
  3. Save the file.

Source: http://docs.alfresco.com/4.2/tasks/jmx-disable.html

  • JConsole is not a supported console
  • The property: alfresco.jmx.connector.enabled is set to true
  • Remote JMX functionality is disabled by default
  • JConsole does not support JMX Remoting (JSR-160)

A registered user attempts to login for the first time and the login attempt fails. Which of the following considerations might explain this behavior?

Access to Alfresco One is licensed on a per user basis.

You can register any number of users in Alfresco (see Setting up Alfresco authentication and security) and a license is only consumed when the registered user logs in to Alfresco and is authorized.

You can see a list of users along with their authorization states on the Admin Console > Users and Groups > Users page. A registered user can have any one of the following states:

  • Never Authorized: Specifies that the user has been registered but never logged in to Alfresco.
  • Authorized: Specifies that the user has successfully logged in to Alfresco.
  • Deauthorized: Specifies that the Administrator has removed the user from the authorization list.

Source: http://docs.alfresco.com/5.1/concepts/license-process.html

  • The Administrator has removed the user from the authorization list.
  • The user license limit has been exceeded.
  • The user registration has expired.
  • The user already exists.

When upgrading from any version of Alfresco prior to Alfresco One 4.2 to 5.1.1 is recommended to delete the hazelcastConfig.xml file. Which of the following options justifies this?

  • Before upgrading, all files and configuration are backed up and then deleted.
  • Any customization(s) made, for example, creation of custom caches, might need to be reapplied using the new Alfresco One 5.1.1 clustering infrastructure.
  • This is a legacy file that is not longer supported.
  • Centralized configuration is now included within the alfresco.war deployment archive.