Free ACSCA Practice Test Questions and Answers (2026)

Both Cloud Sync and Clustering are features exclusive to the enterprise-grade Alfresco Content Services (ACS) and are not supported in the Alfresco Community Edition. Clustering is a fundamental architectural feature providing high availability and scalability, which is essential for mission-critical enterprise deployments. Cloud Sync is a specific capability for synchronizing content between an on-premise instance and the Hyland Cloud, enabling hybrid cloud scenarios. The absence of these features represents key differentiators between the two editions.

A. share: Alfresco Share is the default web client and a core component available in both Alfresco Community and Enterprise editions for content management and collaboration.

C. Admins Tools: The Admin Console and other essential administrative functionalities are included in the Alfresco Community Edition for system management, though ACS offers more advanced tools.

1. Hyland Alfresco Documentation. (2023). Alfresco Content Services vs. Alfresco Community Edition. In Alfresco Content Services 7.4 Documentation. The official comparison table explicitly lists "High availability - clustering" and "Alfresco Cloud Sync" as features available only in Alfresco Content Services (Enterprise) and not in Alfresco Community Edition. The table also confirms that "Alfresco Share" and "Admin Console" are available in both editions. See the sections on "High availability and scalability" and "Hybrid cloud".

The statement "does not include any in-transaction indexing" means that the process of updating the SOLR search index is separate and asynchronous from the database transaction that commits the content or metadata changes. When a user saves a change, the database is updated immediately within a transaction. The indexing subsystem then picks up this change at a later point to update the SOLR index. This inherent delay between the repository state and the index state means the system is eventually consistent; search results will eventually reflect the latest changes, but not instantaneously.

A. The indexing behavior of each property is set in the content model.

This is a true statement about Alfresco configuration but does not explain the implication of the indexing timing. It defines what is indexed, not when.

B. By default, the properties are indexed automatically.

This describes the default configuration, not the consistency model. Automatic indexing can still be asynchronous and eventually consistent.

D. Transactions are indexed right away.

This is the direct opposite of the premise. "No in-transaction indexing" explicitly means that indexing does not happen immediately with the transaction commit.

---

1. Alfresco Content Services 7.4 Documentation, "Search service overview": "Alfresco Full Text Search is based on Solr. It is eventually consistent. This means that there is a small delay between the time the content is created or updated in the repository and the time it is available in the search results." This directly confirms that the lack of in-transaction indexing leads to eventual consistency.

2. Alfresco Content Services 7.4 Documentation, "Transactional metadata query": This section contrasts database queries with search-based queries, stating: "The search-based queries are eventually consistent. This means that the information in the search index is not updated immediately." It further explains that for immediate consistency, one must use transactional metadata queries against the database, reinforcing the asynchronous nature of SOLR indexing.

The Alfresco audit framework includes the AuditFilter interface, which is specifically designed to intercept and evaluate audit events as they are generated. An implementation of this interface can be configured to reject certain events based on specific criteria, preventing them from being passed to any audit applications for processing or storage. This allows for fine-grained control over which activities are audited, helping to reduce storage overhead and noise in the audit trail by filtering out irrelevant or low-value events before they are ever persisted.

A. Audit applications are consumers of audit data. They define how the data is processed and stored (e.g., in a database or log file), but they do not reject events at the source.

B. The Audit service is the central component that orchestrates the audit process, but the specific mechanism for filtering and rejecting events is the AuditFilter, making D the more precise answer.

C. An Audit data producer is responsible for generating audit data for specific events (e.g., login, node creation). It does not have a role in filtering or rejecting events.

1. Alfresco Content Services 7.0 Documentation, Auditing technical overview: In the section describing the audit architecture, it states, "The AuditFilter interface can be used to reject audit events produced so that their values are never used by audit configurations." This explicitly confirms the role of audit filters in rejecting events.

Source: Alfresco Community Edition 7.0 Documentation, Administering -> Auditing -> Auditing technical overview.

2. Alfresco Public API JavaDocs: The org.alfresco.repo.audit.AuditFilter interface contains the method boolean isEnabled(Map auditMap). The implementation of this method determines whether the event (represented by the auditMap) is enabled (i.e., not rejected) for auditing.

Source: Alfresco Repository Public API, org.alfresco.repo.audit.AuditFilter interface documentation.

