OCIR shows repositories named project01/acme-web-app and project01/other-app. What do those names mean?
Select an answer to reveal the explanation.
Short Explanation
A slash in a repository name is just a character—project01/acme-web-app is one repo, not a folder holding another. Sibling names share a prefix for IAM convenience only.
Full Explanation
In OCIR, a name like project01/acme-web-app is a single repository name that happens to contain a slash. The shared project01/ prefix on project01/acme-web-app and project01/other-app is organizational naming convenience so humans can group related apps visually. There is no parent “folder” repository that owns children; each slash-containing string is its own repository resource with its own tags, policies, and lifecycle.
Treating project01 as a filesystem directory that physically contains nested repository folders imports a wrong mental model from file trees. The slash does not create a Kubernetes namespace that OCIR mounts into every cluster—Kubernetes namespaces are cluster API objects, unrelated to OCIR name spelling. Slash-separated names are not rejected by the OCI distribution API; they are a normal naming pattern when policies and docs allow them.
Exam caveat: IAM and retention rules apply per repository name—do not assume a prefix inherits settings from a fictional parent. Operational check: in the Console, open each of project01/acme-web-app and project01/other-app as separate repositories, confirm they have independent tag lists, and apply a test policy change to one without expecting the other to change automatically.