Which action allows a Content Library in VMware vSphere Foundation (VVF) to be accessed by other VMware vCenter Server instances?

Question

Options

• AEnable automatic synchronization.
• BStore the library on a vSAN datastore.
• CStore the library on a shared NFS datastore.
• DPublish the Content Library.

• A
  7% (3)
• B
  2% (1)
• C
  2% (1)
• D
  89% (41)

Explanation

Publishing a Content Library (option D) exposes it as a "subscribed library" endpoint that other vCenter Server instances can discover and sync against - this is the designed mechanism for cross-vCenter library sharing in VVF. Automatic synchronization (A) is a feature that subscribed libraries use to stay updated, but it requires the library to already be published; enabling sync alone doesn't make it accessible. Storing the library on a vSAN (B) or shared NFS datastore (C) controls where the content physically lives, not who can access it - other vCenter instances have no awareness of datastores outside their own management domain.

Memory tip: Think of it like a website - you can host files on any server (datastore), but until you publish the URL, no one outside can subscribe to it.

No community discussion yet for this question.