Most Asked JFrog Interview Questions for Freshers (2027)
75 JFrog interview questions for freshers: Artifactory repository types, checksums, build info, Xray, Curation, permissions and first JFrog CLI commands.
The most asked JFrog interview questions for freshers cover the basics: what a binary repository manager is, the four Artifactory repository types (local, remote, virtual, federated), how checksums and metadata work, what Xray scans, how the JFrog CLI uploads and downloads artifacts, and how users, groups and permissions control access. Know these before scenario rounds.
This page has 75 definition and fundamentals questions with short answers, grouped by level, plus a few scenarios at the end. It is the starting point. When you are comfortable here, move to our scenario-based JFrog interview questions, which assume you already know every term on this page.
Key takeaways
- Artifactory stores build outputs and third-party packages in one place, with metadata, checksums and access control. Most fresher questions are about its repository types.
- Local repositories hold your own artifacts, remote repositories proxy and cache public registries, virtual repositories combine both behind one URL, and federated repositories sync across sites.
- Xray scans artifacts and builds for known vulnerabilities and licence issues and can block downloads through policies and watches.
- The JFrog CLI command is
jf. Learnjf config add,jf rt ping,jf rt upload,jf rt downloadandjf rt build-publish. - JFrog Pipelines reached end of life on 1 May 2026. Do not prepare Pipelines answers as if it were current; expect questions on connecting Artifactory to GitHub Actions, GitLab CI or Jenkins instead.
How the JFrog pages differ
| Page | Question style | Use it when |
|---|---|---|
| This page | Definitions, fundamentals, first commands | You are new to JFrog or need a refresher |
| Scenario-based JFrog questions | "This broke, what do you do?" with CI/CD, Docker, Xray and operations | You can answer everything here without notes |
| Artifactory or Nexus explainer | Background reading | You want to understand why artifact managers exist |
JFrog interview questions for freshers: core concepts
1. What is JFrog?
JFrog is a company that sells a software supply chain platform. Its best-known product is Artifactory, a binary repository manager. The platform also includes Xray for security and licence scanning, Curation for vetting open source packages before they enter your organisation, Distribution for release delivery, and Advanced Security features.
2. What is a binary repository manager?
A server that stores and serves binary files such as JARs, npm packages, Docker images, Python wheels and Helm charts, with versioning, metadata and access control. Source code goes in Git; the things you build from it go in a binary repository.
3. Why not just store build outputs in Git or a shared drive?
Git is designed for text diffs, not large binaries, and shared drives have no package metadata, no dependency resolution for build tools, no fine-grained permissions and no audit trail. A repository manager speaks the native protocol of each package manager, so Maven, npm or Docker can resolve from it directly.
4. What is Artifactory?
JFrog's universal repository manager. It supports many package types in one server, proxies public registries, stores internal artifacts, records build information and integrates with CI tools.
5. What is an artifact?
Any file produced or consumed by a build: a compiled library, an installer, a container image, a ZIP of a static site. In Artifactory each artifact has a path, checksums and optional properties.
6. Which package types does Artifactory support?
Many, including Maven, Gradle, npm, PyPI, NuGet, Docker and OCI, Helm, Go, Conan, RPM, Debian, Terraform and generic files. Check the docs for the full list your version supports rather than quoting a number.
7. What is the JFrog Container Registry?
A free edition of Artifactory focused on Docker and Helm. It is useful for learning and for small teams that only need container images.
8. How can the JFrog Platform be deployed?
As a SaaS service that JFrog runs on a public cloud, or self-hosted on your own servers or Kubernetes cluster with Linux packages, Docker or Helm charts. Some organisations run both, with replication between them. Interviewers ask this to see if you know who handles upgrades and backups in each model.
9. Which ports does a self-hosted Artifactory use?
In Artifactory 7, the JFrog Router listens on 8082 and serves the UI and the platform's external entry point, while the Artifactory service itself listens on 8081. Production setups usually put a reverse proxy or load balancer with TLS on 443 in front.
10. What are the main parts of a self-hosted Artifactory installation?
The Artifactory service, a database for metadata (PostgreSQL is the usual production choice), a filestore for binaries (local disk, NFS or object storage such as S3), and platform services such as Router, Access (users, tokens, permissions) and Metadata. Knowing that binaries and metadata are stored separately helps when you discuss backups.
11. What is the difference between the filestore and the database?
The filestore holds the binary content, named by checksum. The database holds paths, properties, permissions and build info. You need both, taken consistently, to restore a working instance.
12. What is Artifactory high availability?
Several Artifactory nodes behind a load balancer, sharing one database and one filestore, so the service survives a node failure and handles more load. High availability needs a licence that includes it, and shared storage that every node can reach.
Freshers: repository types
13. What is a local repository?
A repository that stores artifacts you deploy yourself, such as your team's releases or internal Docker images. It is the source of truth for internal artifacts.
14. What is a remote repository?
A caching proxy for an external registry such as Maven Central, npmjs or Docker Hub. The first request downloads the package and caches it; later requests are served from the cache. This speeds up builds and keeps them working if the public registry is slow or briefly unavailable.
15. What is a virtual repository?
A single URL that aggregates several local and remote repositories of the same package type. Developers configure one endpoint, and Artifactory searches the included repositories in the order you set.
16. What is a federated repository?
A repository whose content is kept in sync across several Artifactory instances, for example in different regions, so teams in each location work against a nearby copy. Check your licence, as federation is not in every edition.
17. Why does the order of repositories in a virtual repository matter?
Artifactory resolves from the first repository that has the requested artifact. Putting internal local repositories before public remotes helps prevent a public package with the same name from being picked up by mistake.
18. What is a default deployment repository on a virtual repository?
The local repository that receives artifacts when someone deploys to the virtual URL. Without it, deploys to the virtual repository fail.
19. What is the difference between a release and a snapshot repository in Maven?
Release repositories hold fixed versions such as 1.4.0, which should never change. Snapshot repositories hold development versions such as 1.5.0-SNAPSHOT, which are replaced as builds run. Keeping them separate lets you apply different cleanup and overwrite rules.
20. What is a repository layout?
A pattern that tells Artifactory how paths map to module, version and file name for a package type, for example the standard Maven layout. Features such as version cleanup and some searches depend on it.
21. How long does a remote repository cache metadata?
Package files, once cached, do not change. Metadata such as Maven maven-metadata.xml or npm package documents does change, so remote repositories re-check it after a configurable metadata retrieval cache period. A short period finds new versions quickly; a long one reduces calls to the public registry.
22. What do include and exclude patterns on a repository do?
They limit which paths a repository will accept or serve. On a remote repository, excluding your internal group IDs or npm scopes means Artifactory will never fetch those names from the public registry, which is a defence against dependency confusion.
23. What does marking a remote repository offline do?
Artifactory stops contacting the remote URL and serves only what is already cached. It is useful during an upstream outage or in air-gapped environments, but new packages cannot be fetched.
24. What is a smart remote repository?
A remote repository that points to another Artifactory instance instead of a public registry. It can sync properties and show remote content more richly than a plain proxy, and is common between regional instances.
25. What is a generic repository?
A repository with no package-type logic, used for any files: installers, ZIP archives, scripts, test data. It has no special metadata, so naming conventions and properties matter more.
Freshers: storage, metadata and search
26. How does Artifactory store files?
It stores each binary once, identified by its checksum, and keeps paths and metadata in a database. Two paths pointing to identical content share one stored binary. This is called checksum-based storage and gives deduplication.
27. Which checksums does Artifactory use?
It records SHA-1, SHA-256 and MD5 for artifacts. Clients and pipelines can verify downloads against them, and SHA-256 is the one to prefer for integrity checks.
28. What are properties in Artifactory?
Key-value metadata attached to artifacts or folders, for example build.name, qa.status=passed or git.commit. You can search, filter, promote and set permissions based on them.
29. What is AQL?
Artifactory Query Language, a JSON-like query syntax for searching artifacts, builds and properties through the REST API. It answers questions such as "all files over 500 MB in this repository" or "artifacts not downloaded in a year".
30. What is build info?
A record of a CI build: its name and number, the artifacts it produced, the dependencies it used, environment details and links to the Git commit. Artifactory stores it so you can trace a release back to its inputs and promote whole builds.
31. What is build promotion?
Moving or copying a build's artifacts from one repository to another as it passes quality gates, for example from a staging repository to a release repository, usually with a status change recorded in build info. You promote the same binary rather than rebuilding it.
32. What is a release bundle?
An immutable, signed collection of artifacts that represents a release, created from builds or chosen artifacts. Release bundles can be promoted through environments and distributed to other sites. Because they are signed, the receiving side can check nothing changed in transit.
33. What is the trash can in Artifactory?
A holding area for deleted items, kept for a configurable number of days so accidental deletions can be restored. Storage is not freed until items leave the trash can, which surprises people during cleanup.
34. What is checksum deploy?
A client sends only the checksum of a file it wants to deploy. If Artifactory already stores a binary with that checksum, it creates the new path without the upload. It saves time and bandwidth for large files that already exist elsewhere in the instance.
Freshers: security and access
35. How does Artifactory control access?
Through users, groups and permissions. A permission gives users or groups actions such as read, annotate, deploy, delete or manage on chosen repositories or builds. Grant permissions to groups rather than individuals.
36. Which authentication options are common?
Local users, LDAP or Active Directory, SAML or OpenID Connect single sign-on, and tokens. For CI systems, prefer short-lived access tokens or OIDC-based authentication over passwords stored in pipeline settings.
37. What is an access token?
A credential issued by the JFrog Platform with a scope and an expiry, used instead of a password for API, CLI and CI access. Tokens can be revoked without changing a user's password.
38. What is JFrog Xray?
A scanning service that analyses artifacts and their dependencies against vulnerability and licence data. It can scan repositories, builds and release bundles continuously.
39. What are watches and policies in Xray?
A policy defines rules, for example "fail if a critical vulnerability is found" or "block GPL licences", and what to do on a violation. A watch applies policies to chosen resources such as repositories or builds. Together they decide whether downloads are blocked or builds fail.
40. What is an SBOM, and how does it relate to JFrog?
A software bill of materials lists the components inside a piece of software. Xray can generate SBOM reports in standard formats such as CycloneDX and SPDX, which customers and auditors increasingly ask for.
41. What is JFrog Curation?
A service that checks open source packages against policies before they are downloaded into your organisation through remote repositories, so risky or malicious packages are blocked at the entry point instead of found later in a scan.
42. What are CVE and CVSS, and how does Xray use them?
A CVE is an identifier for a publicly known vulnerability. CVSS is a scoring system for its severity. Xray maps components in your artifacts to CVEs and shows severities, and policies can act on severity levels, for example failing builds on critical findings.
43. Why can a reported vulnerability be less urgent than its score suggests?
The vulnerable function may never be called by your code, or the component may not be reachable in your deployment. JFrog's Advanced Security includes contextual analysis that checks whether a finding applies. Interviewers like candidates who triage by real exposure, not by score alone.
44. What is an ignore rule in Xray?
A recorded decision to suppress a specific violation, for example a vulnerability with no fix that does not affect you, ideally with an expiry date and a reason. Ignore rules keep builds moving without hiding the issue forever.
45. What kind of licence issues can Xray find?
It identifies the licences of open source components, such as MIT, Apache-2.0 or GPL, and flags those your policy forbids or that are unknown. Legal teams usually set the allowed list.
Freshers: JFrog CLI and first commands
46. What is the JFrog CLI?
A command-line tool, run as jf, for working with Artifactory, Xray and other platform services from a terminal or a CI job. It handles uploads, downloads, build info and scanning.
47. How do you configure the CLI and test the connection?
jf config add my-server --url=https://mycompany.jfrog.io --access-token="$JF_ACCESS_TOKEN"
jf rt ping
jf rt ping returns OK when Artifactory is reachable and the credentials work.
48. How do you upload a file?
jf rt upload "build/app-1.4.0.zip" generic-local/app/1.4.0/
49. How do you download files that match a pattern?
jf rt download "generic-local/app/1.4.0/*.zip" ./downloads/
50. How do you search for artifacts?
jf rt search "generic-local/app/*"
51. How do you record and publish build info from the CLI?
jf rt upload "build/*.zip" generic-local/app/ --build-name=app --build-number=42
jf rt build-collect-env app 42
jf rt build-add-git app 42
jf rt build-publish app 42
52. How do you scan a project's dependencies with the CLI?
Run jf audit in a project folder to scan its dependencies with Xray, or jf scan on files and archives. Both need Xray on your platform.
53. How do you push a Docker image to Artifactory?
docker login mycompany.jfrog.io
docker tag app:1.4.0 mycompany.jfrog.io/docker-local/app:1.4.0
docker push mycompany.jfrog.io/docker-local/app:1.4.0
jf docker push does the same and can also collect build info. The exact registry path depends on how the Docker repositories are set up.
54. How do you check Artifactory health through the REST API?
curl -s https://mycompany.jfrog.io/artifactory/api/system/ping
It returns OK when the service is healthy. Monitoring tools often poll this endpoint.
55. How do you set properties on artifacts from the CLI?
jf rt set-props "generic-local/app/1.4.0/*" "qa.status=passed;git.commit=abc1234"
56. How do you copy or move artifacts between repositories?
jf rt copy "generic-staging/app/1.4.0/" generic-release/app/1.4.0/
jf rt move "generic-staging/app/1.3.0/" generic-archive/app/1.3.0/
57. What is a file spec?
A JSON file that describes uploads or downloads (patterns, targets, properties, exclusions) so a CI job can run the same transfer with one command, for example jf rt upload --spec=upload-spec.json. It keeps long command lines out of pipeline scripts.
{
"files": [
{ "pattern": "build/libs/*.jar", "target": "libs-release-local/app/1.4.0/", "props": "team=payments" }
]
}
58. How do you resolve Maven dependencies through Artifactory with the CLI?
Run jf mvn-config in the project to set the resolution and deployment repositories, then build with jf mvn clean install. The CLI points Maven at Artifactory and records build info, which a plain settings.xml setup does not do by itself.
Questions for 2 to 5 years of experience
59. How do you point npm at Artifactory?
Set the registry to a virtual npm repository and authenticate with a token, for example with npm config set registry https://mycompany.jfrog.io/artifactory/api/npm/npm-virtual/ plus credentials in .npmrc, or run jf npm-config and then build with jf npm install to capture build info.
60. How do you clean up old artifacts?
Use cleanup policies or scripted AQL searches for artifacts older than a set age or not downloaded recently, keep a set number of snapshot versions per module, and empty the trash can on a schedule. Never auto-delete release repositories without a retention agreement.
61. What is the difference between copy and move in Artifactory?
Copy creates another path to the same stored binary (no extra storage because of checksum storage). Move changes the path and removes the original. Promotion can use either.
62. Why use a remote repository instead of letting CI pull from Docker Hub directly?
Caching reduces external downloads and helps avoid Docker Hub pull rate limits, builds keep working through short registry outages, and you get one place to scan, block or audit what enters the company.
63. How do you stop someone from overwriting a release version?
Do not give deploy-with-overwrite or delete permissions on release repositories to developers or CI users, and keep release and snapshot repositories separate. Promote into release repositories with a dedicated service identity.
64. What is repository replication?
Copying repository content between Artifactory instances on a schedule or on events. Push replication sends from the source; pull replication has the target fetch through a remote repository. Federated repositories are the newer option for two-way sync of the same repository across sites.
65. What would you monitor on a self-hosted Artifactory?
The ping endpoint, filestore and database disk space, database connection pool use, request latency and error rates, JVM memory, and remote repository errors. Artifactory can expose metrics in a format that Prometheus collects, and logs can go to your log platform.
66. How do Docker clients address repositories in Artifactory?
Artifactory supports different Docker access methods, such as a repository path in the image name (for example mycompany.jfrog.io/docker-local/app:1.4.0) or a subdomain or port per repository on self-hosted setups behind a reverse proxy. The method decides how image names look, so check the instance's setup before writing pipeline scripts.
67. How do you point pip at Artifactory?
Set the index URL to a virtual PyPI repository, for example in pip.conf or with pip install --index-url https://mycompany.jfrog.io/artifactory/api/pypi/pypi-virtual/simple, using a token for authentication. jf pip-config and jf pip install do the same and record build info.
68. How do you use Artifactory as a Go module proxy?
Create a Go remote repository for the public proxy and a virtual repository in front of it, then set GOPROXY to the virtual repository URL. Private modules go in a local Go repository included in the same virtual. jf go-config can set this up.
69. What is the difference between Artifactory and a plain container registry such as Docker Hub or Amazon ECR?
A container registry stores images. Artifactory stores images plus every other package type, proxies public registries for all of them, keeps build info and properties across types, and connects to Xray and Curation. Teams that only need images in one cloud may choose the cloud registry; teams with many package types often centralise in Artifactory.
70. How do you back up a self-hosted Artifactory?
Back up the database and the filestore together so they stay consistent, or rely on storage-level snapshots taken at the same point in time. For object storage filestores, use the storage service's versioning and replication. Built-in system exports suit small instances; large ones need database and storage backups. Test a restore on a separate instance.
Senior-level and scenario questions
71. A build fails because a dependency cannot be resolved, but it exists on the public registry.
Check that the build uses the virtual repository URL, that the remote repository is included in the virtual, that the remote's URL and credentials are right, and that it is not offline or blocked by Curation or an Xray policy. Look at the remote repository's request log and try the download with curl using the same credentials.
72. Security asks how you would protect builds from dependency confusion.
Resolve through virtual repositories with internal locals listed first, use include and exclude patterns on remotes so internal package names are never fetched from public registries, reserve your namespace or scope on public registries where possible, and use Curation or Xray policies to block unexpected packages. This is a defensive design question, so describe controls rather than attacks.
73. Your team still has old JFrog Pipelines definitions. What do you tell an interviewer?
JFrog Pipelines reached end of life on 1 May 2026, so the pipelines need to move to the organisation's chosen CI tool. Keep Artifactory and Xray as the artifact and scanning layer, use the JFrog CLI in the new jobs, and run old and new pipelines side by side until outputs match.
74. Uploads start failing and the UI shows storage warnings.
The filestore or database disk is nearly full. Free space quickly by emptying the trash can and removing old snapshots or unused caches in remote repositories, then add capacity. Afterwards, set cleanup policies, alert on disk use well before it is critical, and consider object storage for the filestore.
75. After a change to the LDAP settings, nobody in one department can log in.
Check the LDAP configuration for the search base, filter and group mapping, test it from the admin settings, and look at the Access service logs for errors. A narrower search base often excludes a department's organisational unit. Keep an internal admin account that does not depend on LDAP so you can fix such problems.
Terms you should be able to define in one sentence
| Term | One-line definition |
|---|---|
| Local repository | Stores artifacts your teams deploy |
| Remote repository | Caching proxy for an external registry |
| Virtual repository | One URL that combines local and remote repositories of one type |
| Federated repository | A repository kept in sync across several Artifactory instances |
| Build info | Record of a CI build's artifacts, dependencies and environment |
| Promotion | Moving or copying a tested build to the next repository without rebuilding |
| Release bundle | Signed, immutable set of artifacts that represents a release |
| Watch | Applies Xray policies to chosen repositories or builds |
| Policy | Rules for vulnerabilities or licences and the action on violation |
| AQL | Artifactory's query language for artifacts, builds and properties |
| Access token | Scoped, expiring credential used instead of a password |
Mistakes freshers make in JFrog interviews
- Describing Artifactory as "a place to store JARs" and missing remote and virtual repositories.
- Saying developers should deploy straight to release repositories.
- Putting admin passwords in CI variables instead of scoped, short-lived tokens or OIDC.
- Treating every CVE as urgent without checking whether it applies.
- Answering Pipelines questions as if the product were still current.
- Not knowing the difference between copy and move, or why copy costs no extra storage.
A 10-day study plan for freshers
| Days | Focus | Hands-on |
|---|---|---|
| 1 to 2 | Questions 1 to 25 | Start a free trial or JFrog Container Registry; create local, remote and virtual repositories |
| 3 to 4 | Questions 26 to 34 | Upload files, add properties, run an AQL search, publish build info |
| 5 to 6 | Questions 35 to 45 | Create groups and permissions; scan a repository if Xray is available |
| 7 to 8 | Questions 46 to 70 | Use the JFrog CLI from a GitHub Actions or Jenkins job |
| 9 to 10 | Questions 71 to 75, then the scenario page | Explain each answer aloud in under two minutes |
Artifact management usually sits inside a CI/CD round. Our DevOps training in Pune covers pipelines, container registries and artifact flow in the Kharadi classroom and live online, and the Jenkins training goes deeper on CI jobs that publish to Artifactory. For context on how large companies build pipelines, see 18 CI/CD pipeline examples from big tech, and for broader prep, our 200+ DevOps interview questions.
FAQ
What are the four Artifactory repository types?
Local (your own artifacts), remote (a caching proxy for a public registry), virtual (one URL combining locals and remotes) and federated (content synced across several Artifactory instances).
What is the difference between Artifactory and Xray?
Artifactory stores and serves artifacts. Xray scans those artifacts and builds for vulnerabilities and licence problems and can block them through policies and watches.
Is JFrog Pipelines still used?
JFrog Pipelines reached end of life on 1 May 2026. Interviewers now ask how Artifactory and Xray connect to CI tools such as GitHub Actions, GitLab CI and Jenkins.
What command checks that the JFrog CLI can reach Artifactory?
jf rt ping. It returns OK when the server is reachable and the configured credentials work.
What is build info in Artifactory?
A record of a CI build that lists the artifacts produced, the dependencies used, environment details and the Git commit, so releases can be traced and promoted.
Is there a free version of Artifactory to practise on?
JFrog offers the free JFrog Container Registry edition and cloud trials. Check JFrog's site for current options, since editions and trial terms change.
Should freshers learn Nexus as well?
Knowing that Sonatype Nexus Repository solves the same problem helps in interviews, but go deep on whichever tool the job description names.
Official references
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0