Q: HOTSPOT In the image below, select the user role that can include an API endpoint to existing API products and plans, specifies access control, and publishes the API to the developer portal for external discovery. https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/IBM_C1000-147/page_16_img_1.jpg

THE USER SHOULD CLICK ON THE API OWNER ROLE. Explanation: The API Owner (often synonymous with API Product Manager) is the role responsible for the business and lifecycle management of an API. This role's key responsibilities include defining the API as a product by bundling it into plans, specifying business-level policies such as access control and rate limits, and deciding when to publish the API to the developer portal for consumption by Application Developers. While the API Developer writes the code, the API Owner is responsible for its strategic packaging, governance, and release, as depicted by the flow from the API Owner to the API Management component in the diagram.

Question 1

What does Agile Integration, as defined by IBM, relate to?

Accepted Answer

D

Explanation: IBM defines Agile Integration not as a single technology or pattern, but as a comprehensive rethinking of the integration discipline. It is an architectural approach based on three core pillars: decentralized integration (affecting people and ownership), fine-grained architecture (using APIs, microservices, and event-driven patterns), and cloud-native infrastructure (the underlying technology). This holistic view, which combines changes in people, architecture, and technology to achieve speed and flexibility, is most accurately captured by option D. The other options describe specific components or patterns within this broader approach.

Question 2

Which statement about the Container Storage Interface (CSI) drivers is true?

Accepted Answer

D

Explanation: The Container Storage Interface (CSI) is a standard that enables third-party storage vendors to develop plugins for container orchestration systems like OpenShift without altering the core codebase. These CSI drivers are not part of the application or the core OpenShift installation. Instead, they are packaged and distributed as container images. A cluster administrator is responsible for deploying these containerized components—typically a controller plugin (as a Deployment) and a node plugin (as a DaemonSet)—onto the cluster. This "out-of-tree" model allows storage functionality to be added, updated, or removed independently of OpenShift releases.

Question 3

When deploying API Connect on an OpenShift cluster, what are the minimum number of nodes required for high availability for the platform?

Accepted Answer

D

Explanation: For a high-availability (HA) platform deployment, both the underlying OpenShift cluster and the IBM API Connect application must be resilient. OpenShift requires a minimum of three master (control plane) nodes to establish a stable etcd quorum, which is essential for control plane HA and preventing "split-brain" scenarios. Additionally, a minimum of three worker (compute) nodes is the standard requirement for a production API Connect deployment. This allows for proper pod distribution across failure domains, supporting rolling updates and ensuring the service remains available even if one worker node fails.

Question 4

Which format is used to export metering reports from Cloud Pak for Integration?

Accepted Answer

B

Explanation: IBM Cloud Pak for Integration utilizes the IBM Cloud Pak foundational services License Service to monitor and report on license usage. When generating an audit snapshot or retrieving metering reports, the service packages the data into a compressed .zip file. This package contains a complete set of audit files, and the data within these files is formatted as Comma-Separated Values (CSV). This standard format facilitates easy analysis and processing of license usage data in spreadsheet programs or other data analysis tools.

Question 5

What is the IBM App Connect Enterprise Toolkit?

Accepted Answer

D

Explanation: The IBM App Connect Enterprise Toolkit is an Integrated Development Environment (IDE) built on the Eclipse platform. Its primary purpose is to provide developers with a rich, graphical user interface for creating, testing, and packaging integration solutions. Developers use the Toolkit to visually construct message flows by connecting processing nodes, define message models, create graphical data maps for transformation, and manage all the associated artifacts required for an integration application before deploying it to the runtime environment.

Question 6

HOTSPOT In the image below, select the user role that can include an API endpoint to existing API products and plans, specifies access control, and publishes the API to the developer portal for external discovery. https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/IBM_C1000-147/page_16_img_1.jpg

Accepted Answer

THE USER SHOULD CLICK ON THE API OWNER ROLE.

Explanation: The API Owner (often synonymous with API Product Manager) is the role responsible for the business and lifecycle management of an API. This role's key responsibilities include defining the API as a product by bundling it into plans, specifying business-level policies such as access control and rate limits, and deciding when to publish the API to the developer portal for consumption by Application Developers. While the API Developer writes the code, the API Owner is responsible for its strategic packaging, governance, and release, as depicted by the flow from the API Owner to the API Management component in the diagram.

Question 7

HOTSPOT Click the diagram that shows a decentralized IBM MQ Containerized Architecture:

Accepted Answer

ENLARGED

Explanation: The provided diagram illustrates a Hybrid MQ Architecture . This model integrates both centralized and decentralized messaging patterns within the same system. Some components (Applications 2, 3, and 5) are shown in a decentralized, container-style pattern, each with its own dedicated MQ queue manager. This provides agility and isolation for modern, microservices-based applications. Simultaneously, a large, shared MQ instance serves as a central messaging backbone. This centralized component is used by other applications (like Application 4) and also facilitates communication between the newer decentralized applications and legacy systems. This hybrid approach is common in enterprises that are progressively modernizing from a monolithic architecture to a microservices-based one.

Question 8

DRAG DROP What is the correct order of dependencies in the DataPower Gateway services point of view as they are nested into each other? https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/IBM_C1000-147/page_11_img_1.jpg

Accepted Answer

