Scenario: You are preparing to install HCL Workload Automation 10.2 master domain manager using DB2. The DB2 administrator has created the database instance but not the tables. What is the correct sequence involving provided tools?

• A.Install first, then use optman to initialize database.
• B.Manually run SQL scripts from tws_tools; no automated tool available.
• C.Use serverinst script with --createdb true parameter.
• D.Run configureDb.vbs directly with admin credentials to create and populate tables.
• E.Provide create_database.sql to DB2 admin for database creation, then run configureDb to populate tables.

Comment: *

Name: *

Email: *

Verification: *

Which conditions persisting beyond the threshold trigger automatic failover to a backup master in HCL Workload Automation 10.2? (Select All that Apply)

• A.Batchman, Mailman, or Jobman processes fail three restart attempts
• B.WebSphere Application Server Liberty Base down
• C.Dynamic Workload Console disconnected
• D.Database connection lost
• E.Netman port unresponsive

Comment: *

Name: *

Email: *

Verification: *

A newly hired HCL Workload Automation administrator is troubleshooting intermittent authentication failures with conman commands from a jump server. They suspect that some commands are using stale or partial connection configuration. The administrator wants to ensure that the command-line client always prefers explicitly specified command parameters but falls back to local configuration when needed. What does the product's connection parameter resolution sequence imply for how the administrator should structure scripts?

• A.Scripts should avoid using localopts entirely, because any presence of local options overrides command-line parameters
• B.Scripts must always specify the full set of connection parameters on the command line to avoid reading local configuration
• C.Scripts should rely solely on environment variables and ignore both command options and localopts
• D.Scripts should pass only parameters that need to differ from the localopts settings, letting the client read missing values from localopts after processing the command-line options

Comment: *

Name: *

Email: *

Verification: *

Dynamic Workload Broker ResourceAdvisorConfig.properties shows diskWeight=0.7 causing 52% job rejections on SSD pools during 4800 jobs/hour I/O-intensive workload. CPU utilization 32%. What resource weighting corrects SSD misclassification?

• A.diskThreshold=0.92;enableIoMonitoring=YES
• B.ResourceAdvisorConfig.properties: diskWeight=0.2;ioWeight=0.4;cpuWeight=0.4
• C.resourceSelectAlgorithm=capacity;diskWeight=0.1
• D.cpuWeight=0.6;memoryWeight=0.3;diskWeight=0.1

Comment: *

Name: *

Email: *

Verification: *

To manage multiple Orchestration CLI configurations in HCL Workload Automation 10.2, adding a new context "backup" with different API key, how? (Select two)

• A.ocli context add backup --endpoint backup_url --apikey newkey
• B.Manually update config.yaml
• C.ocli config create backup
• D.Edit config.yaml add context backup
• E.ocli login --save backup

Comment: *

Name: *

Email: *

Verification: *