C1000-130 Sample Questions Answers

A token available in ibm-licensing-token secret in the cp4i namespace.

A password available in platform-auth-idp-credentials in the ibm-common-services namespace.

A password available in ibm-entitlement-key key in the cp4i namespace.

A token available in ibm-licensing-token secret in the ibm-common-services namespace.

Uninstall.sh

Cloud Pak for Integration console

Operator Catalog

OpenShift console

platform-auth-idp-credentials. in the 1AM service installation folder.

platform-auth-idp-credentials, in the ibm-common-services namespace.

platform-auth-idp-credentials, in the /sbin folder.

platform-auth-idp-credentials. in the master-node root folder.

NFS

RWX block storage

RWO block storage

GlusterFS

Travis

Jenkins

Tekton

Argo CD

Use the OpenShift web console to edit the YAML definition of the Asset Re-pository operand of the IBM Automation foundation assets operator.

In OpenShift web console, navigate to the OperatorHub and edit the Automa-tion foundation assets definition.

Open the terminal window and run "oc upgrade ..." command,

Use the OpenShift web console to edit the YAML definition of the IBM Auto-mation foundation assets operator.

SSL

HTTP

SSH

TLS

Asset Manager

Integration Designer

Confluent Platform

Operations Dashboard

Switch server

Mapping assist

Integration agent

Kafka sync

Click the Update button on the Details page of the common-services operand.

Select the Update Common Services option from the Cloud Pak Administration Hub console.

Use the OpenShift web console to change the operator channel from stable-v1 to v3.

Run the script provided by IBM using links available in the documentation.

Click the Update button on the Details page of the IBM Cloud Pak Founda-tional Services operator.

1 day

30 days

7 days

6 months

It provides the ability to trace transactions through IBM Cloud Pak for Integration.

It provides a capability that allows user to store, manage, and retrieve integration assets in IBM Cloud Pak for Integration.

It provides APIs to discover applications, platforms, and infrastructure in the environment.

It provides an event-streaming platform to organize and manage data from many different sources with one reliable, high performance system.

Messaging service to get robust and reliable messaging services.

Automation assets service to store, manage, and retrieve integration assets.

License Service that reports the license use of the product and its underlying product details that are deployed in the containerized environment.

API management service for managing the APIs created on API Connect.

IAM services for authentication and authorization.

cluster-operator

cluster-admin

admin

operator

Copy the resource definition code into a file and use the oc apply -f filename command line option.

Import the catalog project from https://ibm.github.eom/icr-io/cp4int:2.4

Deploy the catalog the Red Hat OpenShift Application Runtimes.

Download the Cloud Pak for Integration driver from partnercentral.ibm.com to a local machine and deploy using the oc new-project command line option

Paste the resource definition code into the import YAML dialog of the OpenShift Admin web console and click Create.

oc get logs ...

oc logs ...

oc describe ...

oc retrieve logs ...

zen followed by a timestamp.

zen followed by a GUID.

zenteam followed by a timestamp.

zenteam followed by a GUID.

They can be deleted regardless of the deployment methods.

They can be deleted if API Connect was deployed using a single top level CR.

They cannot be deleted if API Connect was deployed using a single top level CR.

They cannot be deleted if API Connect was deployed using a single top level CRM.

The command "which oc" shows that the OpenShift Command Line Interface(oc) is successfully installed.

The duster credentials are included at the end of the /.openshifl_install.log file.

The command "oc get nodes" returns the list of nodes in the cluster.

The OpenShift Admin console can be opened with the default user and will display the cluster statistics.

DataPower gateway uses a Quorum mechanism where a global load balancer uses quorum algorithm to choose the active instance.

Queue Manager (MQ) uses Replicated Data Queue Manager (RDQM).

API management uses a quorum mechanism where components are deployed on a minimum of three failure domains.

Platform Navigator uses an Active/Active deployment, where the primary handles all the traffic and in case of failure of the primary, the load balancer will then route the traffic to the secondary.

AppConnect can use a mix of mechanisms - like failover for stateful workloads and active/active deployments for stateless workloads

The Operand Deployment Lifecycle Manager.

The NamespaceScope operator.

Node taints and pod tolerations.

The IAM operator.

The Analytics subsystem cannot retain historical data.

Developer Portal sites will be unresponsive.

Automated API behavior testing has failed.

New API calls will be rejected by the gateway service.

Cluster Update Operator

Cluster Update Manager

Cluster Version Updater

Cluster Version Operator

Splunk.

Kafka Broker.

Apache Lucene.

Apache Solr.

logging service

audit-syslog-service

systemd journal

fluentd service

A. Regular back-ups of the API Manager and Portal have to be taken and these backups should be replicated

to the second site.

This represents a Active/Passive deployment (or Portal and Management ser-vices.

This represents a distributed Kubernetes cluster across the sites.

In case of Data Center J failing, the Kubernetes service of Data Center 2 will detect and instantiate the portal and management services on Data Center 2. D E. This represents an Active/Active deployment for Gateway and Analytics services.

Basic Authentication

OpenShift authentication

PublicKey

Enterprise SAML

Local User Registry

AES128

Portworx

base64

NFS