Pass the Construction Specifications Institute CDT Certification CDT Questions and answers with ExamsMirror

In CSI-based drawing conventions, a scaled view is one drawn at a stated scale so that actual dimensions can be measured directly from the drawing (e.g., 1:100, 1/4" = 1'-0"). CSI’s Uniform Drawing System (UDS) treats floor plans, roof plans, and foundation plans as primary orthographic views prepared at a defined scale for dimensioning and coordination between disciplines. These are the standard “working drawings” for construction.

Foundation plan (Option B)A foundation plan is an orthographic plan view drawn to a specific scale showing footings, slabs, and foundations with dimensions and notes. It is intended for measurement and layout, and CSI references it as one of the basic scaled plan views of the project drawings.

Why the other options are not correct:

A. Perspective – Perspectives are pictorial views used for visualization and presentation. CSI notes that such views are typically not used for taking dimensions and may not be drawn to a true working scale.

C. Riser diagram – Riser diagrams (for plumbing, fire protection, electrical, etc.) are diagrammatic, showing relationships and routing, not physical locations at scale. They are expressly identified as “not to scale” in most construction document standards.

D. Isometric – Isometric drawings are a type of pictorial/axonometric view used to show three-dimensional relationships. While they can sometimes be constructed proportionally, CSI’s guidance treats them as diagrammatic/pictorial views rather than the primary scaled working views used for dimensioning work in the field.

CSI References (no links):

CSI Uniform Drawing System (UDS) modules on drawing types and views (plan, elevation, section, diagrammatic views).

CSI Project Delivery Practice Guide – discussion of scaled plan views as part of the construction documents set.

Comprehensive and Detailed Explanation From Exact Extract (CSI-based)

CSI’s treatment of warranties in construction distinguishes among several types, including:

Warranty of title – assures that the seller/contractor has good title to goods and that they are free of liens or claims.

Implied warranties – such as merchantability and fitness for a particular purpose, arising under applicable law for goods.

Express warranties – explicitly stated in the contract documents or manufacturer literature, which may include extended warranties.

In the construction context, CSI’s project delivery and specification guidance emphasizes that extended warranties (often called special warranties in specifications):

Survive completion and acceptance of the project.

Provide remedies to the owner for defects in materials and/or workmanship that appear after substantial completion, often beyond the standard one-year correction period.

Are commonly used for critical building components (e.g., roofing systems, waterproofing, major equipment) and may run for 5, 10, or more years.

This directly matches the question’s language: a warranty “used to provide a remedy to the owner for material defects or failures after completion and acceptance of construction.” That is precisely the purpose of an extended warranty in CSI-style contract documents and specifications, making Option D correct.

Why the other options are incorrect:

A. Warranty of titleThis deals with ownership and freedom from liens, not performance of materials or systems after completion. It does not address post-completion material defects.

B. Implied warranty of merchantabilityThis is a legal concept for goods: that they are fit for ordinary purposes. While it may apply in background law, it is not the specific contractual tool that owners rely on in construction documents to secure long-term remedies for material defects.

C. Purchase warranty“Purchase warranty” is not a standard CSI-defined category of construction warranty. Product or manufacturer warranties may be obtained at purchase, but the CSI terminology used in specifications and project delivery guidance is typically standard warranty, special warranty, or extended warranty, not “purchase warranty.”

Key CSI References (titles only):

CSI Project Delivery Practice Guide – sections on Warranties, Guarantees, and the Correction Period.

CSI Construction Specifications Practice Guide – guidance on specifying warranties (including extended warranties) in Division 01 and technical sections.

CSI CDT Body of Knowledge – “Contract Provisions: Warranties and Guarantees.”

Comprehensive and Detailed Explanation From Exact Extract (CSI-aligned, paraphrased)

Integrated Project Delivery (IPD), as described in CSI’s project delivery materials, is a collaborative project delivery method that:

Involves key project participants early in the project,

Uses shared risk and reward, and

Promotes integration of people, systems, business structures, and practices into a process that optimizes project results.

CSI’s discussion of IPD identifies the core IPD team as typically including:

The Owner

The Architect/Engineer (Design Professional)

The Contractor (often a general contractor or construction manager at risk)

In IPD, the contractor is deliberately brought into the project early, often during conceptual or schematic design, to:

Provide constructability input

Contribute cost estimating and scheduling

Help optimize means and methods and coordinate with major trades

