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 Exam C_DBADM_2404 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

Contribute your Thoughts:

Roslyn
2 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
17 days 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
27 days 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
30 days 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
1 months ago
User 1: I think it's actually A) multidb.ini. That's where the magic happens.
upvoted 0 times
...
...
Silvana
2 months ago
A) multidb.ini? Really? I bet the dev who wrote that question was just having a laugh.
upvoted 0 times
Gearldine
22 days ago
B) I think it might be global.ini instead. That file usually contains important system configurations.
upvoted 0 times
...
Belen
1 months ago
A) Yeah, I agree. It does seem like a strange choice for blocklisting properties.
upvoted 0 times
...
...
Hayley
2 months ago
B) attributes.ini, of course! That's where you store all your attribute-related shenanigans.
upvoted 0 times
Adolph
6 days ago
D) indexserver.ini is not the file you're looking for in this case.
upvoted 0 times
...
Stanford
7 days ago
C) I think global.ini might have some important configurations too.
upvoted 0 times
...
Bonita
8 days ago
B) Nope, it's actually attributes.ini that holds the blocklisted properties.
upvoted 0 times
...
Mi
10 days ago
A) multidb.ini is where it's at for blocking system properties.
upvoted 0 times
...
Christiane
16 days ago
D) indexserver.ini is not the file you're looking for in this case.
upvoted 0 times
...
Mona
20 days ago
C) I think global.ini might have some important configurations too.
upvoted 0 times
...
Carman
22 days ago
B) Nope, it's actually attributes.ini that holds the blocklisted properties.
upvoted 0 times
...
Marti
2 months ago
A) multidb.ini is where it's at for blocking system properties.
upvoted 0 times
...
...
Hannah
2 months ago
Because global.ini is commonly used for storing system-wide configurations, including blocklisted properties.
upvoted 0 times
...
Celestine
2 months ago
Why do you think it's global.ini?
upvoted 0 times
...
Hannah
2 months ago
I disagree, I believe the correct answer is C) global.ini.
upvoted 0 times
...
Celestine
2 months ago
I think the answer is A) multidb.ini.
upvoted 0 times
...
Coleen
2 months ago
D) indexserver.ini is probably the right answer. Gotta keep those index servers in check, you know?
upvoted 0 times
...
Heike
2 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
1 months ago
D) indexserver.ini might have some relevant properties, but global.ini is probably the main file for this.
upvoted 0 times
...
Ashlee
2 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
2 months ago
A) multidb.ini is also a possibility, it could be storing the blocklisted properties.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77