IBM C1000-138 Exam - Topic 4 Question 4 Discussion

Actual exam question for IBM's C1000-138 exam

Question #: 4
Topic #: 4

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?

AAdd to the info section 'full-custom: true'.

BAt the beginning of the YAML add global-reflow-policy: 1.0.0.

CAt the beginning of the YAML add policy: 1.0.0.

DEnsure the version at the beginning of the YAML is the same as the version in the info section.

Show Suggested 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

Ardella

3 months ago

I agree with D, consistency is key in YAML files!

upvoted 0 times

...

Cristy

3 months ago

Wait, can we really bypass rate limits like that?

upvoted 0 times

...

Paris

4 months ago

B seems a bit off to me.

upvoted 0 times

...

Dominque

4 months ago

I think A could work too, but not sure.

upvoted 0 times

...

Terrilyn

4 months ago

Option D is definitely the right choice!

upvoted 0 times

...

Gilberto

4 months ago

I think adding 'global-reflow-policy: 1.0.0' was mentioned in one of our discussions, but I’m not confident if it applies here.

upvoted 0 times

...

Brande

5 months ago

I feel like ensuring the version matches in the info section is important, but I can't remember if that's the only requirement we need to meet.

upvoted 0 times

...

Goldie

5 months ago

I remember a practice question where we had to specify the version at the beginning of the YAML, but I can't recall if it was 'policy: 1.0.0' or something else.

upvoted 0 times

...

Melita

5 months ago

I think we might need to add 'full-custom: true' in the info section, but I'm not entirely sure if that's the right approach for this scenario.

upvoted 0 times

...

Noel

5 months ago

I'm pretty confident that the answer is Option A. Adding 'full-custom: true' to the info section of the YAML file is the way to modify the default global ratelimit enforcement behavior as described in the question.

upvoted 0 times

...

Gerald

5 months ago

Okay, I've got this. The question is asking how to modify the global policy YAML file to allow execution of the API even if the ratelimit is exceeded. Option A is the correct answer - we need to add 'full-custom: true' to the info section of the YAML file to achieve this.

upvoted 0 times

...

Alesia

5 months ago

Hmm, I'm a bit confused by this question. I'm not entirely sure what the 'global-reflow-policy' and 'policy' versions refer to in the other options. I'll need to review my notes on ratelimit configuration to make sure I understand the context here.

upvoted 0 times

...

Lili

5 months ago

I think the key here is to look for the option that specifically mentions modifying the default global behavior of the ratelimit enforcement. Option A seems to be the most relevant, as it mentions adding 'full-custom: true' to the info section.

upvoted 0 times

...

Taryn

5 months ago

No problem, I've got this. I'll just go through each option and apply my knowledge of SQL functions. Should be a breeze!

upvoted 0 times

...

Bettina

1 year 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

1 year 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

1 year 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

1 year 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