A local repository is available on this system and you need to enable clients to access this repository via HTTP. The repository information is: PUBLISHER TYPE STATUS URI Identify two of the steps…

Question

Options

• AOn the server:
• BOn the server:
• COn the client:
• DOn the client:
• EOn the client:

• A
  81% (13)
• B
  6% (1)
• D
  13% (2)

Explanation

Making a local IPS repository available over HTTP requires exactly two coordinated actions: one on the server to expose the repository via HTTP (option A), and one on the client to point its publisher configuration at that HTTP URI (option C). Option A is correct because the server must run a service (typically pkg/server or pkg.depotd) that serves the repository over HTTP - without this, the content simply isn't reachable. Option C is correct because the client must redirect its publisher to the new HTTP URI using pkg set-publisher -g http://<server>:<port> <publisher> - the client won't find the repository unless explicitly told where to look.

Option B is wrong because it represents an unnecessary or incorrect server-side action (the depot service alone is sufficient; no additional server step is required). Options D and E are wrong because they describe client-side steps that are either redundant, incorrect syntax, or actions that belong on the server side rather than the client.

Memory tip: Think "two handshake steps" - the server opens its hand (enables HTTP serving), and the client grabs it (sets the publisher URI). One action without the other always fails: the server can serve with no one listening, or the client can point at nothing.

No community discussion yet for this question.