Binary Search on Answer Technique in DSA C++ - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize the search range for binary search on answer.

DSA C++

int low = 0;
int high = [1];

Drag options to blanks, or click blank then click option'

A100

B1000

C10

D1e9

Attempts:

3 left

💡 Hint

Common Mistakes

Setting high too low and missing the correct answer.

Using a small fixed number like 10 or 100 without reasoning.

The high value is set to a large number (1e9) to cover the maximum possible answer range.

2fill in blank

medium

Complete the code to calculate the middle value in binary search on answer.

DSA C++

int mid = low + ([1] - low) / 2;

Drag options to blanks, or click blank then click option'

Ahigh

Blow

Cmid

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using (low + high) / 2 directly which can overflow.

Using low instead of high in the calculation.

We calculate mid as low + (high - low) / 2 to avoid overflow.

3fill in blank

hard

Fix the error in the condition to update the search range based on feasibility check.

DSA C++

if (isPossible([1])) {
    high = mid - 1;
} else {
    low = mid + 1;
}

Drag options to blanks, or click blank then click option'

Amid

Blow

Chigh

Dmid + 1

Attempts:

3 left

💡 Hint

Common Mistakes

Passing low or high instead of mid to isPossible.

Using mid + 1 which is not the current candidate.

The feasibility check should be done on mid, the current candidate answer.

4fill in blank

hard

Fill both blanks to complete the binary search loop condition and update low when answer is not possible.

DSA C++

while ([1] <= [2]) {
    int mid = low + (high - low) / 2;
    if (isPossible(mid)) {
        high = mid - 1;
    } else {
        low = mid + 1;
    }
}

Drag options to blanks, or click blank then click option'

Alow

Bhigh

Cmid

Dlow + 1

Attempts:

3 left

💡 Hint

Common Mistakes

Using mid in the while condition.

Using low + 1 in the while condition instead of high.

The loop continues while low is less than or equal to high.

We update low to mid + 1 when the answer is not possible.

5fill in blank

hard

Fill all three blanks to return the final answer after binary search on answer completes.

DSA C++

int binarySearchAnswer() {
    int low = 0, high = 1e9;
    int result = -1;
    while (low <= high) {
        int mid = low + (high - low) / 2;
        if (isPossible(mid)) {
            result = [1];
            high = [2];
        } else {
            low = [3];
        }
    }
    return result;
}

Drag options to blanks, or click blank then click option'

Amid

Bmid - 1

Cmid + 1

Dhigh

Attempts:

3 left

💡 Hint

Common Mistakes

Not updating result when mid is possible.

Incorrectly updating high or low boundaries.

When mid is possible, we store it in result and move high to mid - 1 to find a smaller possible answer.

Otherwise, we move low to mid + 1 to search higher.

Practice

1. What is the main idea behind the Binary Search on Answer technique?

easy

A. Searching for the answer by repeatedly dividing the search space based on feasibility

B. Sorting the array before applying binary search

C. Using binary search to find an element in a sorted array

D. Applying binary search only on arrays with unique elements

Solution

1. Step 1: Understand the problem context

   Binary Search on Answer is used when the answer lies within a range and we can check feasibility for a candidate answer.

2. Step 2: Apply binary search on the answer range

   We repeatedly pick a middle value and check if it satisfies the problem's conditions, narrowing the search space accordingly.

3. Final Answer:

   Searching for the answer by repeatedly dividing the search space based on feasibility -> Option A

4. Quick Check:

   Binary Search on Answer = feasibility check [OK]

Hint: Think of binary search on answer as guessing and checking [OK]

Common Mistakes:

• Confusing it with normal binary search on arrays
• Not checking feasibility properly
• Trying to apply it on unsorted data without a valid range

2. Which of the following is the correct syntax to start a binary search on answer for an integer range low to high in C++?

easy

A. while (low <= high) { int mid = (low + high) / 2; }

B. for (int mid = low; mid <= high; mid++) { }

C. while (low < high) { int mid = low + (high - low) / 2; }

D. if (low < high) { mid = (low + high) / 2; }

Solution

1. Step 1: Identify the correct loop condition

   Binary search typically uses a loop with condition low < high to avoid infinite loops and handle edge cases.

2. Step 2: Calculate mid safely

   Using mid = low + (high - low) / 2 prevents integer overflow compared to (low + high) / 2.

3. Final Answer:

   while (low < high) { int mid = low + (high - low) / 2; } -> Option C

4. Quick Check:

   Safe mid calculation with proper loop [OK]

Hint: Use low + (high - low)/2 to avoid overflow [OK]

Common Mistakes:

• Using <= in loop causing infinite loops
• Calculating mid as (low + high)/2 risking overflow
• Using for loop instead of while for binary search

3. Consider the following code snippet that uses binary search on answer to find the minimum maximum load for dividing an array into k subarrays:

bool canDivide(const vector<int>& arr, int k, int maxLoad) {
    int currentSum = 0, count = 1;
    for (int num : arr) {
        if (num > maxLoad) return false;
        if (currentSum + num > maxLoad) {
            count++;
            currentSum = num;
        } else {
            currentSum += num;
        }
    }
    return count <= k;
}

int binarySearchAnswer(const vector<int>& arr, int k) {
    int low = 0, high = 0;
    for (int num : arr) high += num;
    while (low < high) {
        int mid = low + (high - low) / 2;
        if (canDivide(arr, k, mid)) high = mid;
        else low = mid + 1;
    }
    return low;
}

int main() {
    vector<int> arr = {7, 2, 5, 10, 8};
    int k = 2;
    cout << binarySearchAnswer(arr, k) << endl;
}

What is the output of this program?

medium

A. 15

B. 18

C. 20

D. 22

Solution

1. Step 1: Understand the problem and code

   The code finds the minimum maximum sum when dividing the array into 2 subarrays. The total sum is 7+2+5+10+8=32.

2. Step 2: Trace binary search on answer

   Check mid values and feasibility:
   - mid=16: canDivide returns true (possible, e.g., subarrays sums 14 and 18)
   - mid=15: canDivide returns true (possible, e.g., subarrays sums 14 and 15)
   - mid=14: canDivide returns false (cannot split into 2 with max sum 14)
   Binary search narrows down to 15 as minimum max load.

3. Final Answer:

   15 -> Option A

4. Quick Check:

   Minimum max load = 15 [OK]

Hint: Sum array, binary search between 0 and sum [OK]

Common Mistakes:

• Not checking if single element > mid
• Incorrectly updating low and high
• Misunderstanding feasibility function

4. The following code attempts to find the smallest maximum weight capacity to ship packages within D days using binary search on answer. Identify the bug:

bool canShip(const vector<int>& weights, int D, int capacity) {
    int days = 1, currentLoad = 0;
    for (int w : weights) {
        if (w > capacity) return false;
        if (currentLoad + w > capacity) {
            days++;
            currentLoad = w;
        } else {
            currentLoad += w;
        }
    }
    return days <= D;
}

int shipWithinDays(const vector<int>& weights, int D) {
    int low = 0, high = accumulate(weights.begin(), weights.end(), 0);
    while (low <= high) {
        int mid = low + (high - low) / 2;
        if (canShip(weights, D, mid)) high = mid - 1;
        else low = mid + 1;
    }
    return low;
}

medium

A. The loop condition should be low < high instead of low <= high

B. The mid calculation can cause integer overflow

C. The canShip function does not handle empty weights array

D. The initial value of low should be the maximum weight in the array, not 0

Solution

1. Step 1: Analyze initial search range

   Low should start at the maximum single package weight because capacity cannot be less than the heaviest package.

2. Step 2: Identify impact of wrong low value

   Starting low at 0 causes unnecessary checks and may cause incorrect results or longer runtime.

3. Final Answer:

   The initial value of low should be the maximum weight in the array, not 0 -> Option D

4. Quick Check:

   Low = max(weights) [OK]

Hint: Low must be max element, high sum of all [OK]

Common Mistakes:

• Starting low at 0 instead of max element
• Using <= in loop causing off-by-one errors
• Ignoring edge cases with large weights

5. You want to find the minimum time required to complete n tasks using m machines, where each machine can complete one task in a fixed time given by array times. You can assign multiple tasks to a machine but tasks are done sequentially. Using binary search on answer, which approach correctly finds the minimum time to finish all tasks?

Choose the correct approach:

hard

A. Binary search on number of machines from 1 to m, checking if tasks can be done in fixed time

B. Binary search on time range from 0 to max(times) * n, and check if total tasks done by all machines in mid time is at least n

C. Sort times and pick the machine with minimum time multiplied by n

D. Use binary search on tasks from 1 to n, checking if tasks fit in given time

Solution

1. Step 1: Define search space for binary search

   The minimum time is 0 and maximum time is max machine time * n tasks (worst case all tasks on slowest machine).

2. Step 2: Check feasibility at mid time

   Calculate total tasks all machines can complete in mid time by summing floor(mid / times[i]). If total tasks >= n, mid time is feasible.

3. Step 3: Narrow search space

   If feasible, try smaller time by setting high = mid; else low = mid + 1.

4. Final Answer:

   Binary search on time range from 0 to max(times) * n, and check if total tasks done by all machines in mid time is at least n -> Option B

5. Quick Check:

   Binary search on time with feasibility check [OK]

Hint: Search time range, count tasks done at mid [OK]

Common Mistakes:

• Binary searching on machines instead of time
• Not summing tasks correctly for feasibility
• Ignoring sequential task processing per machine