156-815.71 · Question #160
Where do the Global Policy database files reside in an MDS environment?
The correct answer is D. $MDSDIR/conf. See the full explanation below for the reasoning.
Question
Where do the Global Policy database files reside in an MDS environment?
Options
- A$CPDIR/conf
- B$MDSDIR/database
- C$MDSDIR/conf/mdsdb
- D$MDSDIR/conf
How the community answered
(40 responses)- A5% (2)
- B15% (6)
- C3% (1)
- D78% (31)
Community Discussion
6The answer is D, $MDSDIR/conf. In a Multi-Domain Security Management setup, $MDSDIR points to the root of your MDS installation, and the conf subdirectory under it is where the Global Policy database files live alongside other MDS-level configuration. Spin up an MDS lab and just navigate there yourself, you will find the global objects and policy data sitting right in $MDSDIR/conf and it clicks immediately once you see it. Option C trips people up because $MDSDIR/conf/mdsdb does exist as a path but that is not where the Global Policy database files specifically reside, it goes one level up at conf. Keep $CPDIR separate in your head too, that variable is for the local Check Point installation on a given machine, not the MDS-level store.
The trick here is that the MDS environment keeps its Global Policy database files under $MDSDIR/conf, not the mdsdb subdirectory that many students confuse it with, because $MDSDIR/conf is the top-level configuration home for the entire Multi-Domain Server layer. When you think MDS config, anchor to MDSDIR - conf as your root, and remember that $CPDIR/conf belongs to the single-domain SmartCenter world, not MDS. Quick check, can you tell me what type of data specifically lives one level deeper in $MDSDIR/conf/mdsdb, and why the exam writers include it as a distractor?
The stem is doing you a favor here because once you recognize the MDS prefix narrows you to B, C, and D automatically, but C is the classic trap, that extra mdsdb subdirectory sounds authoritative precisely because it sounds like a place a database would live, and that is exactly why the writers put it there. Read the stem twice, trust the shorter path, and mark D.
First time through I picked B because "database" in the path felt logical for database files, and that trap cost me. When I retook it I remembered that the Global Policy database actually lives under $MDSDIR/conf, not a dedicated database subdirectory, and that locked it in for me on exam day.
B, because MDS stores its database under $MDSDIR/database, not conf.
Mei-Ling, good instinct to anchor on $MDSDIR, but the database subdirectory is a distractor here, the exam maps that function to the path in option D, which aligns with how the blueprint defines the default configuration store for MDS. Keep $MDSDIR/conf in your notes as the tested answer for this one.