Browse Certification Practice Tests by Exam Family

Series 14: Broker-Dealer Operations

Try 10 focused Series 14 questions on Broker-Dealer Operations, with explanations, then continue with the full Securities Prep practice test.

Series 14 Broker-Dealer Operations questions help you isolate one part of the FINRA outline before returning to a mixed practice test. The questions below are original Securities Prep practice items aligned to this topic and are not copied from any exam sponsor.

Open the matching Securities Prep practice route for timed mocks, topic drills, progress tracking, explanations, and the full question bank.

Topic snapshot

ItemDetail
ExamFINRA Series 14
Official topicFunction 3 — Broker-Dealer Operations
Blueprint weighting9%
Questions on this page10

Sample questions

Question 1

For a broker-dealer’s regulatory reporting process (for example, trade or position reporting), which record BEST demonstrates adequate evidence of supervisory review?

  • A. An email stating “reports look good” without referencing the specific output reviewed
  • B. A written supervisory procedure stating reports must be reviewed daily
  • C. A dated, attributable sign-off identifying the reviewer and showing exceptions were investigated and resolved
  • D. A saved copy of the report output with no reviewer attribution

Best answer: C

Explanation: Defensible supervisory evidence ties a specific reviewer and review date to the output reviewed and the disposition of any exceptions.

Evidence of supervisory review must be specific, attributable, and retrievable. The strongest record shows who performed the review, when it occurred, what reporting output was reviewed, and how any exceptions were dispositioned. A generic policy, an unauthenticated report copy, or an untethered email does not reliably prove a meaningful review occurred.

For reporting processes, regulators expect supervisory reviews to be documented in a way that is objective and defensible in an exam. Adequate evidence typically shows (1) attribution to the supervisor/principal, (2) the date/time of the review, (3) the specific output or exception queue reviewed (so it is clear what was in scope), and (4) the investigation and resolution or escalation of exceptions. This creates an audit trail that supports both the firm’s monitoring obligations and the integrity of the reporting process. Records that are generic (policy-only), not attributable (no reviewer), or not tied to a particular review population are weak because they do not demonstrate that an effective review actually occurred.

  • Policy-only documentation shows expectations but not that a review happened.
  • Unauthenticated report retention helps recordkeeping but does not evidence supervision.
  • Generic “looks good” email lacks scope and exception disposition, so it is not a reliable audit trail.

Question 2

A broker-dealer runs an end-of-day automated comparison between the equity trade blotter (executed quantity/price, capacity, and commission/markup fields) and the customer confirmation output file. Any trade with a missing confirmation or a mismatch in price, capacity, or charges is held for review before confirmations are released.

Which SEC Rule 10b-10 concept is this control primarily designed to support?

  • A. Accurate transaction and remuneration disclosures on confirmations
  • B. Supervising communications to ensure they are fair and balanced
  • C. Reconciling customer cash and securities balances for customer statements
  • D. Documenting the basis for a suitability/best interest determination

Best answer: A

Explanation: Rule 10b-10 confirmations must accurately reflect executed trade terms, the firm’s capacity, and customer charges, and the blotter-to-confirm compare is designed to catch errors or omissions.

Rule 10b-10 focuses on what must appear on a customer trade confirmation, including key execution details, whether the firm acted as agent or principal, and the related commission/markup. A trade blotter-to-confirmation reconciliation is a practical control to ensure those required fields are complete and accurate before the confirmation is sent.

SEC Rule 10b-10 confirmations are intended to give customers a reliable record of what happened in the transaction and what the firm earned on it. In practice, that means the confirmation should match the executed trade (e.g., security, quantity, price), clearly state the firm’s capacity (agent or principal), and accurately disclose the customer’s transaction-related charges/compensation (e.g., commissions or markups/markdowns, as applicable).

A reconciliation that compares the firm’s official execution record (the trade blotter) to the confirmation output is a core operational control because it:

  • detects missing confirmations (nothing sent for an executed trade)
  • detects inaccurate confirmations (price/quantity/capacity/charges discrepancies)

The key idea is ensuring the customer-facing confirmation is a faithful, complete reflection of the executed trade and required disclosures.

  • Suitability/best interest is evidenced through recommendations, profiles, and surveillance, not confirmation-field matching.
  • Customer statement reconciliation is focused on periodic account balances/positions, not trade-by-trade confirmation content.
  • Communications supervision addresses advertising/correspondence approval and review, not 10b-10 confirmation accuracy.

