HCLSoftware Certified Administrator- HWA 10.2 Sample Questions:

1. For deploying with Docker in restricted environments, which feature allows non-root installation in recent HCL Workload Automation 10.2 updates?

A) Regular user account for all components
B) Agent-only non-root
C) Root required for schema creation
D) Helm operator mandatory
E) Only console non-root

2. Scenario: A workstation defined as FTA in HCL Workload Automation 10.2 needs conversion to dynamic agent capability. Which architectural change enables advanced options? (Select two)

A) Unlink and redefine
B) Register with dynamic workload broker
C) Remove domain manager role
D) Co-install dynamic agent package on same host
E) Change type to D-AGNT in definition

3. HCL HWA 10.2 OpenShift 4.14 deployment fails dynamic agent pod startup with "Cannot contact gateway on port 31114" despite waserver-h LoadBalancer accessible. values.yaml shows agent.dynamic.gateway.port=31114 correct but exposeServiceType=Routes. NetworkPolicy da-network-policy blocks. What containers architecture fix enables OpenShift Routes access?

A) Set agent.networkPolicy.allow-agent-to-mdm; change exposeServiceType=Routes
B) Create wa-pod-cluster-role-get-routes-binding namespace-wide
C) Modify waserver.server.exposeServiceType=Routes; agent.networkPolicy disabled
D) Update agent.dynamic.gateway.port=443; OpenShift default

4. HCL HWA 10.2 certificate customization audit reveals default IBM CA still active alongside corporate CA. keytool -list shows 15 aliases. What cleanup sequence removes deprecated certificates safely?

A) Only active alias used by serverKeyAlias matters, ignore others
B) keytool -delete -alias ibm-* -keystore keystore.jks -storepass tws; keytool -list -v |grep -i expired
C) for alias in $(keytool -list |grep IBM |awk '{print $2}'); do keytool -delete -alias $alias -keystore keystore.jks; done
D) rm -rf TWS_eclipse/ssl/*.jks; regenerate default certificates via twscert

5. An enterprise customizes production workload in HCL Workload Automation 10.2 using variable tables to parameterize 500 job streams with environment-specific paths (/prod/data vs /test/data). During final production rollout, variable resolution fails for streams referencing VT.PROD.PATH due to table precedence conflicts with Global Options. To enforce variable table precedence over global settings while enabling selective carry forward of customized tables, which variable table configuration directive achieves this?

A) DEFINE VTABLE PROD PRECEDENCE=table OVERRIDE=global CARRY=yes PATH="/prod/data"
B) #TABLE PROD @PRIORITY(high) @CARRY selective=true PATH="/prod/data"
C) @VAR_TABLE PROD PATH="/prod/data" override.global=true carryforward=selective
D) VT PROD.PATH="/prod/data" @PRECEDENCE(table>global) @CARRY(forward)

Solutions: