Question 1

In the shown project network (Activity-on-Arrow), the excavation activity starts at Event 1 and finishes at Event 2 (the arrow's tail and head).

Accepted Answer

Introduction / Context: Network diagrams in project management (particularly Activity-on-Arrow, AOA) depict activities as arrows connecting two events (nodes). This question checks whether you can read the basic meaning of an activity arrow independent of its description or duration annotation. Given Data / Assumptions: An excavation activity is shown as an arrow between Event 1 and Event 2. No unique task subtype (e.g., footing) is explicitly labeled. Any numeric duration (e.g., 8 units) would be secondary to the definition. Concept / Approach: In AOA, the tail node indicates the start event, the head node indicates the finish event. The arrow itself is the activity. A label (if provided) names the activity; a duration (if provided) quantifies its time requirement. The fundamental interpretation is the logical sequence from start event to finish event. Step-by-Step Solution: 1) Identify the notation: arrow between Event 1 → Event 2.2) Interpret semantics: tail = start event, head = finish event.3) Recognize that specific sub-scope (e.g., footing) is not implied unless labeled explicitly.4) Conclude that the correct meaning is: the excavation starts at Event 1 and ends at Event 2. Verification / Alternative check: Standard AOA conventions in CPM literature define activities strictly as arrows joining two events that mark commencement and completion of that activity. Why Other Options Are Wrong: Activity of excavation of a footing: Overly specific; not stated by the network label. Activity of excavation which takes 8 units of time: Duration may exist but is not the primary definition. None of these: Incorrect because the AOA meaning matches option B exactly. Common Pitfalls: Confusing a descriptive task type (footing) with a generic excavation activity. Overemphasizing duration annotations instead of the logical start–finish definition. Final Answer: Activity of an excavation which starts at Event 1 and ends at Event 2.

Question 2

Milestone charts (used to highlight key checkpoints in a schedule) were introduced historically around the year 1930.

Accepted Answer

Introduction / Context: Milestone charts abstract a schedule into key events or deliverables. This question probes knowledge of the historical evolution of early scheduling tools relative to the Gantt chart era. Given Data / Assumptions: We must choose the approximate year of milestone chart origin. Choices span 1910–1950. Concept / Approach: Gantt charts were popularized in the 1910s for depicting activities over time. As scheduling practice matured, milestone-centric views appeared to emphasize checkpoints, approvals, or phase gates—commonly referenced to the early 20th century timeline, around 1930, in classical project management texts. Step-by-Step Solution: 1) Set context: Gantt (1910s) precedes milestone abstraction.2) Milestone emphasis gained traction in the subsequent decades.3) Historical consensus often cites 1930 for the milestone chart concept. Verification / Alternative check: Comparing multiple project management histories shows milestones emerging after early Gantt adoption and before mid-century network methods, aligning with 1930 better than earlier or much later dates. Why Other Options Are Wrong: 1910/1920: Too close to early Gantt adoption; milestone formalization was later. 1940/1950: Too late given already widespread use of milestone tracking by then. Common Pitfalls: Assuming milestones originated simultaneously with Gantt bars. Confusing the formalization of milestones with later network techniques. Final Answer: 1930.

Question 3

In project scheduling terminology, the estimated time required to perform a specific activity is called its duration.

Accepted Answer

Introduction / Context: Precise terminology underpins CPM/PERT analysis. Confusing duration, float, events, and dummies leads to planning and control errors. This question checks the exact term for the time needed to execute an activity. Given Data / Assumptions: An activity has an estimated completion time under normal conditions. We must name that quantity correctly. Concept / Approach: Duration is the planned time for an activity from its start to its finish. It is distinct from float (schedule flexibility), an event (a point in time marking start/finish), or a dummy (a zero-duration logical connector in AOA networks). Step-by-Step Solution: 1) Identify the quantity described: time needed to do the work.2) Map to definitions: duration = required time; float = allowance; event = node; dummy = zero-time logic.3) Conclude the correct term is duration. Verification / Alternative check: Standard CPM/PERT texts define activity time as duration; float is derived later from early/late times and critical path calculations. Why Other Options Are Wrong: Event: Instant in time, not a span. Dummy: Has no time; indicates logic only. Float: Not required time, but schedule leeway. Common Pitfalls: Using float and duration interchangeably. Assuming dummy activities consume time. Final Answer: Duration.

Question 4

In construction planning, a time and progress chart is commonly referred to as a Bar chart (Gantt chart).

Accepted Answer

Introduction / Context: Different visual tools serve distinct planning purposes. This question targets the everyday name used for a time–progress depiction of construction activities. Given Data / Assumptions: Time–progress chart of a construction job is considered. We must pick the conventional name used in practice. Concept / Approach: A bar chart (popularized by Henry Gantt) displays activities as horizontal bars over a calendar. While a Gantt chart is effectively the same artifact, options are separated to test recognition that the general term in site usage is often simply “bar chart.” Step-by-Step Solution: 1) Match “time–progress chart” to artifact: activities vs time bars.2) Recognize CPM and modified milestone charts are different constructs.3) Conclude the conventional label is Bar chart. Verification / Alternative check: Construction management references equate time–progress charts with bar/Gantt charts; CPM is a network analysis method, not merely a time–bar display. Why Other Options Are Wrong: Gantt chart: Equivalent in concept, but the canonical pick here is “Bar chart.” Modified milestone chart: Focuses on key checkpoints only. CPM chart: Emphasizes logic/critical path rather than simple bars. All of the above: Overinclusive; not all are the same artifact. Common Pitfalls: Equating CPM logic diagrams with simple time bars. Assuming milestones alone communicate continuous progress. Final Answer: Bar chart.

Question 5

Identify the first widely used method for project planning: historically, the Bar chart (Gantt chart) preceded milestones, CPM, and PERT.

Accepted Answer

Introduction / Context: Understanding the chronology of planning tools helps explain why different methods exist. Early tools emphasized simple visualization; later ones added logic and uncertainty analysis. This question asks which method came first historically. Given Data / Assumptions: Options span bar charts, milestones, CPM, and PERT. We assume commonly accepted historical sequencing. Concept / Approach: Bar charts (Gantt charts) emerged in the 1910s–1920s. Milestone charts formalized milestone tracking later. CPM (1950s) introduced deterministic network logic and critical path; PERT (late 1950s) added probabilistic time estimates (to, tm, tp). Therefore, bar charts preceded the rest. Step-by-Step Solution: 1) Place bar charts early (Gantt era).2) Recognize CPM/PERT were mid-20th-century innovations.3) Conclude Bar chart method is the earliest widespread planning method. Verification / Alternative check: Most project management histories trace a path: Gantt → milestones → CPM → PERT refinements for uncertainty. Why Other Options Are Wrong: Milestone chart: Came after bar charts to highlight key dates. CPM: Developed in the 1950s (DuPont/Remington Rand). PERT: Late 1950s (U.S. Navy Polaris), after CPM. Common Pitfalls: Assuming CPM/PERT predate simple charts due to their sophistication. Conflating milestone markers with the earlier bar visualization. Final Answer: Bar chart method.

Question 6

In scheduling, the difference between the time available to do a job and the time actually required for that job is called float (slack).

Accepted Answer

Introduction / Context: Float (also called slack) is central to CPM-based control because it quantifies schedule flexibility. This question checks if you can distinguish float from duration, events, and constraints. Given Data / Assumptions: Time available vs time required is given. We must name that difference appropriately. Concept / Approach: Float represents the permissible delay in an activity without affecting specific schedule targets (e.g., project finish, successor earliest starts). Unlike duration (time needed to do work), float is schedule leeway derived from early/late event times in CPM analysis. Step-by-Step Solution: 1) Identify the definition: available time minus required time.2) Map to standard terms: that difference is float/slack.3) Confirm that duration is the required time itself, not the difference.4) Conclude the correct term is float. Verification / Alternative check: CPM computations of total float and free float follow from forward/backward passes and early/late times, capturing this difference formally. Why Other Options Are Wrong: Event: A point in time; does not quantify a difference. Duration: The needed time, not extra allowance. Constraint: A rule/limit (e.g., must-start-on) rather than a time difference. Common Pitfalls: Treating float as a buffer to be consumed casually, risking loss of schedule protection. Confusing float with reserve or contingency added to duration estimates. Final Answer: Float.

Question 7

For a PERT activity with optimistic (to), most likely (tm), and pessimistic (tp) time estimates, the expected time t is computed as t = (to + 4*tm + tp) / 6.

Accepted Answer

Introduction / Context: PERT (Program Evaluation and Review Technique) models activity duration uncertainty using three-point estimates: optimistic (to), most likely (tm), and pessimistic (tp). The question asks for the expected time formula used to compute a weighted mean for scheduling and risk-aware planning. Given Data / Assumptions: Three estimates are available: to, tm, tp. We need the expected time t in PERT. Assume standard Beta-distribution-based weighting used in classical PERT. Concept / Approach: Classical PERT applies a weighted average emphasizing the most likely duration. The standard weighting is: to (weight 1), tm (weight 4), tp (weight 1). The denominator 6 normalizes the weights. This prioritizes tm while accounting for the range from best-case to worst-case. Step-by-Step Solution: 1) Recall PERT mean formula: expected t = (to + 4*tm + tp) / 6.2) Substitute if numerical values are given (not required here).3) Use t for forward pass (earliest times) and for summary statistics of activity duration. Verification / Alternative check: Check units: all terms are time; linear combination over 6 maintains dimension of time. Compare with simple average (to + tm + tp)/3, which would underweight the most likely estimate relative to PERT practice. Why Other Options Are Wrong: t = (to + tm + tp) / 3: Simple mean, not PERT's weighted mean. t = (4*to + tm + tp) / 6: Overweights optimistic time incorrectly. t = (to + 2*tm + 3*tp) / 6: Skews toward pessimistic time, not standard PERT. Common Pitfalls: Forgetting the weight 4 on tm and denominator 6. Using PERT mean without assessing variance; remember sigma^2 = ((tp - to) / 6)^2 for classical PERT. Final Answer: t = (to + 4*tm + tp) / 6.

Question 8

Critical Ratio (CR) scheduling is a dynamic priority rule that compares time remaining with work remaining, thereby setting priorities, revealing status, and adapting as progress data change.

Accepted Answer

Introduction / Context: Critical Ratio (CR) scheduling is a dispatching/priority technique used in project and production environments to decide what to work on next. It relies on a ratio that blends schedule urgency with remaining workload, and it updates as conditions change. This question checks your understanding of what CR achieves in practice. Given Data / Assumptions: CR commonly defined as: (Time remaining to due date) / (Work remaining). Lower CR indicates higher urgency (CR < 1 implies behind schedule). We assume recalculation occurs periodically as data update. Concept / Approach: Because CR is computed with current remaining time and effort, it naturally creates comparable priorities across activities, reveals whether a task is ahead or behind schedule, and changes as progress or estimates change—hence it is dynamic rather than static. Step-by-Step Solution: 1) Compute CR for each activity using current remaining time and work.2) Rank activities by CR: the smallest CR is most urgent.3) Interpret CR value to assess status: CR < 1 behind schedule; CR ≈ 1 on track; CR > 1 ahead.4) Recalculate as progress reports update → priorities adapt automatically. Verification / Alternative check: Run a simple example with two activities; recompute CR after logging progress. Observe priority changes and status signals aligning with expectations. Why Other Options Are Wrong: Options A–D individually describe correct properties, but selecting only one would be incomplete. Therefore, the inclusive statement that captures all properties is the best answer. Common Pitfalls: Treating CR as a one-time calculation instead of a rolling metric. Ignoring estimation accuracy; unreliable “work remaining” skews priorities. Final Answer: All of the above.

Question 9

A Milestone chart highlights key checkpoints and can reveal delays or ahead-of-schedule achievements, but it does not depict detailed interdependencies among jobs.

Accepted Answer