The Alfresco authentication chain processes requests by trying each configured subsystem in a defined sequence. When an authentication request (including one for SSO) is received, the chain is traversed until one subsystem successfully authenticates the user. At that point, the process stops. An SSO authentication event is handled by a single, specific subsystem (e.g., Kerberos, External) within the chain; it is not "targeted at multiple subsystem instances" for a single authentication attempt. This sequential, first-success-wins model is fundamental to the chain's operation.

A. CIFS file system authentication is a core function provided by authentication subsystems such as NTLM and Kerberos, which are designed to integrate with Windows-based network environments.

C. This is a primary function. Subsystems like alfrescoNtlm and ldap-ad are explicitly designed to handle username/password authentication for Alfresco's various protocols and endpoints.

D. This describes user/group synchronization. Subsystems that connect to external directories (e.g., LDAP, Active Directory) are responsible for both authentication and synchronizing user data into the Alfresco database.

1. Alfresco Content Services 7.4 Documentation, "Authentication subsystems": This section provides an overview of authentication subsystems, stating their purpose is to provide authentication and user registry export (synchronization). It lists various protocols they support, including CIFS, FTP, WebDAV, and the SharePoint Protocol.

Reference: Alfresco Content Services 7.4 > Administering > Managing authentication and security > Authentication subsystems.

2. Alfresco Content Services 7.4 Documentation, "Chained authentication": This document explicitly describes the sequential nature of the authentication chain. It states, "Alfresco supports a chain of authentication subsystems... Alfresco will try to authenticate a user against each of the subsystems in the chain, in order, until it finds one that can successfully authenticate the user." This directly contradicts the concept in option B.

Reference: Alfresco Content Services 7.4 > Administering > Managing authentication and security > Chained authentication.

3. Alfresco Content Services 7.4 Documentation, "Configuring authentication subsystems": This page details the properties for configuring the authentication chain (authentication.chain). The examples for SSO (like Kerberos) show the SSO-specific subsystem placed at a single point in the chain, reinforcing that it is one step in a sequence, not a parallel target.

Reference: Alfresco Content Services 7.4 > Administering > Managing authentication and security > Configuring authentication subsystems.

The Alfresco Module Management Tool (MMT) is a command-line utility (alfresco-mmt.jar) specifically designed to manage Alfresco Module Packages (AMPs). Its primary functions are to install new modules into an Alfresco WAR file (e.g., alfresco.war, share.war), list the modules that are currently installed, and uninstall modules. This tool is essential for applying customizations, add-ons, or patches that are distributed in the AMP format. It directly modifies the web application archive to include or remove the module's files.

A. The Environment Validation Tool (EVT) is used to check if a server environment meets the prerequisites for an Alfresco installation or upgrade, not for managing modules.

B. The Alfresco Support Tool (AST) is used to collect system information, logs, and configuration details into a single ZIP file for troubleshooting with Alfresco Support.

D. The Alfresco Java Foundations API (AJF) is a set of Java APIs for developers to build customizations, not a tool for installing pre-packaged modules.

1. Alfresco Content Services 7.4 Documentation: Using the Module Management Tool (MMT). This section explicitly states, "The Alfresco Module Management Tool (MMT) is a command-line tool that installs and manages modules that are packaged as AMP (Alfresco Module Package) files."

2. Alfresco Content Services 7.4 Documentation: Installing an Alfresco Module Package. This guide provides step-by-step instructions on using the MMT, detailing the install command: java -jar alfresco-mmt.jar install .

3. Alfresco Content Services 7.4 Documentation: Alfresco Support Tools. This page describes the Alfresco Support Tool (AST) and its purpose for gathering diagnostic data, distinguishing it from the MMT. It also briefly mentions the Environment Validation Tool (EVT).

The Alfresco Synchronization Service operates by replicating changes from an on-premise Alfresco Content Services (ACS) instance to the cloud. For this to function, two core capabilities are required. First is the Synchronization feature itself, which manages the replication process. Second, the service must be aware of what content has been created, updated, or deleted. This is achieved through an event-driven model where the on-premise repository publishes change events. This mechanism of tracking and recording changes is functionally an Audit capability, providing a trail of events that the Synchronization service consumes to keep the repositories in sync.

A. Synchronization & Multi-tenancy feature.

Multi-tenancy is an architectural feature for hosting separate, isolated organizations on a single instance. It is not a prerequisite for the on-premise system to synchronize with the cloud.

