MENU
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?
Suggested Answer: D
Get Premium C1000-138 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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
25 comments · newest first
AR
Ardella
11 months ago
I agree with D, consistency is key in YAML files!
CR
Cristy
11 months ago
Wait, can we really bypass rate limits like that?
PA
Paris
11 months ago
B seems a bit off to me.
DO
Dominque
11 months ago
I think A could work too, but not sure.
TE
Terrilyn
12 months ago
Option D is definitely the right choice!
GI
Gilberto
12 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.
BR
Brande
12 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.
GO
Goldie
1 year 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.
ME
Melita
1 year 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.
NO
Noel
1 year 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.
GE
Gerald
1 year 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.
AL
Alesia
1 year 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.
LI
Lili
1 year 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.
TA
Taryn
1 year 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!
BE
Bettina
2 years 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.
DA
Danilo
2 years 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.
BE
Becky
2 years 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.
LA
Lavera
2 years 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.
UL
Ulysses
2 years ago
I believe option A could work as well, but I'm not entirely sure.
ME
Melda
2 years ago
I think option D might also be a good option to consider.
AD
Adria
2 years ago
I agree, option B seems like the right choice.
JA
Jame
2 years ago
I think C) At the beginning of the YAML add policy: 1.0.0 makes more sense based on the rationale provided.
FR
Franchesca
2 years 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.
AN
Andree
2 years 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.
RE
Reita
2 years ago
I think the answer is A) Add to the info section 'full-custom: true'.