C1000-143 IBM Cloud Pak for Watson AIOps v3.2 Administrator Question and Answers

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

Database. DASH, Ul, Mediation Tool, DB2

Database, Analytic, TEP, REST Mediation Service, Import

Event Manager, Al Manager, Agile Service Manager, REST Mediation Service, Cloud Pak for Data

Database, Analytic, Ul, Mediation Tool, REST Mediation Service

Create a view that contains the tables to read

Implement a virtual data fabric

Create a second database and export the data

Change the database configuration to use non-normalized tables

Using a crontab job

Using the self-monitoring capabilities of Event Manager

Using the Process Agent

Using failover and fail back

Default LDAP configuration is equal to default CloudPak LDAP settings, however Single Sign On (SSO) with DASH should be configured.

There is no need to configure LDAP user registry as Metric Manager is part of Cloud Pak for Watson AlOps.

It is necessary to create an IdapRegistry.xml file with appropriate content for the LDAP server.

The LDAP directory must be assigned to a Team as a resource before configuring an LDAP user registry for Metric Manager.

You can get all neighbors of the selected resource by adding a Filter tag,

It allows the resources used by a dynamic template to be confined to a specified set of resources.

They are used to identify changes in the time line.

It allows connecting different resource groups