C. Synchronization & Authentication feature.

While authentication is mandatory for establishing a secure connection between the on-premise and cloud systems, the question focuses on the components for the content synchronization logic. The core logic relies on tracking changes (auditing), whereas authentication is a general prerequisite for any remote system communication.

D. Synchronization & Transformation Services feature.

Transformation Services are used to create renditions of content (e.g., PDF previews). They are not a requirement for the fundamental process of synchronizing the original source files between repositories.

1. Alfresco Content Services Documentation, Alfresco Sync Service 3.4, "Sync Service overview": This document describes the architecture, stating, "The repository is configured to send messages to a message queue... when content is created, updated, or deleted. The Sync Service consumes messages from the queue...". This event stream of content changes serves as the audit trail required for synchronization.

2. Alfresco Content Services Documentation, Alfresco Sync Service 3.4, "Configuring Sync Service": The configuration details show properties for connecting to the source and target repositories. While authentication properties (sync.target.auth.) are present and required for the connection, the fundamental logic of synchronization depends on the event messages detailing content changes, which aligns with the concept of an audit trail.

3. Alfresco Content Services Documentation, "Audit Service": The official Audit Service documentation explains its purpose is to "log a complete trail of all the activities that are performed on a record". The Synchronization Service relies on a similar, purpose-built trail of activities specifically for content changes to perform its function. The exam question uses "Audit feature" to refer to this required change-tracking capability.

The upgrade from Alfresco's SOLR1.4 to SOLR4 search subsystem requires a complete re-indexing of the repository content to build the new SOLR4-compatible indexes. To maintain search availability during this potentially long process, Alfresco is designed to keep the existing SOLR1.4 subsystem active for handling queries. Consequently, only the functionalities supported by SOLR1.4 are available to users. Advanced features introduced with SOLR4, such as improved filtered searches and facets, will only become functional after the re-indexing is complete and the system has been switched over to use the new SOLR4 index.

A. While facet configuration is required, its absence would affect specific filters, not disable the entire filtered search capability, which is the symptom described.

B. Index corruption is a possible failure but not the expected, designed behavior of the upgrade process. It would likely result in broader search errors, not just missing features.

D. This statement is factually incorrect. SOLR4 offers significantly enhanced filtering and faceting capabilities compared to its predecessor, SOLR1.4.

1. Alfresco One 5.0 Documentation, "Upgrading from Solr 1.4": This official documentation outlines the migration process. It states, "When you install Solr 4, the Solr 4 search subsystem is not enabled by default. The existing Solr 1.4 subsystem continues to serve search queries until the Solr 4 indexes are built." This confirms that the system falls back to the older search service during the re-indexing phase. (Source: Alfresco One 5.0 Documentation, Administering -> Search -> Solr 4 search subsystem -> Upgrading from Solr 1.4).

2. Alfresco Content Services 6.2 Documentation, "Upgrading Search": While for a newer version, the principles of major search version upgrades are consistent. The documentation for upgrading search subsystems emphasizes that a full re-index is necessary when the underlying index format changes significantly, as it does between SOLR1.4 and SOLR4. During this re-index, the new subsystem is not yet active. (Source: Alfresco Content Services 6.2 Documentation, Upgrading -> Upgrading search).

Alfresco Subsystems are self-contained, configurable modules that operate within their own isolated Spring Application Context. This context is a child of the main Alfresco application context. Because each subsystem instance has its own private container for its beans, bean names do not need to be globally unique across the entire application. They only need to be unique within the scope of that specific subsystem instance. This architectural design is what prevents bean name collisions and allows for multiple, independent instances of the same subsystem type (e.g., multiple LDAP configurations) to coexist.

A. Subsystems are specifically designed to be manageable via Java Management Extensions (JMX), allowing for dynamic, runtime server configuration and monitoring.

B. A primary feature of subsystems is the ability to use a single template Spring configuration to create multiple instances, each with its own distinct parameters.

D. The use of a private container for beans serves to encapsulate and hide implementation specifics from the global context, not make them visible.

1. Alfresco Content Services 7.4 Documentation, "Subsystems": This official documentation describes the core architecture. It states, "Each subsystem has its own isolated Spring application context... This means that you can have multiple instances of a subsystem, each with its own configuration." This directly supports the correctness of option C and refutes option B.

Reference Section: "Subsystems" overview.

2. Alfresco Content Services 7.4 Documentation, "Managing subsystems": This section details the JMX-based management capabilities. It explicitly states, "Subsystems are manageable via JMX... You can view and change the settings for a subsystem while the Alfresco Content Services server is running." This directly refutes option A.

Reference Section: "Managing subsystems".

3. Alfresco Content Services 7.4 Documentation, "Subsystem configuration files": This page explains how subsystem instances are created from categories (templates). It notes, "A subsystem category is a type of subsystem. It is a template for creating one or more subsystem instances with the same or different settings." This further reinforces why option B is incorrect.

Reference Section: "Subsystem configuration files".

In Alfresco's workflow engine, which is based on the BPMN 2.0 standard, the element is the root container for a single process definition. The id attribute is mandatory as it serves as the unique identifier for the process definition. The process engine uses this id to manage, reference, and instantiate the workflow. While a name attribute is often included for human-readable display in the user interface, it is not a mandatory requirement for the engine to function. The id is the critical key for the engine's internal operations.

A. Name: This attribute is a user-friendly display label for the workflow. It is optional and not required for the process engine's execution.

C. UUID: While a UUID could be used as the value for an id, "UUID" itself is not a required attribute of the element.

D. Bean ID: This refers to a Spring bean identifier, which is used within service tasks or listeners to invoke custom Java logic, not as an attribute of the main element.

1. Object Management Group (OMG), Business Process Model and Notation (BPMN) Version 2.0.2, Document Number: formal/2013-12-09:

Section 10.2.1, "Process": Table 10.3, "Process Attributes," explicitly lists the id attribute with a multiplicity of "1," indicating it is required. The name attribute is listed with a multiplicity of "0..1," indicating it is optional.

2. Alfresco Content Services 7.4 Documentation, "Process definitions":

The documentation states, "A process definition is an XML file that defines the structure of a process. It follows the BPMN 2.0 standard." All provided examples of the element consistently include the id attribute, such as . This reinforces that the id is a fundamental part of the definition used by the engine.

3. Alfresco Content Services 7.4 Documentation, "Deploying a process definition":

This section notes: "The process definition is an XML file that follows the BPMN 2.0 standard. The file name must end with .bpmn20.xml and the process ID in the XML must be unique." This highlights the functional requirement and uniqueness constraint of the process id for deployment and management.

The single source of truth for a live, running Alfresco Content Services (ACS) system is the set of Java Management Extensions (JMX) MBeans exposed by the application. JConsole is a standard JMX client that connects to the running Java Virtual Machine (JVM) and allows an administrator to inspect these MBeans in real-time. This provides the actual, in-memory values of all repository properties as the application is currently using them, after all configuration files (like alfresco-global.properties), environment variables, and system property overrides have been applied. It reflects the definitive current state, not just the static configuration.

A. alfresco-global.properties: This is a static configuration file. Its values are read at startup but can be overridden by other mechanisms, so it may not reflect the live operational state.

C. repository.properties: This file, located within the Alfresco WAR, contains the system's default property values, which are intended to be overridden by alfresco-global.properties for any specific installation.

D. slingshot.properties: This file contains configuration properties for the Alfresco Share user interface, not the core repository.

1. Alfresco Content Services 7.0 Documentation, "JMX bean categories reference": "Alfresco exposes JMX MBeans that allow you to manage and monitor the server. You can use a JMX client, such as JConsole, to view the MBeans... The MBeans are arranged in a tree structure, which you can see in the JConsole MBean tab." This confirms JConsole is the tool for viewing live, managed beans representing the system's state.

2. Alfresco Content Services 7.0 Documentation, "Configuration overview": "Alfresco Content Services is configured with a set of default property files... To override the default properties, you can add your settings to the alfresco-global.properties file." This establishes that alfresco-global.properties is an override file, not the final source of truth, which is the resulting in-memory configuration.

3. Alfresco Content Services 7.0 Documentation, "Using the Admin Console - Repository Information": The Repository Information page displays details about the repository server. This information is retrieved from the live system via JMX, demonstrating that JMX is the underlying mechanism for querying the "source of truth" for a running instance. JConsole provides direct access to this JMX interface.

The error message "Alfresco is running without Share Services" specifically indicates that the Alfresco Share user interface is unable to find and connect to essential services that it expects to be available from the repository. These services, which include functionalities for site management, user invitations, and other collaborative features, are packaged within the alfresco-share-services.amp (Alfresco Module Package). This AMP is a repository-side extension and must be applied to the alfresco.war file. Applying this module to the repository and restarting the service makes the required APIs available to Share, resolving the error.

A. The Share Services AMP is a repository extension; applying it to the Share web application (share.war) is incorrect and will not resolve the issue.

C. Re-deploying the share.war file will not fix the problem, as the issue lies with missing components in the repository, not the Share application itself.

D. While using matching versions is a prerequisite for a stable system, it does not automatically install the optional Share Services AMP, which is the specific cause of this error.

1. Alfresco Content Services 7.0 Documentation, Installing Share Services: "The Share Services AMP (alfresco-share-services.amp) is required for Alfresco Share to run correctly. It is applied to the Alfresco Repository WAR (alfresco.war)." This section explicitly states the purpose of the AMP and where it must be installed.

Source: Alfresco Documentation, https://docs.alfresco.com/content-services/latest/install/zip/amp#install-share-services-amp (This link points to the latest version, but the principle is consistent across ACS versions).

2. Alfresco Content Services 6.2 Documentation, Installing an Alfresco Module Package (AMP): This guide details the standard procedure for applying AMP files to Alfresco WAR files using the Module Management Tool (MMT). The process involves placing the AMP in the amps directory and running the applyamps script, which targets the alfresco.war by default. This confirms the technical procedure implied in the correct answer.

Source: Alfresco Documentation, https://docs.alfresco.com/content-services/6.2/install/zip/amp/ (Section: "Install an Alfresco Module Package").

The Smart Folders functionality is installed using an Alfresco Module Package (AMP). However, after the installation of the AMP, the feature is not active by default. To use Smart Folders, a system administrator must explicitly enable the function by setting the smart.folders.enabled property to true in the alfresco-global.properties file and then restarting the Alfresco server. A failed attempt to create or apply a Smart Folder is a direct symptom of this default-disabled state.

A. The site manager created a template first.

Creating a template is a prerequisite for applying a Smart Folder structure; it is a necessary step in the process, not a cause for failure.

B. Smart Folders can only be created by Site Administrators.

This is incorrect. Applying a Smart Folder template is governed by standard folder permissions; users with edit permissions on a folder (e.g., Site Manager, Collaborator) can apply the template.

C. The Smart Folder AMP has not been installed.

While a missing AMP would make the feature unavailable, the more specific and common cause of failure after installation is that the feature remains disabled by its default configuration.

1. Alfresco Content Services 7.0 Documentation, "Configuring Smart Folders": This official documentation explicitly states the default configuration.

Reference: "You can enable or disable the Smart Folders feature by setting the smart.folders.enabled property to true or false in the alfresco-global.properties file. You must restart the Alfresco server for the setting to take effect. By default, this property is set to false."

Source: Alfresco Content Services 7.0 Documentation, Administering Section.

2. Alfresco Content Services 7.0 Documentation, "Applying a Smart Folder Template": This page clarifies the permissions required, refuting option B.

Reference: Under the prerequisites for applying a template, the documentation states: "Ensure you have the correct permissions to edit the folder." This indicates standard permissions are used, not a role exclusive to Site Administrators.

Source: Alfresco Content Services 7.0 Documentation, Using Content Services Section.

The Aggregating Content Store is specifically designed to combine multiple content stores into a single virtual store. It designates one store as the primary, which handles all read and write operations for new content. The remaining stores are configured as secondary, read-only stores. This architecture is commonly used for content migration scenarios, allowing access to legacy content in read-only archives while all new content is directed to the primary store.

A. File content store: This is the default, single-store implementation. It does not have the built-in capability to aggregate multiple stores or define primary/secondary read-write/read-only roles.

B. Selector Content Store: This store routes new content to one of several underlying stores based on defined rules (e.g., content type or properties), but it doesn't create a primary/secondary read-only structure.

C. Caching content store: This store provides a local cache for a remote backing store to improve performance in distributed environments. It is not designed to aggregate multiple read-only secondary stores.

1. Alfresco Content Services 7.4 Documentation, "Types of content stores":

Aggregating content store: "The Aggregating content store is a content store that aggregates a set of stores. It is a primary store for read and write, and a set of secondary stores for read only."

