In high-volume environments, to manage log growth while retaining traces:

• A.External forwarding
• B.In-memory only
• C.Configure CCLog rotation limits and max files
• D.Manual pruning
• E.Disable non-critical traces

Comment: *

Name: *

Email: *

Verification: *

During HCL HWA 10.2 installation on AIX 7.2, the administrator sets TWA_HOME=/usr/lpp/twas and TWS_DATA_DIR=/dbdata/twas_data exceeding 4TB total with joblog archiving enabled. twsinst reports "Insufficient disk space in TWS_DATA_DIR". What is the precise calculation for minimum required space in TWS_DATA_DIR?

• A.TWA_HOME size x 2 + 20% for database growth
• B.1.5x TWA_HOME + log retention period in days x 100MB
• C.2x TWA_HOME size + 10GB per 1000 jobs/day
• D.TWA_HOME size + 500MB per CPU core + swap space

Comment: *

Name: *

Email: *

Verification: *

HCL HWA 10.2 customizing DWC certificates for SAML federation fails signature validation: "Signature algorithm SHA1withRSA not allowed". IdP metadata specifies SHA256. Required Liberty SAML configuration override?

• A.server.xml: <samlSP id="samlSP" idpMetadataRef="idpMetadata" signatureAlgorithm="RSA_SHA256"/>
• B.samlGlobalSpMetadata.xml: <signatureMethod algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
• C.IdP metadata auto-negotiates SHA256, no configuration required
• D.jvm.options: -Dsaml.security.signature.algorithm=SHA256withRSA

Comment: *

Name: *

Email: *

Verification: *

To combine multiple topics: In a secure HCL Workload Automation 10.2 environment with customized Dynamic Workload Console, after changing an encrypted database password, an administrator updates the datasource file and restarts the server. Users still cannot connect via the console due to outdated engine parameters, and some dynamic agents fail job execution. Which actions resolve all issues? (Select All that Apply)

• A.Update and save engine connection parameters in Dynamic Workload Console
• B.Restart the Dynamic Workload Console application server for branding consistency if customized
• C.Clear all browser caches globally
• D.Verify JobManager.ini on affected agents for broker connectivity

Comment: *

Name: *

Email: *

Verification: *

During the installation of a new HCL Workload Automation dynamic agent on an IBM i system, the administrator must specify the host that the agent will connect to, the installation directory, and other agent-related details. The target system will be part of an existing distributed environment, and the administrator wants to ensure the installer correctly registers the agent against the endpoint. According to the IBM i agent installation parameters, which parameters are essential to correctly identify the host and installation directory?

• A.db.serverName and db.databaseName parameters set in the engine configuration
• B.db.portNumber and db.driver.path parameters supplied during installation
• C.hostname and -inst_dir parameters supplied to the installation program
• D.agent.dynamic.gateway.hostname and agent.dynamic.gateway.port parameters only

Comment: *

Name: *

Email: *

Verification: *