C1000-143 Sample Questions Answers

Using a crontab job

Using the self-monitoring capabilities of Event Manager

Using the Process Agent

Using failover and fail back

AMD64

iSeries

ARM

M1

Entity types in the Topology view

Observer loads

Resources exported from the Topology Manager

Resources that an instance of Topology Manager holds

Event Manager Components can only be started by using the Installation Manager.

Start-up scripts can be created to automatically start the various Event Manager components.

Startup GUI can be installed to automatic start the various components.

Event Manager components can only be started ally by using Linux or Windows commands.

Existing on-premises Event Manager components can only communicate with cloud-based components using a mediation package.

Existing on-premises probes cannot be connected to cloud-based Event Manager components.

Existing on-premises ObjectServers cannot be connected to cloud-based Event Manager components.

Existing on-premises probes can be connected to a cloud-based ObjectServer.

It is the easiest architecture to configure.

It provides the highest level of robustness and distributes the workload evenly.

It provides an out-of-the box integration into all components of Cloud Pak for Watson AlOps.

It eliminates the problem with manual failover and failback.

cURL

Swagger Ul

EventManager API

Manager API

Runbooks API

Any problem / incident data

Any time series data

Any log data

Any event data

JSON

Streamlation

CSV

Parquet

Avro

Archive mode

Backlog mode

Training mode

Replay mode

Partial

Semi-automated

Initial

Fully-automated

Locked-partial

inasm_admin

inasm_editor

inasm_developer

inasm_operator

To enrich ChatOps stories, which might have infrastructure artifacts, from exposure to the Internet

To expose Al Manager for secure two-way communication with the ChatOps tool

To protect the location and blast radius information in the ChatOps tool sent from Al Manager

To secure communication between servers where ChatOps applications run

-was-secret

-settings-secret

aiops-was-secret

-secret

Edit the auth-idp ConfigMap and change the AUTH_SVC_LDAP_CONF1G_TlMEOUT value.

Edit the platform-auth-idp ConfigMap and change the LDAP_TlMEOUT_CONFIG value.

Edit the platform-auth-idp ConfigMap and change the AUTH_SVC_LDAP_CONF1G_TIMEOUT value.

Edit the auth-idp ConfigMap and change the LDAP_TIMEOUT_CONFIG value.

Reactive

Proactive

Public

Private