{"id":372,"date":"2026-10-13T23:11:06","date_gmt":"2026-10-13T23:11:06","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2014\/08\/20\/interview-questions-and-answers-in-svn-subversion\/"},"modified":"2026-10-13T23:11:06","modified_gmt":"2026-10-13T23:11:06","slug":"interview-questions-and-answers-in-svn-subversion","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/interview-questions-and-answers-in-svn-subversion\/","title":{"rendered":"SVN Interview Questions and Answers: Trunk, Branch, Tag, Update, Commit, Patch, Backup, and Authentication"},"content":{"rendered":"\n

Originally published on 2014-08-20; fully revised and updated.<\/em><\/p>\n\n\n\n

If you are preparing for a DevOps, build\/release, or legacy enterprise tooling interview, SVN (Subversion) still comes up regularly. This guide turns the original question list into practical answers you can use in interviews and in real repositories.<\/p>\n\n\n\n

\"svn-subversion-interview-questions-and-answers\"\/<\/figure>\n\n\n\n

SVN fundamentals you should explain clearly<\/h2>\n\n\n\n

SVN (Subversion)<\/strong> is a centralized version control system. A central repository stores project history, and developers work from local working copies. Each commit creates a new revision in the repository.<\/p>\n\n\n\n

  • Repository:<\/strong> Central store of versioned files and history.<\/li>
  • Working copy:<\/strong> Your local checked-out files.<\/li>
  • Revision:<\/strong> A repository-wide snapshot ID created by commit.<\/li>
  • Update:<\/strong> Pull repository changes into your working copy.<\/li>
  • Commit:<\/strong> Push local committed changes to repository.<\/li><\/ul>\n\n\n\n

    Trunk, branch, and tag in SVN<\/h2>\n\n\n\n

    A common SVN layout is trunk\/<\/code>, branches\/<\/code>, and tags\/<\/code>. These are directory conventions in the repository, not separate repository types.<\/p>\n\n\n\n

    Path<\/th>Typical purpose<\/th>Change pattern<\/th>Interview-ready explanation<\/th><\/tr><\/thead>
    trunk\/<\/td>Main development line<\/td>Frequent commits<\/td>Default integration branch for active work<\/td><\/tr>
    branches\/feature-x<\/td>Isolated feature or release work<\/td>Temporary or long-lived<\/td>Created to avoid destabilizing trunk<\/td><\/tr>
    tags\/v1.0.0<\/td>Release snapshot marker<\/td>Usually no further edits<\/td>Immutable by convention, used for reproducible releases<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
    # Create a branch from trunk<\/span>\nsvn copy https:\/\/svn.example.com\/repos\/app\/trunk \\<\/span>\n         https:\/\/svn.example.com\/repos\/app\/branches\/release-1.0 \\<\/span>\n         -m \"Create release branch\"<\/span>\n\n# Create a tag from trunk<\/span>\nsvn copy https:\/\/svn.example.com\/repos\/app\/trunk \\<\/span>\n         https:\/\/svn.example.com\/repos\/app\/tags\/v1.0.0 \\<\/span>\n         -m \"Tag v1.0.0\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Update vs commit vs \u201csynchronize with repository\u201d<\/h2>\n\n\n\n
    Update<\/strong> and commit<\/strong> are core SVN operations. \u201cSynchronize with repository\u201d is often a GUI\/client phrase that combines checking incoming and outgoing changes, then reconciling them.<\/p>\n\n\n\n
    Operation<\/th>Direction<\/th>What it does<\/th>Common command<\/th><\/tr><\/thead>
    Update<\/td>Repository \u2192 working copy<\/td>Brings local files up to latest revision<\/td>svn update<\/td><\/tr>
    Commit<\/td>Working copy \u2192 repository<\/td>Publishes your local changes as a new revision<\/td>svn commit -m “message”<\/td><\/tr>
    Synchronize<\/td>Both (workflow concept)<\/td>Review incoming and outgoing changes, resolve conflicts, then update\/commit<\/td>Client-dependent wording<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    \nflowchart TD\n    A[Edit working copy] --> B[Run svn status and svn diff]\n    B --> C[Run svn update]\n    C --> D{Conflicts found}\n    D -- Yes --> E[Resolve conflicts]\n    D -- No --> F[Run tests]\n    E --> F[Run tests]\n    F --> G[Run svn commit]\n    G --> H[New repository revision]\n<\/pre>\n\n\n
    # Typical daily cycle<\/span>\nsvn status\nsvn diff\nsvn update\n# resolve conflicts if any<\/span>\nsvn commit -m \"Describe what changed and why\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    How to create and apply a patch in SVN<\/h2>\n\n\n\n
    Patch workflows are useful when you need to share changes without direct commit access.<\/p>\n\n\n
    # Create a patch from your working copy changes<\/span>\nsvn diff > fix.patch\n\n# Apply patch with SVN client support<\/span>\nsvn patch fix.patch\n\n# Alternative with system patch tool<\/span>\npatch -p0 < fix.patch<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Handling conflicts and overriding local files with repository versions<\/h2>\n\n\n\n
    If update produces conflicts and you want to discard local edits, first revert local changes, then update. Use this carefully because local modifications are lost.<\/p>\n\n\n
    # See changed and conflicted files<\/span>\nsvn status\n\n# Discard local edits recursively<\/span>\nsvn revert -R .\n\n# Pull clean repository state<\/span>\nsvn update<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    For already-marked conflicts, you may resolve by accepting repository content where appropriate:<\/p>\n\n\n
    svn resolve --accept theirs-full -R .\nsvn update<\/code><\/span><\/pre>\n\n\n
    Backup and restore process in SVN<\/h2>\n\n\n\n
    Interviewers often expect two backup patterns: hotcopy<\/strong> for fast full copies and dump\/load<\/strong> for portable backups and migrations.<\/p>\n\n\n
    # Full repository backup<\/span>\nsvnadmin hotcopy \/var<\/span>\/svn\/project \/backup\/project-hotcopy\n\n# Logical backup<\/span>\nsvnadmin dump \/var<\/span>\/svn\/project > \/backup\/project.dump\n\n# Restore to a new repository path<\/span>\nsvnadmin create \/var<\/span>\/svn\/project-restored\nsvnadmin load \/var<\/span>\/svn\/project-restored < \/backup\/project.dump<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Important: these commands run on server-side repository paths, not on a local working copy checkout.<\/p>\n\n\n\n
    How to set up SVN and authentication (quick reference)<\/h2>\n\n\n\n
    SVN is commonly served either through svnserve<\/code> or Apache HTTP server with WebDAV SVN modules. The right choice depends on your access, security, and integration requirements.<\/p>\n\n\n\n
    Serving option<\/th>Strength<\/th>Typical auth approach<\/th>When teams choose it<\/th><\/tr><\/thead>
    svnserve<\/td>Simple, lightweight<\/td>Built-in passwd\/authz files<\/td>Internal networks, straightforward setups<\/td><\/tr>
    Apache + SVN modules<\/td>HTTP(S), mature integration<\/td>HTTP auth methods plus authz rules<\/td>Enterprise environments, centralized web auth<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Minimal svnserve setup example<\/h3>\n\n\n
    # Create repository<\/span>\nsvnadmin create \/srv\/svn\/myrepo\n\n# Start svnserve daemon rooted at \/srv\/svn<\/span>\nsvnserve -d -r \/srv\/svn<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n
    # \/srv\/svn\/myrepo\/conf\/svnserve.conf<\/span>\nanon-access = none\nauth-access = write\npassword-db = passwd\nauthz-db = authz<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n
    # \/srv\/svn\/myrepo\/conf\/passwd<\/span>\n[users]\nalice = strong-password\nbob = another-password<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n
    # \/srv\/svn\/myrepo\/conf\/authz<\/span>\n[\/]\nalice = rw\nbob = r<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    10 SVN interview questions to practice<\/h2>\n\n\n\n
    • What is SVN, and how is centralized version control different from distributed models?<\/li>
    • What are trunk, branches, and tags, and how are they used in release workflows?<\/li>
    • What does \u201csynchronizing with repository\u201d mean in your client\/tooling context?<\/li>
    • What is the difference between svn update<\/code> and svn commit<\/code>?<\/li>
    • How do you generate and apply patches in SVN?<\/li>
    • How do you handle merge conflicts during update?<\/li>
    • How would you force local files to match repository state?<\/li>
    • How do you design a practical trunk\/branch\/tag strategy?<\/li>
    • How do you back up and restore an SVN repository?<\/li>
    • How do you configure authentication and authorization for SVN access?<\/li><\/ul>\n\n\n\n
      Common pitfalls and best practices<\/h2>\n\n\n\n
      • Always run svn update<\/code> before commit to reduce avoidable conflicts.<\/li>
      • Treat tags as read-only by team policy.<\/li>
      • Use clear, audit-friendly commit messages.<\/li>
      • Back up repositories on a schedule and test restore procedures.<\/li>
      • Use least-privilege authz rules (read-only where possible).<\/li>
      • Do not run destructive commands like svn revert -R .<\/code> unless you are sure local changes are disposable.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
        A practical, interview-focused guide to Subversion (SVN) concepts and commands. Learn how to explain trunk\/branch\/tag, update vs commit, conflict handling, patching, backup\/restore, and auth setup with confidence.<\/p>\n","protected":false},"author":1,"featured_media":3403,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[52],"tags":[641,647,766,507,1567,482,394,1561,1563,1566,395,1562,1564,1565,637,1568],"class_list":["post-372","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-interview-questions-answers","tag-answers","tag-best","tag-interview","tag-list","tag-list-of-svn-interview-questions","tag-questions","tag-subversion","tag-subversion-interview","tag-subversion-interview-questions","tag-subversion-interview-questions-and-answers","tag-svn","tag-svn-interview","tag-svn-interview-questions","tag-svn-interview-questions-and-answers","tag-top","tag-top-svn-interview-questions"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/372","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=372"}],"version-history":[{"count":4,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/372\/revisions"}],"predecessor-version":[{"id":79247,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/372\/revisions\/79247"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/3403"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=372"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=372"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=372"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}