Question 3

A retail customer opened a brokerage account in January 2022. The firm’s WSPs state it will request customers to confirm or update “essential account information” at least every 36 months, consistent with FINRA Rule 4512. In February 2026, during a FINRA exam, the firm cannot show any 36‑month update request for this account and has no documented “reasonable efforts” to obtain updates.

What is the most likely outcome for the firm?

  • A. A recordkeeping/supervision deficiency for failing to evidence required update efforts
  • B. No issue, because customers must self-report changes to their account information
  • C. An automatic requirement to freeze the account until all information is re-verified
  • D. A requirement to file a SAR solely because the periodic update was not documented

Best answer: A

Explanation: FINRA will typically cite the firm for not making and documenting the required periodic update/reasonable-efforts process under Rule 4512.

Rule 4512 requires firms to make reasonable efforts to obtain and maintain essential customer account information and to evidence those efforts, including periodic update requests. If the firm cannot demonstrate it sent the required update request and follow-ups (or an equivalent documented process), FINRA will most likely treat it as a books-and-records and supervisory control weakness requiring remediation.

The core issue is not whether the customer actually changed any information, but whether the firm can demonstrate a compliant process to maintain essential customer account information. Under FINRA Rule 4512, firms must make reasonable efforts to obtain and keep required account information current and to create records that evidence those efforts. When a firm’s procedures call for a periodic (e.g., 36‑month) request to confirm/update information, the firm must be able to produce documentation showing the request was made (and any follow-up efforts) for the account. If the firm cannot, the likely exam consequence is a deficiency (and potential rule violation), along with required corrective action such as performing the update outreach, enhancing WSPs, and improving supervisory evidence and exception tracking. The key takeaway is that “if it isn’t documented, it didn’t happen” from a recordkeeping perspective.

  • Customer responsibility is insufficient because the firm must make and evidence reasonable efforts to maintain required account records.
  • Freezing the account is not an automatic Rule 4512 consequence; remediation is typically process and documentation-driven.
  • SAR filing is not triggered solely by missing periodic-update documentation without suspicious activity indicators.

Question 4

Your firm is preparing its quarterly regulatory filing package (prepared by Finance and submitted through the regulator’s portal). The compliance principal performs a supervisory review before submission. After a recent internal audit, you learn the firm retains only the final submitted PDF and does not retain the workpapers or evidence of review.

Exhibit: Current retained records (per audit)

- Final submitted PDF
- Portal submission confirmation email

What is the best next step to bring the process to a defensible supervisory-evidence standard for the next filing cycle?

  • A. Use an email from the reviewer as the only evidence of review
  • B. Reconstruct support only if a regulator later requests it
  • C. Build and retain a controlled filing packet with support and dated review sign-off
  • D. Retain only the final PDF and submission confirmation as official records

Best answer: C

Explanation: A defensible standard requires retaining the inputs, reconciliations/variance support, documented exception resolution, and a dated supervisory attestation tied to the submitted version.

Regulatory reporting supervision must be evidenced, not just performed. The firm should retain a reviewable packet that shows what data and reconciliations were relied on, what variances/exceptions were resolved, who reviewed it, when the review occurred, and which final version was submitted. This creates a defensible audit trail for the reporting process.

For regulatory filings, a “defensible” supervisory review record typically ties three things together: (1) the version submitted, (2) the underlying support that shows how key figures were derived and reconciled, and (3) documented supervisory review/approval before submission. In practice, the firm should maintain a controlled filing packet that includes the draft and final versions, source reports and reconciliations, variance explanations and any corrections made, and a dated reviewer attestation (or workflow sign-off) that is linked to the final submission. The packet should be retained in accordance with the firm’s recordkeeping controls so it can be promptly produced and demonstrates what the reviewer actually evaluated.

The key is to evidence both the review and the basis for the numbers, not merely proof that something was filed.

  • Final-only retention fails because it does not evidence supervisory diligence or the basis for the reported figures.
  • Email-only sign-off is usually insufficient without the underlying workpapers and version control tying the sign-off to what was filed.
  • Reconstruct on demand is weak because records should be retained contemporaneously to show what was reviewed and resolved at the time.

Question 5

A broker-dealer uses automated pre-trade controls for program (basket) trading. For each strategy, the order management system (OMS) calculates projected intraday net notional exposure as:

Projected net = current net + (basket buys − basket sells)

The OMS must block any basket that would cause projected net to exceed the strategy’s intraday net limit; any override requires written approval by the designated risk principal and documentation on the order ticket.

Exhibit: Intraday risk snapshot (USD notionals)

StrategyCurrent netNet limitBasket buysBasket sells
US Equity Index Arb$32,000,000$40,000,000$12,000,000$3,000,000

Which action best aligns with the firm’s control for this basket?

  • A. Keep the block; require documented risk-principal override
  • B. Split into two baskets so each is under the $40 million limit
  • C. Release; gross basket notional is $15 million, under the limit
  • D. Release; projected net is $37 million, under the limit

Best answer: A

Explanation: Projected net is $32M + ($12M − $3M) = $41M, so the basket must be blocked absent an approved override.

The control is based on projected intraday net exposure for the strategy, not gross basket size. Using the firm’s formula, the basket increases net exposure by $9 million, taking the strategy from $32 million to $41 million. Because $41 million exceeds the $40 million limit, the OMS should block the order unless an appropriately approved override is documented.

Pre-trade and intraday risk limits for high-volume basket activity are typically applied to a defined exposure metric (here, strategy net notional) and enforced automatically to prevent limit breaches before execution. The correct application is to compute the incremental net effect of the basket and add it to the strategy’s current net exposure:

  • Basket net impact = buys − sells = $12M − $3M = $9M
  • Projected net exposure = current net + impact = $32M + $9M = $41M

Since the projected net exceeds the $40M limit, the compliant workflow is to keep the system block in place unless the firm’s documented override process is followed (risk-principal approval and ticket documentation). The key takeaway is that controls should not be bypassed by reformatting orders to avoid the limit.

  • Netting error subtracts the basket impact from current exposure instead of adding it.
  • Wrong metric relies on gross basket size even though the limit is defined as net exposure.
  • Control circumvention splitting orders to evade a limit defeats the purpose of automated risk controls.

Question 6

Which statement is most accurate regarding beneficial ownership and accumulation reporting under Sections 13(d) and 13(g) of the Exchange Act?

  • A. Beneficial ownership excludes securities held in a brokerage account because the broker is the record owner.
  • B. A Schedule 13G filer must switch to Schedule 13D if its purpose changes to influencing or changing control of the issuer.
  • C. Any investor owning more than 5% may file Schedule 13G as long as it has no current plans to sell.
  • D. Sections 13(d) and 13(g) filings are made by broker-dealers on behalf of customers who exceed 5% ownership.

Best answer: B

Explanation: Schedule 13G is limited to specified categories (e.g., passive) and becomes unavailable when control intent is present, triggering Schedule 13D reporting.

Schedule 13D is the default reporting framework for persons who cross the 5% beneficial ownership threshold and are not eligible for Schedule 13G. Schedule 13G is a streamlined alternative only for specified types of holders (including passive holders), and it is no longer appropriate once the holder’s intent shifts toward influencing or changing control. In that case, the holder must transition to Schedule 13D reporting.

The core distinction is eligibility and intent. Section 13(d) generally requires detailed public reporting (Schedule 13D) when a person becomes a more-than-5% beneficial owner and does not qualify to use the shorter Schedule 13G. Section 13(g) allows Schedule 13G only for certain categories of investors, including passive investors, and it is conditioned on not having a purpose or effect of changing or influencing control of the issuer. If a person that has been reporting on Schedule 13G later develops control-related intent (for example, seeking influence over management or corporate actions), the appropriate framework is Schedule 13D, so the filer must move off 13G and report on 13D. A key compliance takeaway is to monitor for changes in intent and activity that would make 13G no longer available.

  • Overbroad 13G availability fails because 13G is not available to “any” 5% holder and is not based on whether the holder plans to sell.
  • Street name misconception fails because beneficial ownership focuses on voting and/or investment power, not record ownership.
  • BD files for customers fails because the reporting obligation is on the beneficial owner (the person/entity with the ownership power), not automatically on the broker-dealer.

Question 7

A broker-dealer is designing its books-and-records control framework.

Treatment 1: Operations is accountable for creating/capturing trade and customer account records in the firm’s systems, maintaining retention/retrieval controls with IT/records management support, and evidencing completeness and integrity; Compliance sets recordkeeping requirements in WSPs, provides training, performs periodic testing, and escalates deficiencies.

