Practice Mode • Cloud & DevOps • easy

Pod Placement Decision

100 points

Choose a node that satisfies CPU, memory, and label constraints.

Problem

You are implementing choose a node that satisfies CPU, memory, and label constraints. The input is one JSON value. Return exactly the JSON or scalar result described by the examples, with stable ordering and no extra logging. Choose the lexicographically stable schedulable node or return pending. Explain your reasoning and complexity during interview review; the judge evaluates only the returned result.

Input contract

One UTF-8 JSON value matching the structures shown in the examples.

Output contract

One deterministic JSON value or scalar with no explanatory text.

Target complexity

O(n log n) time, O(n) space

Judge protocol

function-stdin-json-v1

Examples

Example 1

Input: {"nodes":[{"availableCpu":3,"availableMemory":4,"labels":{"zone":"x"},"name":"a"},{"availableCpu":4,"availableMemory":8,"labels":{"zone":"y"},"name":"b"}],"requestCpu":2,"requestMemory":4,"requiredLabels":{}}
Output: a

This example demonstrates the core cloud devops invariant.

Example 2

Input: {"nodes":[],"requestCpu":1,"requestMemory":1,"requiredLabels":{}}
Output: pending

This example covers the empty or minimum boundary.

Constraints

Input is valid UTF-8 JSON and is at most 64 KB.
Output must be deterministic for identical input.
Do not use network access, persistent filesystem writes, subprocesses, or environment secrets.
Handle the empty or minimum boundary shown in the examples.

Progressive hints

Integrity: hidden tests, editorial solutions, and assessment-only cases are never sent to the browser as answer keys. Final execution occurs only in the separately isolated runner.

Execution unavailable until runner deployment and certificationdisabled • pending

Sign in to code

You can review the complete problem publicly. Sign in to save encrypted drafts and submit to the isolated runner.