Introduction / Context: Milestone charts provide a high-level view of a project by focusing on significant events (milestones) rather than every activity. They are excellent for executive communication and quick health checks but are limited in how much logic they convey. This question probes what a milestone chart can and cannot do. Given Data / Assumptions: We consider a standard milestone chart with planned vs actual dates. We assume the chart can mark slippages or early completions. No network logic (detailed dependencies) is shown unless supplemented. Concept / Approach: By comparing planned milestone dates with actuals, a planner can quickly see if a milestone is delayed or achieved early. However, a milestone chart by itself does not illustrate detailed precedence relationships among all underlying tasks; that is the domain of CPM/PERT networks. Step-by-Step Solution: 1) Identify purpose: summarize key deliverable checkpoints.2) Compare planned vs actual marks to detect delay or earliness.3) Note that job-to-job logic is not explicit in a pure milestone chart.4) Conclude that highlighting delays is a core strength while interdependency depiction is not. Verification / Alternative check: Review any milestone dashboard: late markers are visible immediately; but you cannot infer complex sequencing without referring to a network or bar chart with links. Why Other Options Are Wrong: Shows interdependencies of various jobs: Not inherently; needs a network diagram. Points out jobs going ahead of schedule, if any: Possible, but the question format requires exactly one correct choice; highlighting delay is the classic, emphasized use. None of these: Incorrect because milestone charts do surface schedule slippages. Common Pitfalls: Expecting a milestone view to substitute for full dependency and critical path analysis. Using only milestone status without drilling into causes within the detailed schedule. Final Answer: Depicts the delay of jobs, if any.

Question 10

In network planning for civil engineering projects, identify the incorrect statement about activities, events, nodes, and networks.

Accepted Answer

Introduction / Context: This question checks foundational terminology in project scheduling (PERT/CPM): what are activities, events/nodes, and how they combine to form a network. Clarity on these definitions prevents modeling errors that lead to wrong schedules and floats. Given Data / Assumptions: Activity represents work that takes time and resources. Event (node) marks an instantaneous milestone (start or finish) with zero duration. A project network links activities and events in logical order. Only one statement is incorrect among the given options. Concept / Approach: In classic Activity-on-Arrow or Activity-on-Node conventions, activities consume time; events (nodes) do not. The critical activity is the one on the critical path with zero total float, but it is still an activity, not a node. Therefore, any statement that calls an activity a node is incorrect. Step-by-Step Solution: Check option A: It correctly defines activity as time-consuming work.Check option B: Correct—events mark start/finish points with zero duration.Check option C: Incorrect—nodes are events, not time-consuming activities; the longest activity is not called a node.Check option D: Correct—networks are built from activities and events in sequence.Conclude that C is the incorrect statement. Verification / Alternative check: Standard references define nodes as milestones and activities as duration-bearing tasks. Critical activities have zero total float but remain activities. Why Other Options Are Wrong: Option A: Correct statement; not wrong. Option B: Correct statement; not wrong. Option D: Correct statement; not wrong. Option E: Invalid because there is an incorrect statement (C). Common Pitfalls: Calling a long or critical activity a node; confusing instantaneous events with time-consuming activities; mixing AOA and AON terminology without keeping their meanings clear. Final Answer: The activity that consumes the maximum time is called a node.

Question 11

With total float = 5 days and original duration = 10 days for an activity, what schedule flexibilities are permissible without affecting the overall project?

Accepted Answer

Introduction / Context: Total float measures how long an activity's start or finish can be delayed without delaying the project completion (or the start of its successors, depending on conventions). Understanding float enables practical flexibility in start dates, finish dates, and even resource pacing. Given Data / Assumptions: Total float (TF) = 5 days. Original activity duration = 10 days. No change to network logic or successor constraints beyond what TF already allows. Concept / Approach: Total float = LST - EST = LFT - EFT. If TF = 5, the activity can slip by up to 5 days in any combination of later start, later finish, or extended duration, so long as its earliest network relationships are not violated. Step-by-Step Solution: Option A: A 5-day delay in start still fits inside the 5-day TF.Option B: A 5-day delay in finish (holding start constant) also fits inside TF.Option C: Increasing duration from 10 to 15 days (without shifting start) delays finish by 5 days, which is exactly the available TF.Hence, all statements A, B, and C are simultaneously consistent with TF = 5. Verification / Alternative check: Compute TF as difference between late and early dates. Any combination of start/finish shift or duration stretch that uses ≤ 5 days of slack is permissible. Why Other Options Are Wrong: Choosing only A, only B, or only C ignores other equally valid uses of the same float. Common Pitfalls: Confusing total float with free float; assuming float can only be used to delay start; forgetting that slower execution (longer duration) consumes float as well. Final Answer: All the above.

Question 12

In management history, Frederick W. Taylor introduced which influential organisational system for improving industrial efficiency?

Accepted Answer