Treatment 2: Compliance is accountable for day-to-day capture, indexing, and reconciliation of operational records (e.g., blotters and confirms), while Operations only supports retrieval requests.

Which treatment best matches an appropriate assignment of ownership?

  • A. Treatment 2
  • B. Both treatments are appropriate if Compliance approves the retention schedule
  • C. Neither treatment is appropriate because IT must be the record owner
  • D. Treatment 1

Best answer: D

Explanation: The business/operations function should own record creation/capture and integrity controls, while compliance sets requirements and independently tests and escalates.

An effective books-and-records framework assigns first-line ownership for creating, capturing, and maintaining records to the business/operations functions that generate them. Compliance typically owns the governance layer—WSP requirements, training, independent monitoring/testing, and escalation—rather than performing day-to-day record production activities. This separation improves accountability and evidentiary defensibility.

Books-and-records controls work best when ownership aligns to who generates the record and who provides independent oversight. Operations (and the relevant business areas) should be accountable for the end-to-end record lifecycle in production systems—accurate creation/capture, completeness, tamper-resistant retention, and timely retrieval—often with IT/records management as control operators or service providers. Compliance should translate regulatory requirements into policies/WSPs, deliver guidance and training, and independently test that operational controls are working (including vendor oversight and remediation tracking). Making compliance responsible for day-to-day capture/reconciliation of operational records blurs first- and second-line roles and weakens accountability for record integrity.

Key takeaway: assign operational record ownership to the producing function, with compliance providing requirements and independent assurance.

  • Second line doing first-line work is weak because compliance oversight should be independent from daily record production and reconciliation.
  • Approval alone isn’t ownership because signing off on retention schedules doesn’t shift accountability for capture and integrity controls.
  • IT as owner is tempting, but IT typically enables controls; the producing business function remains accountable for the records.

Question 8

During a FINRA Rule 4511 records test, you review how the firm preserves evidence of principal approval for retail emails. Firm policy requires retail communications and related approvals to be retained for at least 3 years (first 2 years readily accessible).

Exhibit: Exception tracker (single row)

Control: Retail email pre-use approval
Evidence stored: SharePoint /Marketing/Approved-Email
File type: .docx (editable)
Version history: OFF
Retention setting: 90 days
Owner note: "Replace prior version when updated"

Based on the exhibit, which interpretation is best supported?

  • A. Only the final email sent must be retained, not approvals
  • B. Retention and integrity controls are not compliant as configured
  • C. The setup is compliant because SharePoint is an electronic repository
  • D. A 90-day retention is acceptable if supervisors approve pre-use

Best answer: B

Explanation: The exhibit shows both an insufficient retention period and a setup that permits undetectable alteration/overwrite of required records.

FINRA Rule 4511 requires firms to make and preserve required books and records, including supervisory evidence, in a manner that protects record integrity and meets required retention periods. The exhibit shows a 90-day retention setting despite a 3-year requirement, and it also shows editable files with version history turned off and an overwrite practice, which undermines record integrity. Those facts support a records-control deficiency.

Rule 4511 focuses on creating and preserving business records (including supervisory approvals and exception evidence) so they are complete, accurate, and retrievable for the required retention period. When records are stored electronically, the firm must also control integrity—i.e., prevent or detect alteration and avoid practices that effectively “replace” prior required records.

Here, the exhibit supports two clear problems: the retention setting (90 days) conflicts with the stated 3-year requirement, and the combination of editable files, version history turned off, and an instruction to replace prior versions means the firm may not be able to demonstrate what was approved and when. A compliant interpretation is that retention must be extended and the storage method must preserve prior versions with defensible auditability.

  • “Repository equals compliance” misses that retention and integrity controls must also meet requirements.
  • “Approvals aren’t records” is inconsistent with supervisory evidence being part of required books and records.
  • “Approval fixes retention” confuses supervisory action with the separate obligation to preserve records properly.

Question 9

A broker-dealer’s internal audit finds inconsistent handling of required records across departments: Operations maintains trade blotters in the OMS, Sales supervisors review correspondence in a separate tool, and IT manages an email archive vendor. The report concludes that “no single process identifies what records exist, who is accountable for their integrity, or how exceptions are escalated.” As the compliance official, which action best aligns with a durable books-and-records control framework and appropriate ownership?

  • A. Move all recordkeeping duties to Compliance to ensure independence
  • B. Create record inventory; Ops owns controls; Compliance monitors/tests
  • C. Require reps to screenshot messages and upload monthly to SharePoint
  • D. Accept vendor archiving as sufficient; stop internal retention reviews

