JFrog Artifactory Interview Questions: Repos and CLI (2027)
30 JFrog Artifactory interview questions: local, remote, virtual and federated repos, JFrog CLI upload and build-publish, Xray, promotion.
JFrog Artifactory interview questions focus on repository design and daily administration: when to use local, remote, virtual and federated repositories, how CI pipelines upload artifacts and publish build info with the JFrog CLI, how Xray scanning fits in, and how to keep storage, permissions and replication under control.
This page is about Artifactory itself: repository types, pipeline integration and operations. For questions across the wider JFrog Platform, use our 80+ JFrog interview questions, the main JFrog interview page on this site. Repository definitions and CLI syntax were checked against JFrog's documentation in November 2026.
Key takeaways
- Local repositories hold artifacts you build; remote repositories cache an external registry; virtual repositories combine both behind one URL.
- Federated repositories keep contents synchronised with other federated repositories at remote sites in the same federation.
- Release Bundle repositories need an Enterprise+ subscription with JFrog Distribution and protect signed artifact groups from change.
- The JFrog CLI commands to know:
jf config add,jf rt ping,jf rt upload,jf rt download,jf rt build-publish,jf auditandjf scan. - Build info links an artifact to the build, commit and dependencies that produced it, which is what makes promotion and audits possible.
Repository types at a glance
| Type | Holds | Typical name | Use it for |
|---|---|---|---|
| Local | Artifacts your teams build and upload | libs-release-local | Build outputs, internal packages, images |
| Remote | A cache of an external registry | npm-remote | Third-party dependencies |
| Virtual | Nothing itself; aggregates local and remote | npm | One URL for developers and CI |
| Federated | Contents synchronised across sites | docker-fed | Multi-site teams that all publish |
| Release Bundle | Signed, immutable artifact groups | Managed by Distribution | Distribution to edge sites |
Repository design (questions 1 to 9)
1. What is Artifactory's role in a DevOps pipeline?
It is the binary repository: the single store for build outputs and the proxy for third-party packages. CI uploads what it builds, deployments pull from it, and the build info stored with each artifact tells you exactly where it came from.
2. What is a local repository?
A repository for artifacts your organisation creates and uploads, such as build outputs and internal libraries. JFrog describes these as first-party or second-party artifacts.
3. What is a remote repository and why use one?
A caching proxy for a repository at a remote URL, such as a public registry. The first request downloads the package and later requests are served from the cache. That speeds up builds, keeps them working when the public registry is slow or down, and gives you one place to scan and control what enters.
4. What is a virtual repository?
One endpoint that aggregates any number of local and remote repositories for searching and resolving artifacts. Developers configure a single URL, and administrators can change the repositories behind it without touching every build.
5. How does resolution order in a virtual repository matter?
Artifactory searches the included repositories in the configured order. Put local repositories before remote ones so internal packages win, which also protects against dependency confusion attacks where a public package uses an internal name. Many teams add include and exclude patterns on remote repositories for the same reason.
6. When do you need a federated repository?
When teams in several locations all publish to the same logical repository and need each other's artifacts locally. Federated repositories synchronise contents between members of a federation, unlike one-way replication.
7. How would you lay out repositories for a Maven and Docker shop?
Per package type: maven-dev-local, maven-release-local, maven-remote and a virtual maven; docker-dev-local, docker-prod-local, docker-remote and a virtual docker. Separate dev and release repositories so promotion is a move or copy with permissions, not a rebuild.
8. Why separate snapshot and release repositories?
Snapshots change often and can be cleaned up aggressively; releases must be immutable and kept. Mixing them makes cleanup risky and lets a snapshot slip into production.
9. Why does Artifactory store files by checksum?
Artifactory stores a binary once by its checksum and keeps references from each repository path. The same file uploaded to two repositories uses storage once, and copying or promoting it is a metadata operation. This is general Artifactory design; confirm current storage details for your version in JFrog's documentation.
CI/CD integration (questions 10 to 17)
10. How does a pipeline authenticate to Artifactory?
With a scoped access token or OIDC integration from the CI provider, stored in the CI secret store. Avoid user passwords and avoid tokens that can write to every repository.
11. How do you configure the JFrog CLI?
jf config add my-server --url=https://example.jfrog.io --access-token="$JF_TOKEN" --interactive=false
jf rt ping
jf rt ping (alias jf rt p) confirms the CLI can reach Artifactory.
12. Upload a build output and download it later.
jf rt upload "target/*.jar" libs-release-local/com/example/app/1.4.0/ --build-name=app --build-number=142
jf rt download "libs-release-local/com/example/app/1.4.0/*.jar" ./deploy/
Upload and download split large files into parts (by default 5 parts for uploads and 3 for downloads, per JFrog's docs) and skip files that already exist.
13. What is build info?
A record of a build: its name and number, the artifacts it produced, the dependencies it used, environment details and the Git commit. With it you can answer which commit produced the image in production and which dependencies went into it.
14. How do you publish build info?
jf rt build-add-git app 142
jf rt build-publish app 142
build-add-git (alias bag) attaches Git details, and build-publish (alias bp) stores the collected build info in Artifactory.
15. How do you resolve dependencies through Artifactory in a Maven or npm build?
Point the build tool at the virtual repository, or wrap it with the CLI (jf mvn, jf npm), which also records dependencies into build info. Then no build talks to public registries directly.
16. What is build promotion?
Moving or copying a build's artifacts from one repository to another, such as from docker-dev-local to docker-prod-local, after tests and scans pass. Production pulls only from the promoted repository, and permissions stop CI from writing there directly.
17. How do Docker clients use Artifactory?
Log in to the registry endpoint with a token, tag images with the Artifactory host and repository, and push. Kubernetes pulls through an image pull secret that has read-only access to the production repository.
Security and operations (questions 18 to 24)
18. Where does Xray fit?
JFrog Xray scans artifacts and builds for known vulnerabilities, license issues and other risks. Policies and watches decide what happens, such as failing a build or blocking downloads of a component above a severity.
19. What do jf audit and jf scan do?
jf audit scans the project in the current directory, including its dependencies, before anything is uploaded. jf scan <pattern> (alias jf s) scans local files such as built binaries. Both use Xray, so you catch problems in the pipeline instead of after deployment.
20. How do you design permissions?
Groups mapped from your identity provider, permission targets per repository set, read for most users, deploy only for CI identities on dev repositories, and promotion rights for a release role. Review who can delete or overwrite.
21. Storage is growing fast. What do you do?
Find the largest repositories, set retention for snapshots and dev images, clean unused remote cache entries, and remove build artifacts older than your retention rule unless a release references them. Test cleanup on a copy first.
22. How does replication differ from federation?
Replication copies content from one repository to another in a set direction, for example from a central site to a remote site. Federation keeps several repositories in sync with each other so every site can publish. JFrog documents both under repository management.
23. How do you monitor Artifactory?
Track request latency, error rates, storage use, remote repository health and database performance, and send logs to your log platform. Alert on disk space and on remote repositories failing to reach upstream.
24. How do you plan an upgrade?
Read the release notes, back up the database and configuration, upgrade a staging instance with production-like data, run a set of upload, download and Docker pull tests, then upgrade production in a window.
Scenario questions (25 to 30)
25. Builds fail because the public npm registry is down.
Builds that resolve through a remote repository keep working for packages already cached. Packages never fetched before fail. Explain this and recommend that all builds resolve through the virtual repository so the cache is warm.
26. A developer published an internal package name to the public registry by mistake, and builds picked up the public one.
Fix resolution order so local repositories come first, add exclude patterns for internal scopes on the remote repository, and remove the public package where possible. This is the dependency confusion risk from question 5.
27. Production pulled an image that was never tested.
CI could push straight to the production repository. Remove CI deploy rights there, make promotion the only path, and require Xray and test results before promotion.
28. Uploads are slow from one region.
Check network latency to the instance, use split uploads and threads in the CLI, and consider a federated or replicated repository closer to that team.
29. An auditor asks which builds include a vulnerable library.
Search Xray for the component and list affected builds and artifacts through build info. Without build info, you cannot answer this quickly, which is the main argument for publishing it.
30. A cleanup job deleted a release artifact.
Restore from trash or backup, then change the cleanup rule to exclude release repositories and anything referenced by a promoted build. Run cleanup in dry-run mode before enabling it.
How to prepare
Use a JFrog trial or a local instance. Create local, remote and virtual repositories for one package type, build a small project through the virtual repository with the CLI, publish build info and promote the build. Then explain each step in your own words. Our explainer on Artifactory and Nexus in artifact management gives the background, and JFrog certification questions help if you are also taking a JFrog exam. For full pipeline practice, see our 200+ DevOps interview questions. Artifact management with Jenkins pipelines is part of our Jenkins course in Pune, in Kharadi and live online.
Frequently asked questions
What is the difference between local, remote and virtual repositories in Artifactory?
Local holds artifacts you build, remote caches an external registry, and virtual combines local and remote repositories behind one URL.
What is a federated repository?
A repository that synchronises its contents with other federated repositories at remote sites in the same federation, so every site can publish and read locally.
How do I upload an artifact with the JFrog CLI?
Run jf rt upload with a source path and a target repository path, for example jf rt upload "target/*.jar" libs-release-local/app/1.0/.
What is build info in Artifactory?
Metadata about a build: name, number, produced artifacts, dependencies, environment and Git details. Publish it with jf rt build-publish.
What is the difference between jf audit and jf scan?
jf audit scans a source project and its dependencies; jf scan scans files on disk such as built binaries. Both use JFrog Xray.
Why put local repositories before remote ones in a virtual repository?
So internal packages are resolved first, which helps prevent dependency confusion when a public package uses an internal name.
Do Release Bundle repositories need a special subscription?
Yes. JFrog lists them as available with an Enterprise+ subscription that includes JFrog Distribution.
References
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0