Introduction / Context: Frederick W. Taylor, the father of scientific management, profoundly shaped industrial engineering and organisational design. Knowing which structure he advocated helps connect early management theory with today's project and construction practices. Given Data / Assumptions: We must identify the organisational form associated with Taylor's scientific management. Options include line, line-and-staff, functional, and a vague term (effective). Concept / Approach: Taylor proposed functional foremanship: instead of a single foreman, several specialist foremen guide workers on planning, quality, maintenance, and methods. This is the essence of functional organisation—authority and responsibility are divided by specialty to raise efficiency and standardisation. Step-by-Step Solution: Map Taylor's ideas (scientific study of work, standard methods, differential piece rate, functional foremanship) to the organisational choices.Functional organisation aligns directly with the distribution of authority to specialists.Therefore, select Functional organisation. Verification / Alternative check: Classic texts cite Taylor's functional foremanship as a central mechanic of scientific management, not pure line or line-and-staff control. Why Other Options Are Wrong: Line organisation: Single chain of command; not Taylor's distinctive proposal. Line and staff organisation: Combines command with advisory roles, more associated with later evolutions. Effective organisation: Not a standard structural type. Common Pitfalls: Confusing Taylor (functional foremanship) with later line-and-staff hybrids; assuming any efficient system equals Taylor's model. Final Answer: Functional organisation

Question 13

In PERT, if a is the optimistic time, b is the pessimistic time, and m is the most likely time of an activity, what is the expected time (te)?

Accepted Answer

Introduction / Context: PERT (Program Evaluation and Review Technique) models activity duration uncertainty using three estimates: optimistic (a), most likely (m), and pessimistic (b). The expected time te is a weighted mean that emphasizes the most likely value while still incorporating extremes. Given Data / Assumptions: Optimistic time = a Most likely time = m Pessimistic time = b Distribution is approximated by a Beta distribution on the activity's range [a, b]. Concept / Approach: PERT uses a weighting scheme that gives four times the weight to the most likely estimate, producing te = (a + 4m + b) / 6. This balances realism (m) with risk bounds (a and b). Step-by-Step Solution: Identify the PERT expected time formula.Write it using standard keyboard symbols:te = (a + 4*m + b) / 6Compare against options to find the match.Select option with (a + 4m + b) / 6. Verification / Alternative check: Variance is often computed as sigma^2 = ((b - a) / 6)^2, consistent with the same weighting logic used for te. Why Other Options Are Wrong: (a + b + m) / 3: Simple average, ignores heavier weight for m. (2a + m + 3b) / 6 and (a + 2m + b) / 4 and (4a + m + b) / 6: Incorrect weightings; they misrepresent the Beta-based heuristic. Common Pitfalls: Using an unweighted mean; swapping weights between a and b; forgetting the denominator 6 tied to 1 + 4 + 1 weighting. Final Answer: te = (a + 4m + b) / 6

Question 14

The technique specifically used to establish and maintain priority among competing jobs or work orders in a project or job shop is known as:

Accepted Answer

Introduction / Context: When multiple jobs compete for limited resources (crews, machines), managers need a rule to decide which job to process first. Priority-assignment rules are central to production control and construction logistics. Given Data / Assumptions: Goal: Choose the technique that sets priorities among jobs. Context: Project or job-shop environment with resource contention. Concept / Approach: Critical Ratio (CR) = Time remaining until due date / Processing time remaining.The job with the lowest CR is given the highest priority. CR dynamically reflects both urgency (due date pressure) and effort remaining, making it a well-known method for maintaining priorities. Step-by-Step Solution: Identify which option names a recognised priority rule.Critical ratio scheduling explicitly provides a numeric priority index.Therefore select Critical ratio scheduling. Verification / Alternative check: Shop-floor control texts list CR alongside SPT (shortest processing time), EDD (earliest due date), and LPT; among given options, CR uniquely states a priority rule by name. Why Other Options Are Wrong: Event-flow scheduling technique: Vague; not a standard priority rule. Slotting technique for scheduling: Generic term; lacks a defined priority index. Short-interval scheduling: A look-ahead planning approach, not a priority formula. Common Pitfalls: Confusing look-ahead/visibility tools with true priority rules; selecting generic terms that do not specify how jobs are ranked. Final Answer: Critical ratio scheduling

Question 15