Best answer: B

Explanation: A defensible framework assigns record ownership to the producing/operational function while Compliance sets standards, performs testing, and drives escalation and remediation.

A strong books-and-records program starts with a complete record inventory and clear accountability for capture, retention, and retrieval. The operational area that generates and maintains each record should own the day-to-day controls, while Compliance establishes requirements, performs periodic testing, and ensures issues are escalated, remediated, and evidenced. This structure supports record integrity and supervisory accountability across systems and vendors.

A broker-dealer’s books-and-records framework should be designed so that every required record is (1) identified, (2) mapped to where it is created and stored, (3) assigned to an accountable owner, and (4) supported by monitoring, testing, and escalation. In practice, the business or Operations function that produces and uses the record is best positioned to own the process controls (capture, completeness checks, exception resolution, and retrieval readiness), while Compliance owns the governance layer (policies/standards, risk-based testing, surveillance of breaks, and documentation of remediation). IT and vendors are key service providers, but they do not replace supervisory accountability; controls must still be evidenced, tested, and subject to issue management. The goal is clear ownership plus independent oversight, not “everyone manages their own way.”

  • Compliance as sole owner weakens first-line accountability and creates an impractical operating model.
  • Vendor reliance is insufficient because third-party tools still require firm-level oversight, testing, and exception handling.
  • Manual screenshots increases integrity and completeness risk and is not a robust, auditable control design.

Question 10

A broker-dealer filed its June 30, 2025 quarterly FOCUS Report (Part II) through eFOCUS on July 24, 2025. On August 5, the controller discovers a balance sheet error: a -150,000 unsecured receivable was incorrectly netted against a payable, which overstated the firm’s reported net capital by -150,000. The firm’s minimum net capital requirement is -250,000, and even after correction the firm remains above the requirement. The CFO tells compliance to “fix it in the next quarter” and not amend anything.

As the compliance official, what is the primary compliance red flag/control concern raised by this situation?

  • A. Potential best execution violations from financing-related trading activity
  • B. A market manipulation risk caused by netting payables and receivables
  • C. An AML reporting failure requiring a SAR due to a balance sheet reclassification
  • D. Failure to escalate and file an amended FOCUS report to correct a filed inaccuracy

Best answer: D

Explanation: An identified error that impacts reported net capital is a regulatory filing inaccuracy that should be escalated and corrected via an amended FOCUS submission with documented review.

Once the firm identifies that a filed FOCUS report is inaccurate in a way that affects net capital, it is a red flag that the firm may be leaving a misleading regulatory filing uncorrected. The appropriate control response is to escalate to the FINOP/finance and compliance leadership, determine materiality and any related notifications, and resubmit an amended filing with an audit trail.

Regulatory reports like the FOCUS report are relied on by regulators to monitor a broker-dealer’s financial condition, including net capital. When the firm discovers that a filed report contains an error that changes reported net capital, the core compliance risk is allowing an inaccurate filing to stand and failing to follow an escalation-and-correction workflow.

A defensible control response is to:

  • Escalate promptly to the FINOP (and CCO/CFO as applicable) and open a tracked issue
  • Assess the impact of the error (including whether any additional notices are triggered) and remediate the books/records
  • Submit an amended FOCUS report via the required filing system and retain evidence of review, approval, and resubmission

Even if the firm remains above its minimum requirement, the key obligation is accurate reporting and timely correction once an error is identified.

  • Wait until next quarter is a supervisory gap because it leaves a known inaccurate regulatory filing uncorrected.
  • Best execution is unrelated because the issue is financial reporting accuracy, not order handling quality.
  • Manipulation framing is misplaced because netting/classification errors are not, by themselves, trading conduct.
  • SAR trigger is not supported where the facts show an accounting error rather than suspicious customer activity.

Continue with full practice

Use the Series 14 Practice Test page for the full Securities Prep route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Free review resource

Use the Series 14 Cheat Sheet on SecuritiesMastery.com when you want a compact review before returning to the FINRA Series 14 Practice Test page.

Revised on Sunday, May 3, 2026