IBM C1000-138 Exam - Topic 3 Question 30 Discussion

Actual exam question for IBM's C1000-138 exam

Question #: 30
Topic #: 3

[All C1000-138 Questions]

A developer would like to run the step debugger on the Gatewayscript policy that is part of the Assembly.

What would allow step debugging on the Gatewayscript?

AAdd a debugger; statement.

BEnable step debug in the Test tab.

CClick the Trace in the Test tab.

DEnable debug checkbox in Assemble.

Show Suggested Answer

Suggested Answer: A

To enable step debugging on a GatewayScript policy in IBM API Connect v10.0.3, a developer must add a debugger; statement within the GatewayScript code. This statement serves as a breakpoint that will pause execution, allowing the developer to step through the code to identify and resolve issues.

Other options are incorrect:

Option B and D ('Enable step debug in the Test tab' and 'Enable debug checkbox in Assemble') do not enable the step debugger in GatewayScript.

Option C ('Click the Trace in the Test tab') allows tracing but not step debugging.

IBM API Connect v10.0.3 Documentation: Debugging GatewayScript Policies

by Kirby at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium C1000-138 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Audry

5 days ago

B) Enable step debug in the Test tab. That's the way to go for sure.

upvoted 0 times

...

Talia

10 days ago

A debugger? In my code? It's more likely than you think!

upvoted 0 times

...

Mi

1 month ago

C) Click the Trace in the Test tab. Seems the most straightforward option.

upvoted 0 times

...

Dexter

1 month ago

A) Add a debugger; statement. That's the only way to get real debugging done!

upvoted 0 times

...

Gary

1 month ago

D) Enable debug checkbox in Assemble.

upvoted 0 times

...

Renea

2 months ago

B) Enable step debug in the Test tab.

upvoted 0 times

...

Bette

2 months ago

I vaguely remember that enabling the debug checkbox in Assemble could be important, but I can't quite remember how it fits into the whole debugging process.

upvoted 0 times

...

Rebbeca

2 months ago

Clicking Trace in the Test tab sounds familiar, but I feel like it might just show logs instead of actually stepping through the code.

upvoted 0 times

...

Nilsa

2 months ago

I remember something about enabling step debug in the Test tab from our practice questions, but I can't recall if that's the right option here.

upvoted 0 times

...

Desire

2 months ago

I think adding a debugger; statement is definitely a part of enabling step debugging, but I'm not sure if it's the only thing needed.

upvoted 0 times

...

Shawnta

2 months ago

I'm feeling pretty confident about this one. The step debugging functionality is usually accessed through the Test tab, so I'm going to go with B. Enabling that option should give me the ability to step through the Gatewayscript.

upvoted 0 times

...

Gilberto

3 months ago

Okay, let me think this through. I'm pretty sure the debugger; statement is for JavaScript, not for Gatewayscript. And the Trace option in the Test tab is probably for something else. I'm leaning towards B, but I want to double-check the documentation just to be sure.

upvoted 0 times

...

Jennifer

3 months ago

Hmm, I'm a bit confused. Is it really that simple? I feel like there might be some other steps involved, but I can't quite put my finger on it.

upvoted 0 times

...

Dewitt

3 months ago

I think the answer is B. Enabling step debug in the Test tab seems like the most straightforward way to get the step debugger running on the Gatewayscript.

upvoted 0 times

...