View All HCL-HWA-ADM-102 Actual Free Exam Questions Jun 17, 2026 Updated
Pass Authentic HCLSoftware HCL-HWA-ADM-102 with Free Practice Tests and Exam Dumps
NEW QUESTION # 348
In HCL Workload Automation 10.2 authentication configuration, for OIDC with custom claims mapping to roles, which element is used?
- A. Liberty role mapping properties
- B. Custom jwtConsumer claims
- C. Federated custom filter
- D. groupMapper extension
- E. <openidConnect> with userIdentityToGroupsMapping
Answer: E
Explanation:
<openidConnect> with userIdentityToGroupsMapping maps token claims to local groups for role assignment.
NEW QUESTION # 349
Scenario: During production plan rollover, incomplete jobs with "carry forward" not set are lost. To ensure critical high-priority jobs always carry forward in future cycles in HCL Workload Automation 10.2, what configurations are required? (Select All that Apply)
- A. Define run cycles with carry forward enabled on job streams
- B. Use planman carryforward command post-rollover
- C. Set global carryforward = all
- D. Set carryforward attribute in individual job definitions
- E. Enable enCarryForward = yes in global options
Answer: A,D,E
Explanation:
Carry forward requires enCarryForward = yes globally, plus either the carryforward attribute on jobs or enabled in their run cycles. This ensures selective persistence of incomplete jobs into the next plan without carrying everything, which could overload processing.
NEW QUESTION # 350
A production HCL Workload Automation 10.2 MDM installation on RHEL9 fails during twsinst -new -mdm with error "SSL certificate validation failed for database connection". The DBA confirms DB2 11.5 is configured with TLS 1.3 only. Which installation property must be added to the response file to bypass this during initial setup?
- A. ignore.db.ssl.validation=true
- B. db.ssl.truststore=/opt/IBM/db2/ssl/truststore.jks
- C. use.db.tls12.compatibility=false
- D. tws_db_ssl_enabled=false
Answer: A
Explanation:
The twsinst script in HWA 10.2 defaults to strict TLS 1.3 validation for DB2 connections, which fails against mixed TLS configurations. Setting ignore.db.ssl.validation=true in the response file temporarily bypasses certificate chain validation during installation, allowing completion. Post-install, configure proper truststores via localopts DB_SSL_TRUSTSTORE and restart Netman to enable secure connections.
NEW QUESTION # 351
Global manufacturer deploys HCL Workload Automation 10.2 Docker containers across Kubernetes EKS cluster for hybrid cloud bursting. Helm chart installation succeeds but wa-agent pods crashloop with "gateway connection timeout" despite correct agent.dynamic.gateway parameters. NetworkPolicy blocks cross-namespace. Which Docker/Kubernetes deployment configuration using precise Helm values resolves container networking for 500 dynamic agents?
- A. helm upgrade --set wa-server.serviceAccount.annotations."eks.amazonaws.com/role-arn"=wa-server-role
- B. values.yaml: global.networkPolicy.enabled=false; agent.service.type=ClusterIP port=31114
- C. kubectl annotate ns wa-agent net.beta.kubernetes.io/network-policy=allow-egress-to-wa-server
- D. helm install hwa-chart --set agent.namespace=wa-agent --set networkPolicy.egress.gateway=true
Answer: B
Explanation:
Container deployment requires values.yaml global.networkPolicy.enabled=false disabling restrictive Egress policies blocking dynamic agent gateway port 31114, combined with agent.service.type=ClusterIP exposing internal 31114/tcp for wa-agent->wa-server communication across 500 agents in EKS cluster. Namespace annotations lack NetworkPolicy selector specificity, serviceAccount IAM roles handle S3 access only, cross-namespace requires additional ServiceEntry for Istio if enabled.
NEW QUESTION # 352
An organization uses HCL Workload Automation 10.2 with DB2, and the support team requests switching from the default type 4 JDBC driver to a type 2 JDBC driver for troubleshooting performance issues. The database server and Dynamic Workload Console remain unchanged. The administrator needs to make this change with minimal impact, ensuring that the engine loads the new driver on the next restart. Which configuration update is required to accomplish this?
- A. Update db.driver.path in the engine properties to point to the type 2 JDBC driver libraries provided for DB2
- B. Update db.sslConnection to true so that the engine automatically switches to the type 2 driver
- C. Update db.databaseName in the engine properties to indicate the driver type and keep db.driver.path unchanged
- D. Update db.user to a special performance user required by the type 2 driver
Answer: A
Explanation:
In HCL Workload Automation, the db.driver.path property specifies the filesystem path to the JDBC driver libraries that the engine uses to connect to the database. Support may request switching between type 4 and type 2 JDBC drivers for DB2 or Oracle, and this is done by adjusting the db.driver.path to reference the desired driver implementation while keeping the rest of the database connection parameters consistent. Because driver type is not inferred from the database name, user, or SSL flag, updating only db.driver.path ensures that the engine loads the new driver implementation at the next startup without further structural changes to the configuration.
NEW QUESTION # 353
HWA 10.2 installation paths verification post-install: find /opt/hcl -name "*.log" -exec ls -la {} ; shows logs in /opt/hcl/twa/logs but localopts LOGDIR=/var/log/tw a. Startup fails disk full. Correct path?
- A. ln -s /var/log/twa /opt/hcl/twa/logs
- B. Logs always relative to TWA_HOME
- C. Set LOGDIR=$TWA_HOME/logs in localopts
- D. mkdir -p /var/log/twa; chown tws:tws /var/log/twa
Answer: D
Explanation:
localopts LOGDIR overrides default $TWA_HOME/logs. Create target directory post-install: mkdir -p /var/log/twa; chown twsusr:twsgrp /var/log/twa; chmod 775 /var/log/twa. Restart Netman redirects logs correctly.
NEW QUESTION # 354
Template configuration for HCL Workload Automation 10.2 CI/CD pipeline instantiates 1000 job definitions but fails variable expansion for @PIPELINE.BUILD_NUMBER. To integrate Jenkins build metadata into templates via external variable table lookup, which template syntax resolves CI/CD context?
- A. #TEMPLATE CI vars="@jenkins_build()"
- B. TEMPLATE CI @CI.BUILD_NUMBER
- C. @VAR BUILD_ID="${resolve('vt.pipeline.buildnum')}"
- D. DEFINE JOBPIPE @EXTERNAL(pipeline.build)
Answer: C
Explanation:
@VAR BUILD_ID="${resolve('vt.pipeline.buildnum')}" resolves Jenkins build numbers from external variable tables during template expansion, enabling dynamic CI/CD workload generation at scale.
NEW QUESTION # 355
HCL HWA 10.2 FTA reset post-production cycle ransomware corrupts msg/*.msg but TWS/registry intact. Jobman 1850 queued jobs preserved. CP=22h37m blocked. What recovery maximizes production continuity?
- A. TWS_home full restore from backup
- B. planman resyncplan wsname /SECURE
- C. conman "stop wsname#batchman"; rm -rf msg/*.msg; startup wsname#batchman
- D. conman "resetws wsname --ransomware"
Answer: C
Explanation:
Selective batchman stop, rm msg/*.msg rebuilds all 11 message files from intact TWS/registry preserving jobman 1850-job queue and CP=22h37m; fault-tolerant recovery post-ransomware versus full restores requiring extended downtime maintaining production cycle resilience.
NEW QUESTION # 356
HCL HWA 10.2 conman monitoring script tracks SLA violations: jobs due 14:00 running 14:30. conman "dj @-due=1400" returns empty. Correct syntax for overdue jobs?
- A. conman "dj @-state=exec -due=+90m"
- B. conman "overdue @"
- C. conman "dj @-late"
- D. conman "dj @+state=exec;due>now-90m"
Answer: A
Explanation:
Late filter combines state and time delta. conman dj @-state=exec -due=+90m shows executing jobs overdue by 90+ minutes. Output: JOB123 14:32:15 (due
14:00:00 +92m) identifies SLA violations.
NEW QUESTION # 357
Telecommunications provider performs typical HCL Workload Automation 10.2 installation but post-reboot master domain manager fails startup with "maximum open files exceeded". ulimit -n shows 1024 despite /etc/security/limits.conf configured. Production plan contains 75,000 job streams. Which permanent file descriptor limit configuration using systemd override resolves server startup for high-complexity workloads?
- A. echo "* soft nofile 65536" >> /etc/security/limits.conf; reboot
- B. prlimit --pid $TWSM_PID --nofile=65536 before monman startup
- C. ulimit -n 65536 in /opt/hwa/TWS/bin/tws_env profile only
- D. Override /etc/systemd/system/tws.service: LimitNOFILE=65536; systemctl daemon-reload
Answer: D
Explanation:
Server processes require systemd override /etc/systemd/system/tws.service.d/limits.conf containing [Service] LimitNOFILE=65536 ensuring monman/netman inherit 65K file descriptors for 75K job streams, surviving reboots unlike /etc/security/limits.conf PAM limitations. prlimit applies runtime only, tws_env profile scopes shell sessions excluding daemons, echo>> risks syntax errors breaking inheritance chain.
NEW QUESTION # 358
Scenario: Dynamic agent jobs are not receiving updated variables from the master in HCL Workload Automation 10.2. Which process and communication path should be examined?
- A. Writer to Symphony
- B. Mailman to jobman via local queue
- C. Liberty broker to jobman via HTTPS
- D. Monman to event processor
- E. Batchman to netman
Answer: C
Explanation:
Liberty broker to jobman via HTTPS handles direct job dispatch and parameter streaming for dynamic agents without traditional message files.
NEW QUESTION # 359
Installation Properties HWA 10.2 ARM64 support: twsinst on Ubuntu 22.04 ARM fails "Unsupported architecture". Dockerfile uses multi-arch manifest. Correct property for native ARM build?
- A. docker buildx build --platform linux/arm64
- B. Set TWS_ARCH=aarch64 in response file
- C. Install x86_64 emulation via qemu-user-static
- D. HWA 10.2 ARM support only via container
Answer: A
Explanation:
HWA 10.2 native ARM64 requires buildx multi-platform build. docker buildx create --use; docker buildx build --platform linux/arm64 -t hwa:10.2-arm64 --load. twsinst detects uname -m aarch64 correctly, installs ARM-optimized binaries.
NEW QUESTION # 360
Production HCL HWA 10.2 Dynamic Workload Broker shows CLIConfig.properties maxConcurrentAllocations=100 causing 29% queuing delay during 5800 jobs/hour ramp.
BrokerWorkstation.properties cliThrottle=NO. What CLI concurrency optimization eliminates queuing?
- A. BrokerWorkstation.properties: cliMaxThroughput=1000
- B. JobDispatcherConfig.properties: cliAllocationPriority=HIGH
- C. resourceSelectAlgorithm=fastest;cliEnabled=YES
- D. CLIConfig.properties: maxConcurrentAllocations=800;queueDepthLimit=200
Answer: D
Explanation:
maxConcurrentAllocations=800;queueDepthLimit=200 supports 5800 jobs/hour CLI ramp eliminating 29% queuing; bounded concurrency prevents broker overload vs throughput limits throttling bursts or priority lacking capacity maintaining Dynamic Workload Broker CLI scalability during production ramps.
NEW QUESTION # 361
A customer wants to brand the Dynamic Workload Console 10.2.3 with their corporate logo and icon so that the console visually aligns with their other internal portals. They ask whether this kind of visual customization is supported and, if so, from which version. What is the documented capability regarding branding the Dynamic Workload Console?
- A. Starting from version 10.2.3, the Dynamic Workload Console can be customized with a customer's own icon and logo
- B. Branding is supported only in versions earlier than 10.0 and was removed in later releases
- C. Branding is not supported; only color themes can be changed through CSS overrides
- D. Branding requires modifying the HWA server binaries and is not supported as a configuration-only change
Answer: A
Explanation:
Community documentation for HCL Workload Automation states that, starting from version 10.2.3, administrators can customize the Dynamic Workload Console with their own brand elements, including custom icons and logos. This capability allows organizations to align the console's appearance with corporate visual guidelines without altering core server binaries. Earlier versions did not provide the same level of straightforward branding support, and the feature is explicitly described as available from 10.2.3 onward.
NEW QUESTION # 362
You are configuring full SSL encryption for communications between the Dynamic Workload Console (DWC) and a distributed network of dynamic agents in HCL Workload Automation 10.2. To enforce the strongest possible encryption while maintaining compatibility with agents at version 10.2.2, which cipher suites and protocols should you prioritize in the localopts and SSL settings? (Select two)
- A. Use RSA key exchange ciphers to ensure backward compatibility with older fault-tolerant agents
- B. Enable TLSv1.3 exclusively with cha-cha20-poly1305 cipher suites for forward secrecy
- C. Disable TLSv1.0 and TLSv1.1 explicitly in the WebSphere Liberty server.xml
- D. Configure the MDM and DWC to use only ECDHE-RSA-AES256-GCM-SHA384 and similar GCM ciphers
- E. Set SSL Encryption Cipher = HIGH:MEDIUM in the agent localopts to allow fallback
Answer: C,D
Explanation:
Configuring the MDM and DWC to use only ECDHE-RSA-AES256-GCM-SHA384 and similar GCM ciphers ensures strong authenticated encryption with perfect forward secrecy, aligning with modern security standards in version 10.2. Disabling TLSv1.0 and TLSv1.1 explicitly in the WebSphere Liberty server.xml eliminates vulnerable protocols, forcing the use of TLSv1.2 or higher, which is supported across 10.2 components for maximum security without breaking connectivity.
NEW QUESTION # 363
OpenShift 4.14 HCL HWA 10.2 FTA workstation reset fails after OCP node drain; TWS_home/msg/*.msg corrupted, TWS/registry partial. 500 jobs aborted mid-execution.
DWC shows "Agent Down". What OCP-aware architecture reset preserves partial registry state?
- A. oc patch statefulset wa-waagent --type merge -p '{"spec":{"template":{"spec":{"securityContext":{"runAsUser":1001}}}}}'
- B. conman "resetws wsname --ocp-safe"; rm msg/*.msg
- C. oc delete pvc data-hwa-waagent; helm upgrade
- D. oc adm policy add-scc-to-user hwa-privileged -z wa-waagent; conman "startup wsname"
Answer: D
Explanation:
OpenShift workstation architecture reset requires hwa-privileged SCC binding for wa-waagent pod to execute conman startup rebuilding corrupted msg files from partial TWS/registry; preserves 500-job state versus PVC deletion. SCC enables fault-tolerant recovery maintaining workstation architecture integrity.
NEW QUESTION # 364
HCL HWA 10.2 monitoring script tracks prompt backlog: 200 TAPE prompts pending. conman "prompts" shows 3-day accumulation. What bulk prompt satisfaction?
- A. conman "flushprompts"
- B. conman "satisfyall prompts"
- C. conman "clearprompts TAPE*"
- D. conman "reply prompt TAPE* YES @"
Answer: D
Explanation:
Wildcard reply satisfies prompt patterns. conman reply prompt TAPE* YES @ replies YES to all TAPE001-TAPE999 prompts across workstations. Backlog clears instantly releasing dependent workloads.
NEW QUESTION # 365
HCL HWA 10.2 emergency plan extension during outage: conman "extendplan 4h" fails "Invalid time specification". Current final 18:00, extend to 22:00. Correct syntax?
- A. conman "extendplan +4:00"
- B. conman "extendplan 2200"
- C. conman "setfinal 22:00"
- D. conman "extendplan -final 22:00"
Answer: A
Explanation:
Explanation: Relative extension adds hours to current final. conman extendplan +4:00 extends 18:00 final to 22:00 allowing late jobs completion. conman planlist shows new FINAL=22:00.
NEW QUESTION # 366
HCL HWA 10.2 workload security blocks cross-workstation job submission. User submits job from Unix agent to Windows workstation fails ACL. What security file configuration grants transitive workstation access?
- A. USER admin WS=* ACCESS=submit,control,kill
- B. localopts CROSS_WS_SUBMIT_AUTH=admin
- C. security.txt: user=admin workstation=ALL@ actions="submit job"
- D. RBAC grants workstation access automatically
Answer: C
Explanation:
Security file defines cross-workstation permissions explicitly. $TWA_HOME/security.txt: user admin workstation UNIX@,WINDOWS@ actions="submit job control kill" grants admin submit rights across workstation classes. conman sj @WINDOWS/jobname succeeds from Unix agent.
NEW QUESTION # 367
Configuring authentication HCL HWA 10.2 with biometric MFA fails fingerprint validation: "FIDO2 authenticator attestation failed". Liberty server.xml fido2LoginModule configured but attestation certificate missing. Required configuration?
- A. Hardware token required for attestation
- B. <fido2LoginModule id="fidoAuth" relyingPartyId="dwc.corp.com" attestationCertificateAlias="fido-attestation"/>
- C. FIDO2 MFA unsupported in Liberty
- D. Browser handles FIDO2 attestation automatically
Answer: B
Explanation:
Liberty FIDO2 configuration validates authenticator attestation. server.xml: <fido2LoginModule id="fidoMFA" rpId="dwc.corp.com" attestationFormats="packed,fido-u2f" attestationCertificateAlias="yubikey-attestation" origin="https://dwc.corp.com:9443"/> imports YubiKey attestation certificate chain.
NEW QUESTION # 368
HCL HWA 10.2 workstation reset required after FTA corruption shows batchman reading stale PlanBox.msg from previous symreq (version mismatch), jobman semaphore exhaustion on Courier.msg, monman ignoring Moncmd.msg UPGRADE. Netman NetReq.msg stable. What architecture-complete reset sequence preserves running jobs while rebuilding message files?
- A. kill -9 all processes; TWS_home clean install
- B. evtsize all 20M; conman "flushq wsname"
- C. conman "stop wsname#batchman,jobman,monman"; rm msg/*.msg; startup wsname#batchman
- D. conman "resetws wsname"; preserve Courier.msg; netman recycle
Answer: C
Explanation:
Workstation architecture reset targets corrupted batchman PlanBox.msg, jobman Courier.msg semaphores, monman Moncmd.msg via selective conman stops preserving netman NetReq.msg linkage; rm msg/*.msg rebuilds from TWS registry while startup wsname#batchman cascades jobman/monman restarts. Running jobs continue via jobman semaphores until Courier.msg refresh, maintaining workstation fault-tolerant architecture versus full kills or evtsize masking corruption.
NEW QUESTION # 369
A scripting team wants to run automated maintenance jobs through the HCL Workload Automation command line without interactive prompts and with minimal exposure of credentials. They plan to use a dedicated technical user and schedule scripts from a secure operations server. How does the command-line client assemble the full set of connection parameters when some values are provided as command options and others are stored locally?
- A. It first reads parameters supplied to the command and then fills any missing ones from the localopts configuration on the same computer
- B. It always prioritizes the values found in localopts over any parameters passed on the command line
- C. It requires all parameters, including username and password, to be specified on the command line for non-interactive use
- D. It ignores local configuration when a technical user is used and relies only on environment variables
Answer: A
Explanation:
The HCL Workload Automation command-line client constructs its connection configuration by first checking for values supplied as explicit parameters to the command. For any required parameters still missing, such as hostname, port, or other connection details, the client consults the localopts file or related local properties on the same computer, allowing a mix of command-line and local configuration. This behavior enables scripts to override specific parameters where necessary while relying on centrally maintained defaults, avoiding the need to repeat full connection details in each script.
NEW QUESTION # 370
......
New HCL-HWA-ADM-102 Exam Questions Real HCLSoftware Dumps: https://skillmeup.examprepaway.com/HCLSoftware/braindumps.HCL-HWA-ADM-102.ete.file.html