Select the correct comprehensive statement about CPM and PERT: orientation, uncertainty treatment, and time–cost linkage.

Accepted Answer

Introduction / Context: CPM and PERT are canonical network techniques in project management. Knowing their orientation and assumptions guides method selection, interpretation of floats, and risk handling. Given Data / Assumptions: We must judge multiple statements about CPM and PERT. Only one option provides the best overall characterisation. Concept / Approach: CPM (Critical Path Method) is activity-oriented and assumes deterministic durations; it also supports time–cost optimisation (crashing). PERT (Program Evaluation and Review Technique) is event-oriented and models duration uncertainty using a, m, b with expected times. Step-by-Step Solution: Evaluate A: True—CPM focuses on activities.Evaluate B: True—PERT historically emphasises events and probabilistic times.Evaluate C: True—CPM uses single (deterministic) durations.Evaluate D: True—CPM includes time–cost trade-off analyses (crashing).Therefore E (All the above) is correct. Verification / Alternative check: Textbook comparisons of CPM vs PERT consistently list these differences and capabilities. Why Other Options Are Wrong: Picking A, B, C, or D alone omits other equally correct facets. Common Pitfalls: Assuming PERT and CPM are interchangeable; forgetting time–cost trade-off is more closely tied to CPM. Final Answer: All the above.

Question 16

If TL denotes the latest allowable occurrence time of the head event, the total activity slack (total float) is equal to which of the following expressions?

Accepted Answer

Introduction / Context: Total float quantifies the maximum delay allowable for an activity without jeopardizing the project schedule. Multiple equivalent expressions exist depending on whether we look at starts, finishes, or event times. Given Data / Assumptions: EST/EFT: earliest start/finish times of the activity. LST/LFT: latest start/finish times consistent with project deadlines. TL: latest allowable time of the head (finish) event connected to the activity. Concept / Approach: Total float TF can be written in equivalent ways: TF = LST - EST = LFT - EFT. In Activity-on-Arrow, with TL as latest time of the head event, TF can also be expressed as TF = TL - EFT, since the head event's latest time bounds the latest feasible finish of the activity. Step-by-Step Solution: Start definition: TF = LST - EST.Using durations, TF equivalently equals LFT - EFT.With event times, TF equals TL - EFT for the head event, maintaining consistency.Therefore, all listed expressions are valid and equal. Verification / Alternative check: Compute with a small example network and confirm the equality numerically; each form yields identical TF values. Why Other Options Are Wrong: Any single expression alone is not wrong, but choosing only one ignores the other equivalent forms. Common Pitfalls: Mixing up free float and total float; misapplying TL (event time) as if it were LFT without linking to the head event. Final Answer: All the above.

Question 17

According to standard public-works classification, works costing less than Rs. 20,000 are generally treated as which category?

Accepted Answer

Introduction / Context: Cost thresholds are used in public works to categorise jobs for administrative control, sanctioning powers, and procedure. This classification guides tendering, supervision, and reporting levels. Given Data / Assumptions: Monetary threshold: less than Rs. 20,000. We must select the appropriate category used in typical practice questions. Concept / Approach: Small-value works are commonly grouped as minor projects/works, attracting simpler procedures and lower sanctioning levels compared to major projects. While exact thresholds can vary by department and time, exam standards usually map sub-Rs. 20,000 works to the minor category. Step-by-Step Solution: Identify conventional categories: major vs minor.Map the small cost value to the minor class.Select Minor projects. Verification / Alternative check: Older CPWD/state PWD manuals and standard exam prep sources treat small-ticket works as minor; confirm with the latest departmental schedule when applying in practice. Why Other Options Are Wrong: Projects: Too generic; does not reflect scale. Major projects: Reserved for high-value, complex works. All the above.: Mutually inconsistent categories; cannot all be correct. Common Pitfalls: Assuming uniform thresholds across departments or years; ignoring that exam questions use conventional legacy thresholds for pedagogy. Final Answer: Minor projects

Question 18

On a bar (Gantt) chart for scheduling, individual activities of a project are conventionally represented by which graphical element?

Accepted Answer