Among the choices given, the participant that is clearly recognized as a primary IPD participant in CSI-oriented explanation of IPD is the:

C. Contractor

Why the other options are not the best answer:

A. Authority having jurisdiction (AHJ)The AHJ (e.g., building department, fire marshal) is always involved in permitting and inspections, regardless of delivery method. However, they are not part of the project’s contractual IPD team, nor do they share in IPD contractual risk/reward structures.

B. Commissioning agentA commissioning agent (or authority) may participate in IPD projects, but is not a mandatory or defining core party. Commissioning can be part of many delivery methods (Design-Bid-Build, CM at Risk, Design-Build, IPD). CSI’s general description of IPD focuses on owner–designer–contractor integration.

D. InspectorInspectors (code inspectors, special inspectors) are similar to the AHJ functions—important to the project but external to the project’s contractual structure and not specific to IPD. They serve regulatory and quality verification roles across all delivery methods.

Thus, in the context of CSI’s explanation of Integrated Project Delivery, the clearly correct answer is Option C – Contractor.

Key CSI-Related References (titles only):

CSI Project Delivery Practice Guide – chapters on Project Delivery Methods and Integrated Project Delivery.

CSI CDT Study Materials – comparisons of Design-Bid-Build, CM at Risk, Design-Build, and IPD, including team composition.

CSI presentations and educational modules on collaborative and integrated delivery methods.

Within CSI’s framework for contract documents, the term “Agreement” (capitalized) has a specific meaning. It refers to the formal written contract for construction between the Owner and the Contractor.

CSI describes the typical structure of the contract documents as including:

The Agreement between Owner and Contractor (such as AIA A101 or similar),

The Conditions of the Contract (General and Supplementary Conditions),

Drawings, Specifications, and Addenda,

And other documents listed in the Agreement.

The Agreement sets out key commercial terms (contract sum, contract time, identification of the work, list of contract documents, progress payments, etc.) and binds the owner and contractor to the Conditions of the Contract and the remainder of the documents.

Why the other options are not correct:

A. Agreement between the owner and the architect/engineer – This is usually a separate professional services agreement (often titled Owner–Architect Agreement or similar) and is not what CSI and AIA mean by “the Agreement” within the construction contract set.

B. The general conditions of the contract for construction – The General Conditions are a separate document; they become part of the contract when they are incorporated by reference in the Agreement, but they are not themselves “the Agreement.”

D. Agreement between the contractor and the subcontractor – This is a separate subcontract document, not part of the owner–contractor contract set defined in the project manual.

CSI’s practice material on contract formation and document relationships consistently identifies “the Agreement” as the contract between the Owner and the Contractor, hence Option C is correct.

CSI’s description of project roles is very clear about the owner’s role in project delivery:

The owner is the party that:

Identifies the need or opportunity and therefore initiates the project.

Provides the funding for design and construction.

Retains the design and construction teams and selects the project delivery method.

Ultimately assumes the primary financial and project risk, because the owner is the one investing in and depending on the completed facility.

In contrast:

The designer (architect/engineer) is responsible for planning and design, preparing construction documents, and administering the construction contract on the owner’s behalf, but does not typically initiate the project or provide funding.

The contractor is responsible for constructing the project in accordance with the contract documents; the contractor bears construction execution risk, but not the basic project-initiative and funding role.

Suppliers provide materials/equipment and have no overarching control over the project delivery process.

The question lists all of the characteristics that CSI attributes to the owner:

“initiates the project, assumes the risk, controls and manages the design and construction process, and provides the funding.”

Thus, the correct answer is Option D – Owner.

CSI references (by name only, no links):

CSI Project Delivery Practice Guide – “Participants in Project Delivery” (owner, designer, constructor, suppliers)

CDT Body of Knowledge – descriptions of owner responsibilities and risk

In CSI / CDT usage, quality assurance (QA) and quality control (QC) are distinct concepts:

Quality Assurance (QA) focuses on planning, processes, and preventive actions put in place before and during the work to help ensure the required quality will be achieved. It is about systems and procedures.

Quality Control (QC) focuses on inspection, testing, and verification to determine whether the constructed work conforms to the requirements of the Contract Documents.

Typical examples:

QA examples (process-oriented):

Developing and following a project-specific quality plan.

Coordinating scheduling and sequencing of the work so trades do not interfere with one another and work is done under appropriate conditions.

Prequalification of contractors, subcontractors, and testing agencies.

