SAP Exam C_DBADM_2404 Topic 5 Question 29 Discussion

Actual exam question for SAP's C_DBADM_2404 exam

Question #: 29
Topic #: 5

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

Amultidb.ini

Battributes.ini

Cglobal.ini

Dindexserver.ini

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

Submit Cancel

Roslyn

4 months 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

3 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

3 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

3 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

3 months ago

User 1: I think it's actually A) multidb.ini. That's where the magic happens.

upvoted 0 times

...

Silvana

4 months ago

A) multidb.ini? Really? I bet the dev who wrote that question was just having a laugh.

upvoted 0 times

Gearldine

3 months ago

B) I think it might be global.ini instead. That file usually contains important system configurations.

upvoted 0 times

...

Belen

3 months ago

A) Yeah, I agree. It does seem like a strange choice for blocklisting properties.

upvoted 0 times

...

Hayley

4 months ago

B) attributes.ini, of course! That's where you store all your attribute-related shenanigans.

upvoted 0 times

Adolph

2 months ago

D) indexserver.ini is not the file you're looking for in this case.

upvoted 0 times

...

Stanford

2 months ago

C) I think global.ini might have some important configurations too.

upvoted 0 times

...

Bonita

2 months ago

B) Nope, it's actually attributes.ini that holds the blocklisted properties.

upvoted 0 times

...

Mi

2 months ago

A) multidb.ini is where it's at for blocking system properties.

upvoted 0 times

...

Christiane

2 months ago

D) indexserver.ini is not the file you're looking for in this case.

upvoted 0 times

...

Mona

3 months ago

C) I think global.ini might have some important configurations too.

upvoted 0 times

...

Carman

3 months ago

B) Nope, it's actually attributes.ini that holds the blocklisted properties.

upvoted 0 times

...

Marti

4 months ago

A) multidb.ini is where it's at for blocking system properties.

upvoted 0 times

...

Hannah

4 months ago

Because global.ini is commonly used for storing system-wide configurations, including blocklisted properties.

upvoted 0 times

...

Celestine

4 months ago

Why do you think it's global.ini?

upvoted 0 times

...

Hannah

4 months ago

I disagree, I believe the correct answer is C) global.ini.

upvoted 0 times

...

Celestine

4 months ago

I think the answer is A) multidb.ini.

upvoted 0 times

...

Coleen

4 months ago

D) indexserver.ini is probably the right answer. Gotta keep those index servers in check, you know?

upvoted 0 times

...

Heike

4 months 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

3 months ago

D) indexserver.ini might have some relevant properties, but global.ini is probably the main file for this.

upvoted 0 times

...

Ashlee

4 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

4 months ago

A) multidb.ini is also a possibility, it could be storing the blocklisted properties.

upvoted 0 times

...