Explanation: The dependency order in IBM DataPower Gateway follows a clear hierarchical structure, from the physical or virtual platform down to individual configuration settings. Appliance : This is the top-level container, representing the physical or virtual DataPower Gateway itself. All other components and configurations reside on the appliance. Tenant : On supported models, an appliance can be partitioned into logically isolated instances called tenants . Each tenant receives a dedicated portion of the appliance's resources, effectively operating as a self-contained virtual appliance. Domain : Within an appliance or a tenant, an application domain is a logical partition used to isolate development, testing, or production configurations. Each domain contains its own set of services and resources. Object : An object is the most granular component. It represents a specific configuration instance, such as a Multi-Protocol Gateway, a processing policy, or a cryptographic profile, and always exists within a specific domain.

Question 9

DRAG DROP Select all that apply What is the correct order to configure TLS profiles for an API's access and encryption? List the API Connect components to be configured, from the first to the last one. https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/IBM_C1000-147/page_8_img_1.jpg

Accepted Answer

Explanation: The correct sequence for configuring TLS profiles in IBM API Connect follows the platform's hierarchical structure and component dependencies. Organization : The configuration starts at the highest level, which is the provider Organization . This entity acts as a container for all other components like Catalogs, APIs, and Products. Catalog : Within an Organization, you create a Catalog , which serves as a staging target for APIs. Key configurations, including the TLS profiles for the associated API gateway, are managed at this level. Portal : The Developer Portal is a service associated with a specific Catalog. Its TLS profile is configured within the parent Catalog's settings to secure the portal's website. Space : A Space is a subdivision within a Catalog. Official documentation states that before you can enable and use Spaces, the parent Catalog and its associated Developer Portal must already be configured. Therefore, Space configuration is the final step in this sequence.

Question 10

DRAG DROP A new proxy API needs to be created, security added, and published to the Sandbox catalog. Which is the correct sequence of steps that should be taken to perform these tasks? https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/IBM_C1000-147/page_18_img_1.jpg

Accepted Answer

Explanation: The correct sequence follows the standard API lifecycle workflow in IBM API Connect. First, an API definition must be created or imported. This is the foundational step. Next, security definitions (e.g., API Key, OAuth) are added to the API. This defines what security schemes are available. Then, these definitions are referenced in the API's security section to enforce them on API operations. APIs are not published directly; they must be bundled into a Product . Therefore, the secured API is added to a Product definition. Finally, the Product is published to a Catalog (like the Sandbox catalog), making the API accessible to developers.

Question 11

Which statement is true about IBM Event Streams?

Accepted Answer

C

Explanation: IBM Event Streams is built upon Apache Kafka, which is fundamentally a distributed commit log. A core architectural principle of this design is durability. All messages published to a topic are written to disk and replicated, making persistent storage an inherent and default feature. This ensures that data is not lost in the event of a broker failure or restart, providing strong durability guarantees for event data.

Question 12

Application owned asynchronous capabilities, like messaging and events, must exhibit which features to align to agile integration paradigm?

Accepted Answer

C

Explanation: The agile integration paradigm fundamentally shifts ownership of integration capabilities from a central team to the application development teams. To facilitate this decentralized model and achieve development agility, the underlying asynchronous infrastructure (messaging and events) must provide self-service capabilities. Self-provisioning and self-administration empower teams to create, configure, and manage their own resources (like queues or topics) on-demand, eliminating dependencies and bottlenecks associated with a central IT team. This autonomy is a cornerstone of agile integration, directly enabling faster development and deployment cycles.

Question 13

Which approach can be implemented with Cloud Pak for Integration to help a company modernize its application environment and container management capabilities?

Accepted Answer

A

Explanation: IBM Cloud Pak for Integration is fundamentally designed to facilitate application modernization by enabling a shift from traditional monolithic architectures to more agile, cloud-native patterns. The microservices approach is central to this modernization. It involves decomposing large applications into smaller, independently deployable, and containerized services. Cloud Pak for Integration, built on Red Hat OpenShift (a Kubernetes platform), provides the essential capabilities—such as API management, event-driven messaging, and application integration—to connect, secure, and manage these distributed microservices, thereby directly supporting both application environment modernization and container management.

Question 14

Which is an IBM Cloud Pak solution advantage?

Accepted Answer

A

Explanation: The primary advantage of IBM Cloud Pak solutions is that they provide enterprise-ready, containerized software stacks built on Red Hat OpenShift. This approach offers a complete and consistent experience for developing, deploying, and managing applications across hybrid cloud environments. IBM certifies the entire stack, from the infrastructure to the middleware, ensuring ongoing security patching, compliance management, and version compatibility. This significantly reduces the complexity and operational overhead for enterprises compared to assembling and maintaining these components independently.

Question 15

What does OpenShift use to provide storage to Cloud Pak for Integration components?

Accepted Answer

C

Explanation: OpenShift, which is built on Kubernetes, utilizes the Persistent Volume (PV) framework to provide storage to containerized applications like the components of Cloud Pak for Integration. A Persistent Volume is an abstraction for a piece of storage in the cluster, which is decoupled from the lifecycle of any individual pod. Cloud Pak for Integration components request this storage using a Persistent Volume Claim (PVC). This mechanism allows stateful applications to maintain their data across restarts, rescheduling, and node failures, by mounting a persistent storage resource that exists independently within the cluster.

Free IBM C1000-147 Actual Exam Questions