Establishing and enforcing submittal procedures and preinstallation meetings.

QC examples (inspection/testing):

Field testing (e.g., concrete cylinder tests, soil compaction tests).

Visual inspection of installed work.

Checking that installed products match submittals and specifications.

Looking at the options:

A. Performing compaction testing – This is a field test used to verify densities and is clearly quality control, not QA.

B. Field observations – These are performed by the A/E or others to observe and verify that work appears to be in general conformance; this is quality control.

C. Validating quantities for payment – This is a contract administration / cost control activity, not primarily a quality activity.

D. Scheduling and sequencing of the work – This is planning and coordination done in advance so the project can proceed efficiently, correctly, and without damaging completed work. Because it is a procedure-based, preventive activity, CSI places this type of planning under quality assurance.

Therefore, the example of quality assurance is “Scheduling and sequencing of the work” (Option D).

Relevant CSI / CDT References (titles only, no links):

CSI Project Delivery Practice Guide – sections on “Quality in Project Delivery” and distinctions between QA and QC.

CSI Construction Specifications Practice Guide – discussions of quality requirements, testing, and inspection.

CDT Body of Knowledge – domain on “Construction Phase: Quality Assurance and Quality Control.”

In CSI’s MasterFormat / SectionFormat framework, temporary facilities and controls (including temporary toilet facilities) are normally specified in Division 01 – General Requirements, specifically in the section often titled “Temporary Facilities and Controls” (e.g., 01 50 00).

CSI’s practice guides and CDT materials explain that:

Division 01 – General Requirements governs project-wide administrative and procedural requirements and many temporary facilities, including temporary utilities, temporary protection, and temporary sanitation (toilet facilities) for the contractor’s workforce.

These requirements apply across the entire project and are not limited to a single trade. That’s why Division 01 is the appropriate location instead of the trade divisions.

So, requirements such as:

Number, type, and cleaning of temporary toilets,

Responsibility for providing and maintaining them,

Locations and general standards for worker facilities,

are typically found in Division 01 – General Requirements, not in the plumbing design sections.

Why the other options are incorrect in CSI context:

A. Supplementary ConditionsSupplementary Conditions modify or add to the General Conditions of the Contract, usually to address project-specific legal, insurance, or procedural issues (local laws, bonding, liquidated damages, etc.). While they could mention sanitation in special cases, they are not the standard, typical place for detailed technical or procedural requirements for temporary toilets. Those belong in Division 01.

B. Division 22 – PlumbingDivision 22 contains requirements for permanent plumbing systems and components (domestic water, sanitary waste, fixtures, piping, etc.) as part of the completed facility. Temporary toilets for construction workers are not part of the permanent plumbing design; they are a temporary facility and therefore addressed in Division 01, not Division 22.

C. The Owner–Contractor AgreementThe Agreement defines contract sum, contract time, identification of the contract documents, and sometimes very high-level obligations, but it does not normally contain detailed requirements for items like temporary toilets. Those details are part of the specifications within the Project Manual, mainly Division 01.

Therefore, in line with CSI’s structure and recommended practice, Division 01 – General Requirements (Option D) is the correct answer.

Relevant CSI references (no URLs):

CSI MasterFormat – Division 01, including section 01 50 00 “Temporary Facilities and Controls.”

CSI Construction Specifications Practice Guide – Discussion of where to specify temporary facilities and contractor responsibilities.

CSI CDT Body of Knowledge – Use and organization of the Project Manual and Division 01.

Comprehensive and Detailed Explanation From Exact Extract (CSI-based)

CSI’s guidance on project record documents distinguishes between several types:

Record drawings – show what was actually installed (dimensions, locations, configurations).

Record specifications/project manual – the written requirements for the work, as issued and modified.

Record submittals – approved shop drawings, product data, and samples documenting the actual products and systems installed, including manufacturer names, model numbers, finishes, and installation instructions.

For replacement of a specific product, such as a broken insulated glazing unit, CSI instruction is that the most precise source is record submittals (Option D). These typically contain:

The exact manufacturer selected.

Product line, model number, glass type, coatings, spacers, gas fill, etc.

Any special fabrication notes or custom sizes.

Contact information or catalog data to facilitate reordering.

This is exactly the information a facility manager needs to “determine where and how to order” the replacement unit. That is why CSI emphasizes maintaining record submittals as part of the owner’s permanent facility information.

Why the other options are less appropriate:

A. Record drawingsRecord drawings (sometimes called “as-built” drawings) can provide size and location of the glazing unit, and possibly indicate type (e.g., “insulated glazing unit”). However, drawings rarely show the precise product manufacturer and model; at best, they reference detail markers or generic notes. They are helpful for field measurement and coordination, but not ideal for identifying the exact product to order.

B. Manufacturer’s representativeA manufacturer’s rep can help once you know the manufacturer and product, but first you need to identify which manufacturer and model were actually installed. Without the record submittals or similar documentation, the rep would be guessing. CSI places the identification of the installed product squarely in the realm of record submittals.

C. Project manualThe project manual (including the specifications) usually lists acceptable manufacturers and products, or performance requirements, but it does not necessarily tell you which one was actually used. If multiple manufacturers or options were permitted, the project manual alone cannot identify the exact unit to reorder.

Thus, under CSI’s treatment of project record documents and facility information, record submittals (Option D) are the best and most appropriate source for ordering an exact replacement product.

CSI reference concepts:

CSI Project Delivery Practice Guide – sections on “Project Closeout” and “Record Documents,” explaining the distinct roles of record drawings and record submittals.

CSI CDT Study Materials – topics describing record submittals as the owner’s record of actual installed products, used for maintenance and replacement.

CSI describes the facility manager as a key stakeholder during project closeout and turnover. Their role is to receive the information, materials, and training needed to operate the completed facility in accordance with the Owner’s Project Requirements (OPR).

Typical responsibilities for the facility manager at closeout, as outlined in CSI’s Project Delivery Practice Guide, include (paraphrased):

Participating in commissioning and training sessions.

Verifying receipt of operation and maintenance (O&M) manuals, warranties, and record documents.

Confirming that required spare parts, attic stock/excess materials, and special tools have been delivered.

Ensuring staff have sufficient training to operate building systems during the initial occupancy period.

This is captured best by Option A, which aligns closely with CSI’s description of closeout responsibilities for the facility manager.

Why the other options are not correct:

B. Coordinate with the architect a final clean-up and site restoration – Final cleaning and site restoration are responsibilities of the contractor, overseen by the A/E and owner. The facility manager may observe but is not normally the one coordinating this work in the contract documents.

C. Hire a new security company – Selecting or changing service vendors (like security firms) is an owner/facility operations business decision, not specifically identified in CSI’s project closeout procedures. It is not a standard closeout task defined in the construction documents.

D. Draft the final changes on the as-built documents – CSI differentiates between “project record documents” maintained by the contractor during construction and record drawings/specifications produced by the A/E (when required). The facility manager receives these but does not normally draft or edit them.

CSI References (no links):

CSI Project Delivery Practice Guide – chapters on Construction Phase and Facility Management/Closeout.

CSI Construction Specifications Practice Guide – sections on project closeout, O&M data, and attic stock.

CSI’s project delivery and CDT materials describe design as having a dual nature:

An aesthetic (or qualitative/artistic) side – concerned with form, appearance, spatial experience, and how the built environment is perceived and used.

A technical side – concerned with structural integrity, building systems, code compliance, constructability, performance, and cost.

In the broader project-management literature you’ve uploaded, the design and construction process is described as blending technical requirements with broader qualitative and organizational goals. For example, the project life cycle discussion notes that each stage involves both technical and managerial activities, reflecting the need to satisfy functional, performance, and experiential objectives simultaneously.

CSI’s CDT framework builds on this by emphasizing that:

The architect/engineer must respond to owner values (aesthetics, image, function) and

Technical constraints and criteria (codes, standards, performance, budget, schedule).

This is what is commonly summarized in CDT study materials as the “dual nature of design” – aesthetic and technical.

Why the other options do not match CSI’s phrasing:

A. Site and building – Both are important aspects of design, but CSI’s dual-nature concept is not expressed as site vs. building.

C. Programming and planning – These are phases or processes that precede or support design, not the two “natures” of design itself.

D. Innovation and authenticity – Desirable qualities, but not the canonical CSI pair.

Thus, the correct pair that matches CSI’s description of the dual nature of design is Option B – Aesthetic and technical.

CSI-aligned references (no URLs):

CSI Project Delivery Practice Guide – “The Design Stage” (discussion of design as both artistic/aesthetic and technical/problem-solving).

CSI CDT body of knowledge – conceptual overview of the designer’s responsibilities and