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

SAP C_DBADM_2404 Exam - Topic 5 Question 29 Discussion

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

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

Suggested Answer: A

Get Premium C_DBADM_2404 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
40 comments · newest first
MA
Matthew 11 months ago
Wait, are you guys sure about that?
CA
Carmelina 11 months ago
No way, it's attributes.ini for sure!
GR
Gracia 11 months ago
I thought it was global.ini?
TE
Tesha 11 months ago
It's definitely the multidb.ini file.
FE
Felix 11 months ago
I agree, multidb.ini is the right one!
GE
Gerardo 12 months ago
I have a feeling it's indexserver.ini, but I might be mixing it up with another configuration file we studied.
KA
Kanisha 12 months ago
This question feels familiar; I think we practiced something similar where attributes.ini was mentioned, but I can't remember the details.
RO
Rodolfo 1 year ago
I remember something about multidb.ini being related to database configurations, but I can't recall if it specifically handles blocklisted properties.
MA
Malinda 1 year ago
I think the blocklisted properties might be in the global.ini file, but I'm not entirely sure.
ST
Stephaine 1 year 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.
KA
Karl 1 year 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.
GA
Garry 1 year 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.
KI
Kirby 1 year 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.
EL
Elin 1 year ago
Hmm, this looks like a tricky one. I'll need to think carefully about where system properties are typically configured.
RO
Roslyn 2 years 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!
GE
Georgene 1 year ago
↳ replying to Roslyn
User 4: I'm not sure, but I'll go with B) attributes.ini. It seems like it could be the one.
TR
Tresa 1 year ago
↳ replying to Roslyn
User 3: I'm sticking with C) global.ini. It just sounds like the right place to blocklist those properties.
KA
Kathryn 1 year ago
↳ replying to Roslyn
User 2: No way, I'm pretty sure it's D) indexserver.ini. That's where the real power lies.
JE
Jerry 2 years ago
↳ replying to Roslyn
User 1: I think it's actually A) multidb.ini. That's where the magic happens.
SI
Silvana 2 years ago
A) multidb.ini? Really? I bet the dev who wrote that question was just having a laugh.
GE
Gearldine 1 year ago
↳ replying to Silvana
B) I think it might be global.ini instead. That file usually contains important system configurations.
BE
Belen 2 years ago
↳ replying to Silvana
A) Yeah, I agree. It does seem like a strange choice for blocklisting properties.
HA
Hayley 2 years ago
B) attributes.ini, of course! That's where you store all your attribute-related shenanigans.
AD
Adolph 1 year ago
↳ replying to Hayley
D) indexserver.ini is not the file you're looking for in this case.
ST
Stanford 1 year ago
↳ replying to Hayley
C) I think global.ini might have some important configurations too.
BO
Bonita 1 year ago
↳ replying to Hayley
B) Nope, it's actually attributes.ini that holds the blocklisted properties.
MI
Mi 1 year ago
↳ replying to Hayley
A) multidb.ini is where it's at for blocking system properties.
CH
Christiane 1 year ago
↳ replying to Hayley
D) indexserver.ini is not the file you're looking for in this case.
MO
Mona 1 year ago
↳ replying to Hayley
C) I think global.ini might have some important configurations too.
CA
Carman 1 year ago
↳ replying to Hayley
B) Nope, it's actually attributes.ini that holds the blocklisted properties.
MA
Marti 2 years ago
↳ replying to Hayley
A) multidb.ini is where it's at for blocking system properties.
HA
Hannah 2 years ago
Because global.ini is commonly used for storing system-wide configurations, including blocklisted properties.
CE
Celestine 2 years ago
Why do you think it's global.ini?
HA
Hannah 2 years ago
I disagree, I believe the correct answer is C) global.ini.
CE
Celestine 2 years ago
I think the answer is A) multidb.ini.
CO
Coleen 2 years ago
D) indexserver.ini is probably the right answer. Gotta keep those index servers in check, you know?
HE
Heike 2 years ago
C) global.ini seems like the obvious choice here. I mean, where else would you store system-wide configuration settings?
SO
Sonia 2 years ago
↳ replying to Heike
D) indexserver.ini might have some relevant properties, but global.ini is probably the main file for this.
AS
Ashlee 2 years ago
↳ replying to Heike
C) global.ini is the most likely option, it makes sense for system-wide settings to be stored there.
DE
Dean 2 years ago
↳ replying to Heike
A) multidb.ini is also a possibility, it could be storing the blocklisted properties.
0/2000 characters

Save Cancel