Selector content store: "The Selector content store provides a mechanism to select a content store to use from a set of stores, based on a content model property."

File content store: "The File content store is the default content store implementation."

Reference Location: Alfresco Documentation > Alfresco Content Services 7.4 > Administering > Repositories > Content stores > Types of content stores.

2. Alfresco Content Services 7.4 Documentation, "Configuring the Aggregating content store":

"The Aggregating content store is a content store that aggregates a set of stores. The first store in the list is the primary store. The primary store is the store that all new content is written to. The other stores are secondary stores and are read-only."

Reference Location: Alfresco Documentation > Alfresco Content Services 7.4 > Administering > Repositories > Content stores > Configuring content stores > Configuring the Aggregating content store.

Java Management Extensions (JMX) in Alfresco provide a standard interface for managing and monitoring the application server. It allows administrators to perform operations such as managing subsystems, enabling or disabling server components like FTP and CIFS, and controlling system-wide settings like single-user mode. However, JMX is not designed for application-level code debugging. Alfresco provides a dedicated JavaScript Debugger tool, accessible via a specific URL, for inspecting and debugging server-side JavaScript extensions. This tool offers features like stepping through code and inspecting variables, which are outside the scope of JMX's management and monitoring capabilities.

A. Alfresco subsystems (e.g., Authentication, Synchronization) are designed to be managed (started, stopped, and configured) directly via JMX MBeans, which is a primary administrative function.

C. The FTP and CIFS servers are implemented as Alfresco subsystems. Therefore, like other subsystems, they can be enabled or disabled at runtime using JMX operations.

D. Alfresco exposes an MBean (Alfresco:Type=Configuration,name=sysAdmin) that includes an operation to enable or disable single-user mode for maintenance tasks.

---

1. Alfresco Content Services 7.4 Documentation, "Using the JMX client": This section details the various administrative tasks that can be performed using a JMX client like JConsole. It explicitly mentions managing subsystems. The File Servers (CIFS/FTP) are listed as manageable subsystems.

Reference: Alfresco Content Services 7.4 Documentation > Administering > Monitoring Alfresco > Using the JMX client.

2. Alfresco Content Services 7.4 Documentation, "JMX bean categories reference": This page lists the MBeans available for management. The Alfresco:Type=Configuration,name=sysAdmin MBean is documented with its attributes and operations, including setSingleUserMode(boolean enabled).

Reference: Alfresco Content Services 7.4 Documentation > Administering > Monitoring Alfresco > JMX bean categories reference > sysAdmin.

3. Alfresco Content Services 7.4 Documentation, "The JavaScript Debugger": This document describes the dedicated tool for debugging server-side JavaScript. It details how to access the debugger via its web script URL (/alfresco/s/api/javascript/debugger) and use its features, confirming it is a separate mechanism from JMX.

Reference: Alfresco Content Services 7.4 Documentation > Developing > Customizing Share > The JavaScript Debugger.

For security reasons, Alfresco Content Services disables the remote JMX RMI connector by default. To connect remotely using a tool like JConsole, an administrator must explicitly enable this functionality. This is achieved by setting the alfresco.jmx.connector.enabled property to true in the alfresco-global.properties file and ensuring the related host and port properties are correctly configured. The problem described, where a connection attempt fails, directly points to this default disabled state.

A. The property alfresco.jmx.connector.enabled being set to true would enable the JMX connector, which is the opposite of the problem described.

C. JConsole is the standard Java monitoring tool included with the JDK and fully supports JMX Remoting (JSR-160) for connecting to remote MBean servers.

D. JConsole is a standard and officially documented tool for managing and monitoring Alfresco via JMX.

1. Alfresco Content Services 7.4 Documentation, Administering > Monitoring Alfresco > JMX settings. The documentation explicitly states: "The JMX RMI connector is disabled by default. To enable the JMX RMI connector, you must override the default settings..." It then lists the property alfresco.jmx.connector.enabled=false as the default.

2. Alfresco Content Services 6.2 Documentation, Administering > Monitoring Alfresco > Using the JMX command-line client. This section provides instructions for connecting with JConsole, confirming it is a supported tool. It also notes the requirement to enable the JMX connector first.

3. Oracle Java SE Documentation, Monitoring and Management Using JMX Technology > JConsole. This official source details the capabilities of JConsole, including its ability to connect to remote JMX agents, which is based on JSR-160.