{"id":374,"date":"2026-10-14T00:21:01","date_gmt":"2026-10-14T00:21:01","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2014\/09\/22\/interview-questions-and-answer-for-perforce-version-control-tool\/"},"modified":"2026-10-14T00:21:01","modified_gmt":"2026-10-14T00:21:01","slug":"interview-questions-and-answer-for-perforce-version-control-tool","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/interview-questions-and-answer-for-perforce-version-control-tool\/","title":{"rendered":"Perforce Interview Prep: Essential p4 Commands for Workspaces, Changelists, and Admin Tasks"},"content":{"rendered":"\n

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

This guide is for engineers preparing for Perforce (Helix Core) interviews or maintaining existing Perforce environments. It focuses on practical commands from the original post, clarifies where each command fits, and highlights safety considerations for admin operations.<\/p>\n\n\n\n

\"perforce-interview-questions-answers\"<\/p>\n\n\n\n

Core Perforce commands interviewers often ask about<\/h2>\n\n\n\n

These are common command-level checks in interviews: file history inspection, changelist discovery, and status-based filtering.<\/p>\n\n\n

# Show each line in a file with revision attribution<\/span>\np4 annotate file.c\n\n# Last 10 changelists touching a project path<\/span>\np4 changes -m 10<\/span> \/\/depot\/project\/...<\/span>\n\n# Last 10 changelists by status<\/span>\np4 changes -m 10<\/span> -s submitted \/\/depot\/project\/...<\/span>\np4 changes -m 10<\/span> -s pending \/\/depot\/project\/...<\/span>\np4 changes -m 10<\/span> -s shelved \/\/depot\/project\/...<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Command<\/th>Best for<\/th>Interview angle<\/th><\/tr><\/thead>
p4 annotate<\/td>Line-by-line revision tracing<\/td>Debugging ownership and historical context<\/td><\/tr>
p4 changes -m N<\/td>Recent activity in a path<\/td>How to scope by depot path and limit result size<\/td><\/tr>
p4 changes -s status<\/td>Filtering by submitted\/pending\/shelved<\/td>Operational reporting by lifecycle state<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Ignoring files in a workspace: client view exclusions and P4IGNORE<\/h2>\n\n\n\n
The original post shows two ways to keep generated binaries (for example, .dll<\/code>) out of normal reconcile\/add flows: negative mappings in the client view and an ignore file via P4IGNORE<\/code>.<\/p>\n\n\n
# Example client view exclusions from the original article<\/span>\n-\/\/depot\/foo\/*.dll \/\/CLIENT\/foo\/*.dll<\/span>\n-\/\/depot\/foo\/...\/*.dll \/\/CLIENT\/foo\/...\/*.dll<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
The post also includes a compact variant:<\/p>\n\n\n
-\/\/depot\/foo...\/*.dll \/\/CLIENT\/foo...\/*.dll<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
References from the original post: Stack Overflow discussion<\/a>, exclude directories from Perforce commands<\/a>, and the P4IGNORE command reference<\/a>.<\/p>\n\n\n\n
\nflowchart TD\n    A[Edit files locally] --> B[Run Reconcile Offline Work]\n    B --> C{Excluded by view or P4IGNORE}\n    C -- yes --> D[Shown as excluded files]\n    C -- no --> E[Opened for add or edit]\n    E --> F[Review changelist]\n    F --> G[Submit]\n<\/pre>\n\n\n\n
Admin commands and interview prompts for Perforce superusers<\/h2>\n\n\n\n
The p4 admin<\/code> command family is used for service-level operations and is typically restricted to superusers.<\/p>\n\n\n
p4 admin checkpoint [ -z | -Z ] [ prefix ]\np4 admin journal [ -z ] [ prefix ]\np4 admin stop\np4 admin restart\np4 admin updatespecdepot [ -a | -s type ]\np4 admin resetpassword -a | -u user<\/code><\/span><\/pre>\n\n\n
Reference: p4 admin command reference<\/a>.<\/p>\n\n\n\n
Common admin interview questions<\/h3>\n\n\n\n
  • How do you take a Perforce backup?<\/li>
  • How do you restore a Perforce backup?<\/li>
  • How do you verify the health of repository metadata?<\/li>
  • What is the difference between p4 dbverify<\/code> and p4 verify<\/code>?<\/li><\/ul>\n\n\n\n
    Choosing metadata mechanisms: counters, keys, attributes, properties<\/h2>\n\n\n\n
    The original article distinguishes these mechanisms by simplicity, association with files, and visibility\/control needs.<\/p>\n\n\n\n
    Mechanism<\/th>Use when<\/th>Scope and behavior<\/th><\/tr><\/thead>
    p4 counter \/ p4 key<\/td>You need flat key\/value storage<\/td>Simple storage; typically no rich visibility model<\/td><\/tr>
    p4 attribute<\/td>Metadata is tied to files<\/td>Associated directly with file objects<\/td><\/tr>
    p4 property<\/td>You need admin-managed definitions and controlled visibility\/precedence<\/td>Used by Perforce applications such as P4V; not core server metadata behavior by itself<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
    p4 property -n name -v value\np4 counter mycounter 123\np4 key mykey 12\np4 attribute -n name -v value files...<\/code><\/span><\/pre>\n\n\n
    Commands that can permanently remove file data<\/h2>\n\n\n\n
    The original post explicitly warns that p4 archive -p<\/code> is one of the few commands that removes file data, and names p4 obliterate<\/code> as the other. Treat both as high-risk operations and validate policy before use.<\/p>\n\n\n\n
    Command<\/th>Risk level<\/th>Operational guidance<\/th><\/tr><\/thead>
    p4 archive -p<\/td>High<\/td>Use with caution; confirm retention and recovery requirements first<\/td><\/tr>
    p4 obliterate<\/td>High<\/td>Use only with explicit approval and change tracking<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Perforce integration topics often discussed in interviews<\/h2>\n\n\n\n
    • Git Fusion<\/li>
    • Swarm<\/li>
    • Replication<\/li><\/ul>\n\n\n\n
      For each integration topic, be prepared to explain why it is used, where it fits in your workflow, and the operational trade-offs.<\/p>\n\n\n\n
      Best practices<\/h2>\n\n\n\n
      • Scope commands by depot path (\/\/depot\/project\/...<\/code>) to reduce noise and risk.<\/li>
      • Prefer explicit exclusion rules for build artifacts to keep reconcile output clean.<\/li>
      • Separate interview knowledge into user commands vs superuser\/admin commands.<\/li>
      • Treat archive\/obliterate workflows as controlled change events with approvals and backups.<\/li>
      • Validate command syntax against your installed Helix Core version before production use.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
        A practical Perforce interview refresher focused on high-value commands and admin concepts from real usage. Learn how to query changelists, exclude files, use metadata options, and avoid risky data-removal mistakes.<\/p>\n","protected":false},"author":1,"featured_media":3543,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[370],"tags":[767,1824,766,507,1553,373,1825,1829,1826,1827,482,1830,341,637,381,1828],"class_list":["post-374","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-perforce","tag-answer","tag-control","tag-interview","tag-list","tag-most-asked","tag-perforce","tag-perforce-interview","tag-perforce-interview-qa","tag-perforce-interview-questions","tag-perforce-interview-questions-answers","tag-questions","tag-selected","tag-tool","tag-top","tag-version","tag-version-control-interview-questions-and-answer"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/374","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=374"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/374\/revisions"}],"predecessor-version":[{"id":79254,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/374\/revisions\/79254"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/3543"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=374"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=374"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=374"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}