QUESTION: 9

How can a Consumer see their API usage?

The calling application would need to keep track of the API usage.
The numbers of requests, for different APIs, that the Consumer's application has made are shown on their application page.
The Consumer can be permitted to access the analytics on API Manager.
The Consumer would need to request an API usage report from the API provider.

Answer(s): B

Explanation:

In IBM API Connect v10.0.3, consumers can see their API usage on their application page within the Developer Portal. This page provides details about the number of requests made by their application to different APIs, allowing consumers to monitor their API consumption directly. This feature helps consumers track their usage metrics without needing to keep track themselves or request reports from the API provider.

Other options are incorrect:
Option A: The calling application does not need to track API usage manually. Option C: Consumers are not typically given access to the API Manager analytics directly. Option D: API providers do not need to generate a separate report; usage details are automatically available to consumers.

Reference:

IBM API Connect v10.0.3 Documentation: Consumer Access to API Usage IBM Community Blog: Developer User Experience with API Connect

Reveal Solution Next Question

QUESTION: 10

How are Gateway extensions packaged to upload to the Gateways?

As .tar files
As .cfg files
As .zip files
As war files

Answer(s): C

Explanation:

Packaging Format: Gateway extensions in IBM API Connect v10.0.3 are packaged as .zip files. This format is used to bundle all necessary files and configurations required for the extension. Upload Process: These .zip files are then uploaded to the Gateway through the API Manager interface. The API Manager handles the deployment and integration of these extensions into the Gateway.
Documentation

Reference:

According to the IBM Certified Solution Implementer - API Connect v10.0.3 documentation, the correct packaging format for Gateway extensions is .zip files1.
1: IBM Certified Solution Implementer - API Connect v10.0.3 Documentation

Reveal Solution Next Question

QUESTION: 11

Which HA concept applies for OAuth operations in a multi-node Kubernetes cluster?

Quorum
Heartbeat
STONITH
Quantum

Answer(s): A

Explanation:

High Availability (HA) Concept: In a multi-node Kubernetes cluster, the concept of "Quorum" is crucial for ensuring high availability and consistency, especially for operations like OAuth. Quorum Definition: Quorum refers to the minimum number of nodes that must agree on a transaction or operation to ensure consistency and avoid split-brain scenarios. This is particularly important in distributed systems to maintain data integrity and availability. OAuth Operations: For OAuth operations, maintaining a quorum ensures that the authentication and authorization processes are reliable and consistent across the cluster. This helps in preventing issues where different nodes might have conflicting states.
Documentation

Reference:

According to the IBM Certified Solution Implementer - API Connect v10.0.3 documentation, the concept of quorum is applied to ensure high availability and consistency in OAuth operations within a multi-node Kubernetes cluster1.
1: IBM Certified Solution Implementer - API Connect v10.0.3 Documentation

Reveal Solution Next Question

QUESTION: 12

What is correct about using context variables in Gatewayscript policies?

context.set('my.vars.amount', 100) generates { "my.vars": { "amount": 100 } }
All API context variables are saved in an XML tree.
context.message.statuscode = '200 Success' updates the status code of the message object.
context. request. statuscode = 400 updates the status code of the request object.

Answer(s): A

Explanation:

Setting Context Variables: In Gatewayscript policies, the context.set function is used to set context variables. The syntax context.set('my.vars.amount', 100) creates a JSON structure where my.vars is an object containing the key amount with the value 100.
JSON Structure: This method of setting context variables generates a JSON structure, which is a common format for data interchange in APIs. The resulting structure would be { "my.vars": { "amount": 100 } }.
Usage in Policies: This approach allows for easy manipulation and access to variables within the GatewayScript, facilitating dynamic API behavior based on the context. Documentation

Reference:

According to the IBM Certified Solution Implementer - API Connect v10.0.3 documentation, using context.set in this manner is the correct way to generate the specified JSON structure1.
1: IBM Certified Solution Implementer - API Connect v10.0.3 Documentation

Reveal Solution Next Question

Free C1000-138 Exam Braindumps (page: 3)

QUESTION: 9

Explanation:

Reference:

QUESTION: 10

Explanation:

Reference:

QUESTION: 11

Explanation:

Reference:

QUESTION: 12

Explanation:

Reference: