Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

IBM Exam C1000-138 Topic 4 Question 4 Discussion

Actual exam question for IBM's C1000-138 exam
Question #: 4
Topic #: 4
[All C1000-138 Questions]

A developer has asked to modify the default global behavior of ratelimit enforcement to allow execution of the API even if the ratelimit is exceeded.

When creating the global policy yaml file which is true?

Show Suggested Answer Hide Answer
Suggested Answer: D

When creating a global policy YAML file to modify the default behavior of rate limit enforcement in IBM API Connect v10.0.3, it is crucial to ensure that the version specified at the beginning of the YAML file matches the version in the info section. This alignment is necessary for the system to recognize and apply the correct policy settings across all configurations.

Other options are incorrect:

Option A is not a valid configuration setting for global policies.

Option B and C do not represent the correct approach to configuring global policy YAML files.


IBM API Connect v10.0.3 Documentation: Creating and Modifying Global Policies

by Marica at Sep 08, 2024, 06:11 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Bettina
10 months ago
Option A looks like it might work, but I'm not sure if 'full-custom: true' is the right way to go about it. I'd double-check the documentation on that one.
upvoted 0 times
...
Danilo
10 months ago
Haha, the developer must be really impatient if they want to bypass the ratelimit. I'd go with option B, but maybe they should just chill and wait their turn.
upvoted 0 times
...
Becky
10 months ago
Hmm, I'm not sure about that. Option D seems more logical to me - the version at the beginning of the YAML should match the version in the info section.
upvoted 0 times
...
Lavera
10 months ago
I think option B is the correct answer. Adding 'global-reflow-policy: 1.0.0' at the beginning of the YAML file should modify the default global behavior of ratelimit enforcement.
upvoted 0 times
Ulysses
10 months ago
I believe option A could work as well, but I'm not entirely sure.
upvoted 0 times
...
Melda
10 months ago
I think option D might also be a good option to consider.
upvoted 0 times
...
Adria
10 months ago
I agree, option B seems like the right choice.
upvoted 0 times
...
...
Jame
10 months ago
I think C) At the beginning of the YAML add policy: 1.0.0 makes more sense based on the rationale provided.
upvoted 0 times
...
Franchesca
10 months ago
I'm not sure, but I think B) At the beginning of the YAML add global-reflow-policy: 1.0.0 could be the correct answer.
upvoted 0 times
...
Andree
10 months ago
I disagree, I believe the answer is D) Ensure the version at the beginning of the YAML is the same as the version in the info section.
upvoted 0 times
...
Reita
11 months ago
I think the answer is A) Add to the info section 'full-custom: true'.
upvoted 0 times
...

Save Cancel