A platform administrator wants to physically segregate the physical storage for metadata in a single environment. What should the platform administrator create?

Question

Options

• Aadditional foundation repositories
• Badditional custom repositories
• Cadditional project repositories
• Dadditional repository libraries

• A
  7% (2)
• B
  90% (27)
• C
  3% (1)

Explanation

Option B is correct because custom repositories are specifically designed to allow platform administrators to configure independent physical storage locations for metadata within a single environment. Each additional custom repository can point to its own distinct storage backend, achieving true physical segregation.

Why the distractors are wrong:

• A (foundation repositories) - Foundation repositories are pre-built, system-level repositories with fixed storage configurations; administrators cannot create additional ones to segregate storage.
• C (project repositories) - Project repositories are scoped to specific projects and share underlying storage infrastructure; they don't enable physical storage separation at the environment level.
• D (repository libraries) - Repository libraries are logical organizational groupings or collections, not separate physical storage units - they don't affect where data is physically stored.

Memory tip: Think of Custom = Configurable. Custom repositories give administrators the most flexibility, including choosing where (physically) the metadata lives. If a question mentions physical storage control or segregation, "custom" is almost always the lever an admin pulls.

No community discussion yet for this question.