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

SAP C_DBADM_2404 Exam - Topic 5 Question 29 Discussion

Actual exam question for SAP's C_DBADM_2404 exam
Question #: 29
Topic #: 5
[All C_DBADM_2404 Questions]

You want to prevent changes to system properties in tenant databases. Which configuration file stores the blocklisted properties?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Vincent at Mar 20, 2025, 08:19 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Matthew
4 months ago
Wait, are you guys sure about that?
upvoted 0 times
...
Carmelina
4 months ago
No way, it's attributes.ini for sure!
upvoted 0 times
...
Gracia
4 months ago
I thought it was global.ini?
upvoted 0 times
...
Tesha
4 months ago
It's definitely the multidb.ini file.
upvoted 0 times
...
Felix
5 months ago
I agree, multidb.ini is the right one!
upvoted 0 times
...
Gerardo
5 months ago
I have a feeling it's indexserver.ini, but I might be mixing it up with another configuration file we studied.
upvoted 0 times
...
Kanisha
5 months ago
This question feels familiar; I think we practiced something similar where attributes.ini was mentioned, but I can't remember the details.
upvoted 0 times
...
Rodolfo
5 months ago
I remember something about multidb.ini being related to database configurations, but I can't recall if it specifically handles blocklisted properties.
upvoted 0 times
...
Malinda
6 months ago
I think the blocklisted properties might be in the global.ini file, but I'm not entirely sure.
upvoted 0 times
...
Stephaine
6 months ago
Ah, I've seen this type of question before. The global.ini file is where you'd typically find settings for controlling system properties across tenant databases. I'm pretty confident that's the right answer.
upvoted 0 times
...
Karl
6 months ago
I think the answer is global.ini. That's where I'd expect to find settings related to system-wide properties and configurations. Let me double-check that in my mind.
upvoted 0 times
...
Garry
6 months ago
I'm a bit confused here. I'm not sure which configuration file would store blocklisted system properties. I'll need to review my notes on system configuration to figure this out.
upvoted 0 times
...
Kirby
6 months ago
Okay, let me see... I'm pretty sure it's not in the multidb.ini or attributes.ini files, since those don't seem related to system properties. I'll focus on global.ini and indexserver.ini.
upvoted 0 times
...
Elin
6 months ago
Hmm, this looks like a tricky one. I'll need to think carefully about where system properties are typically configured.
upvoted 0 times
...
Roslyn
1 year ago
Hmm, I'm gonna go with C) global.ini. It's like the big boss of all the config files, right? Gotta keep those system properties in check!
upvoted 0 times
Georgene
11 months ago
User 4: I'm not sure, but I'll go with B) attributes.ini. It seems like it could be the one.
upvoted 0 times
...
Tresa
11 months ago
User 3: I'm sticking with C) global.ini. It just sounds like the right place to blocklist those properties.
upvoted 0 times
...
Kathryn
11 months ago
User 2: No way, I'm pretty sure it's D) indexserver.ini. That's where the real power lies.
upvoted 0 times
...
Jerry
11 months ago
User 1: I think it's actually A) multidb.ini. That's where the magic happens.
upvoted 0 times
...
...
Silvana
1 year ago
A) multidb.ini? Really? I bet the dev who wrote that question was just having a laugh.
upvoted 0 times
Gearldine
11 months ago
B) I think it might be global.ini instead. That file usually contains important system configurations.
upvoted 0 times
...
Belen
11 months ago
A) Yeah, I agree. It does seem like a strange choice for blocklisting properties.
upvoted 0 times
...
...
Hayley
1 year ago
B) attributes.ini, of course! That's where you store all your attribute-related shenanigans.
upvoted 0 times
Adolph
10 months ago
D) indexserver.ini is not the file you're looking for in this case.
upvoted 0 times
...
Stanford
10 months ago
C) I think global.ini might have some important configurations too.
upvoted 0 times
...
Bonita
11 months ago
B) Nope, it's actually attributes.ini that holds the blocklisted properties.
upvoted 0 times
...
Mi
11 months ago
A) multidb.ini is where it's at for blocking system properties.
upvoted 0 times
...
Christiane
11 months ago
D) indexserver.ini is not the file you're looking for in this case.
upvoted 0 times
...
Mona
11 months ago
C) I think global.ini might have some important configurations too.
upvoted 0 times
...
Carman
11 months ago
B) Nope, it's actually attributes.ini that holds the blocklisted properties.
upvoted 0 times
...
Marti
12 months ago
A) multidb.ini is where it's at for blocking system properties.
upvoted 0 times
...
...
Hannah
1 year ago
Because global.ini is commonly used for storing system-wide configurations, including blocklisted properties.
upvoted 0 times
...
Celestine
1 year ago
Why do you think it's global.ini?
upvoted 0 times
...
Hannah
1 year ago
I disagree, I believe the correct answer is C) global.ini.
upvoted 0 times
...
Celestine
1 year ago
I think the answer is A) multidb.ini.
upvoted 0 times
...
Coleen
1 year ago
D) indexserver.ini is probably the right answer. Gotta keep those index servers in check, you know?
upvoted 0 times
...
Heike
1 year ago
C) global.ini seems like the obvious choice here. I mean, where else would you store system-wide configuration settings?
upvoted 0 times
Sonia
12 months ago
D) indexserver.ini might have some relevant properties, but global.ini is probably the main file for this.
upvoted 0 times
...
Ashlee
12 months ago
C) global.ini is the most likely option, it makes sense for system-wide settings to be stored there.
upvoted 0 times
...
Dean
1 year ago
A) multidb.ini is also a possibility, it could be storing the blocklisted properties.
upvoted 0 times
...
...

Save Cancel