Introduction / Context: Bar charts are among the simplest and most widely used scheduling tools in construction. Recognising how activities are drawn helps in reading and producing clear schedules for stakeholders. Given Data / Assumptions: We are interpreting the visual convention of a Gantt/Bar chart. Each activity has a duration along a time axis. Concept / Approach: On a bar chart, time is on the horizontal axis, and activities are listed vertically. The span of an activity over time is shown as a horizontal bar, whose left end indicates start and right end indicates finish. Step-by-Step Solution: Recall the layout: activity list on the left, timeline on top.Match the representation: activity duration = horizontal bar segment.Select Horizontal lines. Verification / Alternative check: Any standard bar chart image shows activities as horizontal bars aligned against the timeline scale. Why Other Options Are Wrong: Vertical lines: Could indicate milestones or dates, not activity duration bars. Dots / Crosses: Used for scatter/milestone markers, not continuous activity spans. Common Pitfalls: Confusing milestone markers with duration bars; misreading the axes and believing vertical lines denote work. Final Answer: Horizontal lines

Question 19

In network analysis, the time by which an activity's completion can be delayed without affecting the earliest start of its immediate successor(s) is called:

Accepted Answer

Introduction / Context: Different float types quantify different flexibilities. Free float focuses on the leeway available to an activity without encroaching on the early schedule of its immediate successor(s). Given Data / Assumptions: We seek the term for delay that does not impact successor earliest starts. Terminology must distinguish total float from free and interfering float. Concept / Approach: Free float (FF) = Min(EST of successors) - EFT of the activity.Free float measures how much the activity’s finish can slip without changing any successor’s earliest start. Total float is broader: TF = LFT - EFT = LST - EST. Interfering float is the portion of total float that, if used, would delay successors’ earliest starts. Step-by-Step Solution: Identify the definition that matches “no effect on successor earliest start”.Relate to formula: FF depends on successor EST and current activity EFT.Select Free float. Verification / Alternative check: Compute a small example network to confirm that a delay equal to FF keeps successor EST unchanged, while using more than FF encroaches on successor timing. Why Other Options Are Wrong: Duration: Not a float type; the base length of the activity. Total float: Includes portions that might affect successors if used. Interfering float: By definition, it interferes with successor earliest starts. Common Pitfalls: Using TF when FF is intended; assuming all slack is harmless to successors; ignoring the distinction between local (free) and global (total) slack. Final Answer: Free float

Question 20

In public works and civil engineering departments, the final technical authority for a project—covering drawings, specifications, and design approvals—vests with the Chief Engineer.

Accepted Answer

Introduction / Context: The question tests understanding of hierarchical technical authority in typical government engineering set-ups (Public Works Department, irrigation, public health, military engineering). Knowing who gives the final technical clearance ensures clarity on accountability for design integrity, safety, and compliance. Given Data / Assumptions: A standard multi-tier engineering hierarchy exists: Assistant Engineer, Executive Engineer, Superintending Engineer, Chief Engineer. Technical authority refers to approval of designs, drawings, estimates, and specifications. Procurement or financial sanction may have separate delegated powers; here we focus on technical authority. Concept / Approach: In most public works manuals, 'final technical sanction' for significant projects lies with the highest technical post. Lower tiers prepare, scrutinize, and recommend; higher tiers review for code compliance, safety margins, and standard specifications. The Chief Engineer is responsible for department-wide technical standards and, therefore, is the final technical authority for major projects within delegated limits or as per government rules. Step-by-Step Solution: 1) Identify what 'final technical authority' means: ultimate sign-off on technical adequacy.2) Map responsibilities by cadre: A.E. prepares, E.E. consolidates and manages division, S.E. oversees circles and ensures quality control.3) The Chief Engineer frames standards/specifications and accords final technical sanction for major works.4) Conclude: Chief Engineer holds the final technical authority. Verification / Alternative check: Departmental codes (PWD/Irrigation manuals) and delegation of powers tables consistently show higher thresholds and final sanctions resting with the Chief Engineer, subject to budgetary ceilings and government authorization. Why Other Options Are Wrong: Assistant Engineer: Executes site-level supervision and prepares estimates; not final authority. Executive Engineer: Division head; can accord sanction up to lower limits, not final for major works. Superintending Engineer: Circle-level control and scrutiny; still not the apex technical authority. Common Pitfalls: Confusing financial sanction with technical sanction. Assuming divisional approval equals department-level final authority. Final Answer: Chief Engineer.

Construction Management Questions