Free Practice Questions for the IBM Cloud: Integration and Development C1000-171 Exam (2026 Updated)

IBM App Connect Enterprise lets you extend the product with four kinds of user-defined extension: user-defined nodes, connectors, parsers, and user exits. The user-defined nodes and parsers that you create can be used alongside the nodes and parsers supplied with the product, and user exits are written in C and compiled into a loadable exit library (LEL), while user-defined parsers are compiled into a loadable implementation library (LIL). A node.conf.yaml file and an ACE Configuration custom resource are configuration artifacts, not code extensions, and "MQ exits" are an IBM MQ channel concept rather than an App Connect Enterprise extension type. Options A and D are therefore correct.

A CallableFlowInvoke node locates its target by using the application name together with the Endpoint Name property of the CallableInput node. Application and endpoint name pairs must be unique on a single integration server. Callable flows that share the same application and endpoint names are permitted only when they are deployed to different integration servers. The flow name itself plays no part in the addressing.

The figure shows container image options that grow from a minimum (Image A, runtime only) to a maximum (Image E), where each step adds drivers, server configuration, the BAR file and finally environment configuration. IBM describes these deployment styles as "fried" and "baked": in the fried style the product image is kept generic and the BAR file and configuration are supplied when the container starts, while in the baked style everything, including the BAR file and environment configuration, is built into the image. Image E, the furthest-right and most complete image, is therefore the baked approach. It gives consistent, self-contained deployments at the cost of a separate image for each application and environment.

ODBC Activity Log entries describe how the integration server interacts with databases: a message flow connects to an ODBC data source, prepares a database statement for execution, and executes a database statement. Ruleset, queue time-out and HTTP header-size entries belong to other Activity Log resource types.

A security profile is a policy of type Security Profiles. You create it with the Policy editor in the App Connect Enterprise Toolkit, and it defines how authentication, identity mapping and authorization are handled by an external security provider such as LDAP. The security profile is then referenced from a node, a message flow or an HTTP or SOAP configuration, and the resulting policy project is included in the BAR file for deployment.

A JavaCompute node accesses global cache maps through the Java API, using the cache classes in the node's Java code. A Mapping node accesses the cache through the Cache Put, Cache Get and similar transforms in the map. The cache can also be monitored through the activity log and resource statistics, and the embedded cache is administered with mqsicacheadmin. RegistryLookup, HTTPRequest and Route have no cache functions.

After pulling the image from the IBM Cloud Container Registry with docker pull, you re-tag it appropriately and push it to your preferred registry, for example your OpenShift internal registry, so the cluster can pull it without IBM entitlement credentials. The commands are docker tag < source > < target > followed by docker push < target > . Pushing it back to IBM's registry is not possible, and the image does not need to be encrypted.

The JSON parser converts a string written in JSON into a JSON object that later nodes can map, and the CSV parser converts CSV text into a JSON object. So both create JSON objects. The JSON parser goes from string to object, not the reverse, the XML parser is a node placed inside a flow and not a trigger (an event starts the flow), and the log node needs a message as well as a level.

When processing is split between App Connect Enterprise and the cloud service, the Switch server is created and managed for you in the cloud. You download an agent configuration file from the cloud service and use it to configure the on-premises connectivity agent for each integration server. Only when all callable flows and their callers are on-premises do you create and configure the Switch server yourself, using the iibswitch command.

The supported external security providers, also called Policy Decision Points, are TFIM V6.1 (authentication, mapping and authorization), WS-Trust V1.3 compliant security token services including TFIM V6.2, LDAP (authentication and authorization), Windows domain controllers and Kerberos KDCs (authentication). Of the listed options, LDAP and TFIM V6.1 are supported. RADIUS and ADT are not supported, and OAuth is an authorization framework that is not an external security provider in this sense.

A REST API in App Connect Enterprise is described by a Swagger (OpenAPI 2.0) document, and OpenAPI 3.0 is also supported. The document lists the resources and the operations, such as GET and POST, that can be called on them, and the REST API editor builds the flows from it. You can reach the definitions of a deployed API through its definitions URL. XSD describes XML structure and SOAP is a protocol, not a REST specification.

ibmint optimize server, available from 12.0.4.0 for independent integration servers, scans the work directory, server.conf.yaml and deployed flows to find unused components and writes server.components.yaml, which marks the components to switch off so the server starts faster and uses less CPU. Each run replaces any existing file. The file carries optimization metadata, optimizeComponents and serverComponentsVersion, in addition to the component list. The remaining options are not fields of this file. Use --enable or --disable to override the analysis.

When the integration server process crashes, the container exits and the evidence, such as trace, abend and dump files under the work directory, disappears with it. The documented approach is to set an environment variable in the integration server custom resource so the container stays running after the failure, and then to use oc rsh and oc rsync to inspect and copy out the files. mqsivault manages secrets rather than logs, forwarding to Logstash does not capture core or dump files, and a debug pod would not reproduce the crash in the real runtime. Confirm the exact variable name in the troubleshooting guidance for your operator version.

An independent integration server runs as a process that is not managed by an integration node, so the Toolkit and web UI do not stop it. On Windows you stop it either by ending the IntegrationServer process, for example in Task Manager, or by pressing Ctrl+C in the App Connect Enterprise command console. Sending SIGINT is the equivalent method on Linux. Deleting the work directory would destroy deployed resources rather than stop the server.

Connectors for App Connect are built with the IBM Connector Development Kit (Automation Explorer). You can create a connector from scratch by describing the target REST API, which means defining its endpoint and properties manually, or you can import an OpenAPI document and let the kit generate the actions. The result is downloaded as a connector archive (.car) file and imported into the Designer catalog. RAR files and zip files are not connector sources, and a WSDL is consumed by SOAP nodes in the Toolkit rather than used to create a connector.