Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 2.81 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Single-quoted strings allow variable interpolation, while double-quoted strings treat contents literally.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Single-quoted strings allow variable interpolation, while double-quoted strings treat contents literally." ⏎ } ⏎ ``` | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 0.1 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «no» Пояснение: The ?? operator uses null coalescing and does not check for existence like isset.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The ?? operator uses null coalescing and does not check for existence like isset." ⏎ } ⏎ ``` | неверно верный: «yes» | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.07 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The echo function concatenates the string literals.
Raw```json ⏎ { ⏎ "answer": "ab", ⏎ "explanation": "The echo function concatenates the string literals." ⏎ } ⏎ ``` | верно | echo принимает список аргументов: ab. |
T01-L4 0.11 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: The print function in PHP is used for output and returns nothing (void).
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The print function in PHP is used for output and returns nothing (void)." ⏎ } ⏎ ``` | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 0.12 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «yes» Пояснение: The null coalescing operator (??) returns the right operand if the left operand is null or undefined, but the ternary operator (?:) returns the first operand if it is falsy.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The null coalescing operator (??) returns the right operand if the left operand is null or undefined, but the ternary operator (?:) returns the first operand if it is falsy." ⏎ } ⏎ ``` | неверно верный: «no» | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 0.08 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «no» Пояснение: The concatenation operator (.) has higher precedence than addition and subtraction in PHP.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The concatenation operator (.) has higher precedence than addition and subtraction in PHP." ⏎ } ⏎ ``` | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.14 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: In PHP, the exponentiation operator (**) is right-associative, so it is evaluated as 2 ** (3 ** 2), which is 2 ** 9, or 512.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "In PHP, the exponentiation operator (**) is right-associative, so it is evaluated as 2 ** (3 ** 2), which is 2 ** 9, or 512." ⏎ } ⏎ ``` | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 0.12 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: The string concatenation operator (.) will coerce the integer 2 to a string, resulting in 'sum: 23'.
Raw```json ⏎ { ⏎ "answer": "sum: 5", ⏎ "explanation": "The string concatenation operator (.) will coerce the integer 2 to a string, resulting in 'sum: 23'." ⏎ } ⏎ ``` | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 0.09 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: Strict comparison for arrays checks both value and order of elements.
Raw```json ⏎ { ⏎ "answer": false, ⏎ "explanation": "Strict comparison for arrays checks both value and order of elements." ⏎ } ⏎ ``` | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 0.12 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «yes» Пояснение: In strict comparison (===), the type of 0 (integer) does not match the type of false (boolean).
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "In strict comparison (===), the type of 0 (integer) does not match the type of false (boolean)." ⏎ } ⏎ ``` | неверно верный: «no» | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 0.1 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP, comparing a non-empty string to an integer using == does not return true.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "In PHP, comparing a non-empty string to an integer using == does not return true." ⏎ } ⏎ ``` | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.1 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In loose comparison (==), PHP treats null, the empty string, and false as equal to 0.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "In loose comparison (==), PHP treats null, the empty string, and false as equal to 0." ⏎ } ⏎ ``` | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.09 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: Type casting to (int) truncates the string to its leading integer part.
Raw```json ⏎ { ⏎ "answer": "42", ⏎ "explanation": "Type casting to (int) truncates the string to its leading integer part." ⏎ } ⏎ ``` | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.16 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, when one operand is a string, the other operand is coerced into a string for concatenation, but in this case, PHP often performs type juggling leading to addition if both are numeric.
Raw```json ⏎ { ⏎ "answer": "10", ⏎ "explanation": "In PHP, when one operand is a string, the other operand is coerced into a string for concatenation, but in this case, PHP often performs type juggling leading to addition if both are numeric." ⏎ } ⏎ ``` | верно | Числовая строка приводится: int 10. |
T02-L7 0.09 c | Types and comparisons | When cast to string, false becomes "0". | «yes» Пояснение: In PHP, casting boolean false to a string results in the string '0'.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "In PHP, casting boolean false to a string results in the string '0'." ⏎ } ⏎ ``` | неверно верный: «no» | false → "", true → "1". |
T02-L8 0.1 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point imprecision in binary representation, 0.1 + 0.2 is not exactly 0.3.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Due to floating-point imprecision in binary representation, 0.1 + 0.2 is not exactly 0.3." ⏎ } ⏎ ``` | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 0.09 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() operates on single-byte characters and does not correctly handle multi-byte UTF-8 characters.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "strrev() operates on single-byte characters and does not correctly handle multi-byte UTF-8 characters." ⏎ } ⏎ ``` | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.07 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains checks if a string contains a specified substring.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "str_contains checks if a string contains a specified substring." ⏎ } ⏎ ``` | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.07 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad a string on both the left and right sides.
Raw```json ⏎ { ⏎ "answer": false, ⏎ "explanation": "str_pad() can pad a string on both the left and right sides." ⏎ } ⏎ ``` | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 0.09 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips whitespace characters, including spaces, tabs, and newlines.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "By default, trim() strips whitespace characters, including spaces, tabs, and newlines." ⏎ } ⏎ ``` | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 0.11 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen counts the number of bytes, and 'héllo' in UTF-8 is 6 bytes (h, é, l, l, o).
Raw```json ⏎ { ⏎ "answer": 6, ⏎ "explanation": "strlen counts the number of bytes, and 'héllo' in UTF-8 is 6 bytes (h, é, l, l, o)." ⏎ } ⏎ ``` | верно | 6 букв по 2 байта: 12. |
T03-L6 0.1 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: When a negative offset is provided to substr, it counts from the end of the string.
Raw```json ⏎ { ⏎ "answer": "def", ⏎ "explanation": "When a negative offset is provided to substr, it counts from the end of the string." ⏎ } ⏎ ``` | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.09 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character capitalized; it does not modify the original string in place.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "ucfirst() returns a new string with the first character capitalized; it does not modify the original string in place." ⏎ } ⏎ ``` | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.08 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Variable interpolation is supported in heredoc syntax but not in nowdoc syntax.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Variable interpolation is supported in heredoc syntax but not in nowdoc syntax." ⏎ } ⏎ ``` | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.11 c | Arrays | The sort() function preserves the key-to-value association of the array. | «yes» Пояснение: The sort() function, when used with an array, sorts the elements while maintaining their original keys.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The sort() function, when used with an array, sorts the elements while maintaining their original keys." ⏎ } ⏎ ``` | неверно верный: «no» | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.07 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, string keys that look like integers are converted to integers.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "In PHP, string keys that look like integers are converted to integers." ⏎ } ⏎ ``` | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.09 c | Arrays | The in_array() function uses strict comparison (===) by default. | «yes» Пояснение: The in_array function uses strict comparison by default to ensure correct type and value matching.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The in_array function uses strict comparison by default to ensure correct type and value matching." ⏎ } ⏎ ``` | неверно верный: «no» | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.09 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «no» Пояснение: array_filter() requires a callback function to determine which elements to keep.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "array_filter() requires a callback function to determine which elements to keep." ⏎ } ⏎ ``` | неверно верный: «yes» | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.11 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: array_slice() preserves keys only if no offset is specified, but if an offset is given, it returns a new array with re-indexed numeric keys.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "array_slice() preserves keys only if no offset is specified, but if an offset is given, it returns a new array with re-indexed numeric keys." ⏎ } ⏎ ``` | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 0.12 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «json» Пояснение: ```json
{
"answer": [
20,
30
],
"explanation": "array_slice extracts a portion of an array starting at a specified offset with a given length."
}
```
Raw```json ⏎ { ⏎ "answer": [ ⏎ 20, ⏎ 30 ⏎ ], ⏎ "explanation": "array_slice extracts a portion of an array starting at a specified offset with a given length." ⏎ } ⏎ ``` | неверно верный: «[20,30]» парсинг: текст (фолбэк) | [20,30]; ключи перенумеровываются. |
T04-L7 0.1 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The '+' operator for arrays merges the arrays, and the resulting array has two elements.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "The '+' operator for arrays merges the arrays, and the resulting array has two elements." ⏎ } ⏎ ``` | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 0.15 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «no» Пояснение: The spread operator in PHP supports spreading arrays with string keys, but it does not specifically support array arguments in the syntax [...$a, ...$b] in the way array spreading is typically discussed for simple arrays.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The spread operator in PHP supports spreading arrays with string keys, but it does not specifically support array arguments in the syntax [...$a, ...$b] in the way array spreading is typically discussed for simple arrays." ⏎ } ⏎ ``` | неверно верный: «yes» | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 0.1 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: Named arguments can generally be combined with argument unpacking depending on the language version and context, although there are specific restrictions.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Named arguments can generally be combined with argument unpacking depending on the language version and context, although there are specific restrictions." ⏎ } ⏎ ``` | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.08 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «yes» Пояснение: Anonymous functions in PHP can access variables from the enclosing scope by default.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Anonymous functions in PHP can access variables from the enclosing scope by default." ⏎ } ⏎ ``` | неверно верный: «no» | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.07 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments passed to the function.
Raw```json ⏎ { ⏎ "answer": "3", ⏎ "explanation": "func_num_args() returns the number of arguments passed to the function." ⏎ } ⏎ ``` | верно | Считает переданные аргументы: 3. |
T05-L4 0.09 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «yes» Пояснение: Arrow function bodies can contain multiple expressions, including a block enclosed in curly braces.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Arrow function bodies can contain multiple expressions, including a block enclosed in curly braces." ⏎ } ⏎ ``` | неверно верный: «no» | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 0.08 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: Arrow functions do not capture outer variables by reference; they capture them by value.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Arrow functions do not capture outer variables by reference; they capture them by value." ⏎ } ⏎ ``` | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.13 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: Static methods in PHP do not bind to an object instance, thus they cannot capture the instance's scope like a regular method.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Static methods in PHP do not bind to an object instance, thus they cannot capture the instance's scope like a regular method." ⏎ } ⏎ ``` | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 0.12 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «7» Пояснение: The closure captures the variable $x from its outer scope, and the final assignment to $x modifies the variable accessible by the closure.
Raw```json ⏎ { ⏎ "answer": "7", ⏎ "explanation": "The closure captures the variable $x from its outer scope, and the final assignment to $x modifies the variable accessible by the closure." ⏎ } ⏎ ``` | неверно верный: «5» | use захватывает по значению в момент создания: 5. |
T05-L8 0.1 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode, PHP performs type juggling, allowing a string like "5" to be implicitly converted to an integer.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In weak typing mode, PHP performs type juggling, allowing a string like \"5\" to be implicitly converted to an integer." ⏎ } ⏎ ``` | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.08 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.0 introduced constructor property promotion, allowing properties to be declared directly in the constructor.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.0 introduced constructor property promotion, allowing properties to be declared directly in the constructor." ⏎ } ⏎ ``` | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.07 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The 'final' keyword prevents a method from being overridden in subclasses.
Raw```json ⏎ { ⏎ "answer": "final", ⏎ "explanation": "The 'final' keyword prevents a method from being overridden in subclasses." ⏎ } ⏎ ``` | верно | final. |
T06-L3 0.07 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: A final method cannot be overridden by a subclass.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "A final method cannot be overridden by a subclass." ⏎ } ⏎ ``` | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.09 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are not accessible outside the class they are declared in, including subclasses.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Private properties are not accessible outside the class they are declared in, including subclasses." ⏎ } ⏎ ``` | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 0.08 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «class» Пояснение: get_class() returns the fully qualified class name of the object.
Raw```json ⏎ { ⏎ "answer": "class", ⏎ "explanation": "get_class() returns the fully qualified class name of the object." ⏎ } ⏎ ``` | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 0.11 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «no» Пояснение: A private method is not accessible outside the class, and a child class cannot override or access it.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "A private method is not accessible outside the class, and a child class cannot override or access it." ⏎ } ⏎ ``` | неверно верный: «yes» | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 0.08 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: ",
"explanation": "__get()" is called when an object tries to access a non-existent property."
}
```
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "__get()" is called when an object tries to access a non-existent property." ⏎ } ⏎ ``` | верно парсинг: текст (фолбэк) | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 0.08 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property typically throws an Error in PHP.
Raw```json ⏎ { ⏎ "answer": "Error", ⏎ "explanation": "Reassigning a readonly property typically throws an Error in PHP." ⏎ } ⏎ ``` | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.09 c | Interfaces, traits, enum | An interface can declare constants. | «no» Пояснение: Interfaces in PHP cannot declare constants directly; they define contracts for classes to implement.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Interfaces in PHP cannot declare constants directly; they define contracts for classes to implement." ⏎ } ⏎ ``` | неверно верный: «yes» | Константы интерфейса наследуются реализациями. |
T07-L2 0.09 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «false» Пояснение: The instance of a class or interface is checked using the 'instanceof' operator.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The instance of a class or interface is checked using the 'instanceof' operator." ⏎ } ⏎ ``` | неверно верный: «instanceof» | instanceof. |
T07-L3 0.07 c | Interfaces, traits, enum | An interface can declare static methods. | «no» Пояснение: Interfaces can only declare method signatures, not static methods.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Interfaces can only declare method signatures, not static methods." ⏎ } ⏎ ``` | неверно верный: «yes» | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.1 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator checks if an object is an instance of a class or a subclass thereof, including implementing an interface.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The instanceof operator checks if an object is an instance of a class or a subclass thereof, including implementing an interface." ⏎ } ⏎ ``` | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 0.08 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: Interface methods cannot have default implementations; traits can provide default implementations for methods.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Interface methods cannot have default implementations; traits can provide default implementations for methods." ⏎ } ⏎ ``` | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.14 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «no» Пояснение: Abstract methods must be declared as abstract, and their visibility is typically limited to protected or public, but the core concept relates to abstract methods not being implemented.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Abstract methods must be declared as abstract, and their visibility is typically limited to protected or public, but the core concept relates to abstract methods not being implemented." ⏎ } ⏎ ``` | неверно верный: «yes» | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.07 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: The cases defined in the enum will return three elements.
Raw```json ⏎ { ⏎ "answer": 3, ⏎ "explanation": "The cases defined in the enum will return three elements." ⏎ } ⏎ ``` | верно | Статический метод cases(): 3. |
T07-L8 0.1 c | Interfaces, traits, enum | A trait can declare constants. | «no» Пояснение: Traits cannot declare constants directly; constants must be defined within a class or a static property.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Traits cannot declare constants directly; constants must be defined within a class or a static property." ⏎ } ⏎ ``` | неверно верный: «yes» | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.07 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «no» Пояснение: Throwable is the common ancestor of both Exception and Error classes.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Throwable is the common ancestor of both Exception and Error classes." ⏎ } ⏎ ``` | неверно верный: «yes» | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 0.09 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError does not inherit directly from Exception in PHP; it is a distinct type.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "TypeError does not inherit directly from Exception in PHP; it is a distinct type." ⏎ } ⏎ ``` | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.07 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator suppresses errors but does not suppress exceptions.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The @ operator suppresses errors but does not suppress exceptions." ⏎ } ⏎ ``` | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.08 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: Dividing by zero in PHP throws a DivisionByZeroError.
Raw```json ⏎ { ⏎ "answer": "DivisionByZeroError", ⏎ "explanation": "Dividing by zero in PHP throws a DivisionByZeroError." ⏎ } ⏎ ``` | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 0.08 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block always executes, regardless of whether an exception was caught.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The finally block always executes, regardless of whether an exception was caught." ⏎ } ⏎ ``` | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 0.09 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block can still affect the result, depending on how the finally block is structured.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "An exception thrown in a finally block can still affect the result, depending on how the finally block is structured." ⏎ } ⏎ ``` | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.08 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «exception» Пояснение: The expression returns a new instance of the Exception class.
Raw```json ⏎ { ⏎ "answer": "Exception", ⏎ "explanation": "The expression returns a new instance of the Exception class." ⏎ } ⏎ ``` | неверно верный: «true» | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 0.09 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: register_shutdown_function() registers a function to be called when the script is shutting down.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "register_shutdown_function() registers a function to be called when the script is shutting down." ⏎ } ⏎ ``` | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 0.09 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «yes» Пояснение: Including a class statement in PHP requires the class file to be loaded.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Including a class statement in PHP requires the class file to be loaded." ⏎ } ⏎ ``` | неверно верный: «no» | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.07 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: The `function` keyword is used to define a function in PHP.
Raw```json ⏎ { ⏎ "answer": "function", ⏎ "explanation": "The `function` keyword is used to define a function in PHP." ⏎ } ⏎ ``` | верно | use function ...; (и use const для констант). |
T09-L3 0.1 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «src/controller/api/usercontroller.php» Пояснение: PSR-4 mapping maps the namespace prefix to a directory structure.
Raw```json ⏎ { ⏎ "answer": "src/Controller/Api/UserController.php", ⏎ "explanation": "PSR-4 mapping maps the namespace prefix to a directory structure." ⏎ } ⏎ ``` | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.08 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: vendor/autoload.php typically registers autoloaders to handle class loading.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "vendor/autoload.php typically registers autoloaders to handle class loading." ⏎ } ⏎ ``` | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.08 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: The \_\_NAMESPACE\_\_ magic constant holds the name of the current namespace.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The \_\_NAMESPACE\_\_ magic constant holds the name of the current namespace." ⏎ } ⏎ ``` | верно | В корневом пространстве — пустая строка. |
T09-L6 0.1 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name is typically resolved from the current namespace or loaded classes, not directly from the global root in this manner.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "An unqualified class name is typically resolved from the current namespace or loaded classes, not directly from the global root in this manner." ⏎ } ⏎ ``` | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 0.08 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: PSR-4 mapping maps the namespace prefix to the directory path relative to the root.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "PSR-4 mapping maps the namespace prefix to the directory path relative to the root." ⏎ } ⏎ ``` | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 0.09 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: Use statements within a function scope limit their scope to that function.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Use statements within a function scope limit their scope to that function." ⏎ } ⏎ ``` | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 0.1 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, assigning an array copies the value, meaning both variables hold independent copies.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "In PHP, assigning an array copies the value, meaning both variables hold independent copies." ⏎ } ⏎ ``` | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.15 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: Assigning an array by value copies the reference, so modifying \$b also affects \$a's content if \$b is modified with array append.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "Assigning an array by value copies the reference, so modifying \$b also affects \$a's content if \$b is modified with array append." ⏎ } ⏎ ``` | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 0.1 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: User-defined variables inside a function are local to that function unless explicitly declared global or accessed via \$GLOBALS.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "User-defined variables inside a function are local to that function unless explicitly declared global or accessed via \$GLOBALS." ⏎ } ⏎ ``` | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 0.1 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset() inside a function modifies the variable in the scope where it is called; it does not remove the global variable from the global scope.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "unset() inside a function modifies the variable in the scope where it is called; it does not remove the global variable from the global scope." ⏎ } ⏎ ``` | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.08 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function modifies the variable by reference, increasing its value.
Raw```json ⏎ { ⏎ "answer": 6, ⏎ "explanation": "The function modifies the variable by reference, increasing its value." ⏎ } ⏎ ``` | верно | Ссылка меняет оригинал: 6. |
T10-L6 0.1 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: A foreach loop iterates over a copy of the array in most cases, so changes inside the loop do not affect the original array directly.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "A foreach loop iterates over a copy of the array in most cases, so changes inside the loop do not affect the original array directly." ⏎ } ⏎ ``` | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.08 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties belong to the class itself, not to individual instances.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Static properties belong to the class itself, not to individual instances." ⏎ } ⏎ ``` | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 0.1 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «yes» Пояснение: In PHP, an array can use a boolean value as a key, and the value associated with that key will be stored.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In PHP, an array can use a boolean value as a key, and the value associated with that key will be stored." ⏎ } ⏎ ``` | неверно верный: «no» | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 0.12 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «no» Пояснение: Generators use the 'yield' keyword to return values, which are retrieved using the 'yield' expression or by iterating over the generator.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Generators use the 'yield' keyword to return values, which are retrieved using the 'yield' expression or by iterating over the generator." ⏎ } ⏎ ``` | неверно верный: «yes» | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 0.07 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: Once a generator is fully consumed, it cannot be rewound.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Once a generator is fully consumed, it cannot be rewound." ⏎ } ⏎ ``` | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 0.08 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: Yield is used to delegate traversal to another generator or iterable.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Yield is used to delegate traversal to another generator or iterable." ⏎ } ⏎ ``` | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 0.11 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «null» Пояснение: The function g() is an anonymous function, and get_class() on a yielded value will return null in this context.
Raw```json ⏎ { ⏎ "answer": "null", ⏎ "explanation": "The function g() is an anonymous function, and get_class() on a yielded value will return null in this context." ⏎ } ⏎ ``` | неверно верный: «generator» | Функция с yield возвращает Generator. |
T11-L5 0.1 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields three values, which are then converted to an array of size three.
Raw```json ⏎ { ⏎ "answer": 3, ⏎ "explanation": "The generator yields three values, which are then converted to an array of size three." ⏎ } ⏎ ``` | верно | yield from делегирует все 3 элемента. |
T11-L6 0.09 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last-In, First-Out) stack data structure.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "SplStack implements a LIFO (Last-In, First-Out) stack data structure." ⏎ } ⏎ ``` | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.06 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator implements the Iterator interface to traverse an array.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "ArrayIterator implements the Iterator interface to traverse an array." ⏎ } ⏎ ``` | верно | Объектная обёртка над массивом. |
T11-L8 0.07 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject instances can be traversed with foreach.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "ArrayObject instances can be traversed with foreach." ⏎ } ⏎ ``` | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.08 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «no» Пояснение: password_hash() automatically generates a unique salt and incorporates it into the resulting hash.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "password_hash() automatically generates a unique salt and incorporates it into the resulting hash." ⏎ } ⏎ ``` | неверно верный: «yes» | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 0.09 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT uses the recommended hashing algorithm for the current PHP version, not md5.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "PASSWORD_DEFAULT uses the recommended hashing algorithm for the current PHP version, not md5." ⏎ } ⏎ ``` | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.09 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «1» Пояснение: password_verify returns true (which evaluates to 1 in many contexts) when the provided password matches the hash.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "password_verify returns true (which evaluates to 1 in many contexts) when the provided password matches the hash." ⏎ } ⏎ ``` | неверно верный: «true» | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.08 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() is used to remove HTML tags and does not protect against SQL injection.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "strip_tags() is used to remove HTML tags and does not protect against SQL injection." ⏎ } ⏎ ``` | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.08 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() replaces the old session ID with a new one, mitigating session fixation attacks.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "session_regenerate_id() replaces the old session ID with a new one, mitigating session fixation attacks." ⏎ } ⏎ ``` | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.1 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: The php_sapi_name() function returns the name of the PHP execution environment.
Raw```json ⏎ { ⏎ "answer": "php_sapi_name()", ⏎ "explanation": "The php_sapi_name() function returns the name of the PHP execution environment." ⏎ } ⏎ ``` | верно | php_sapi_name(). |
T12-L7 0.1 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «no» Пояснение: session_destroy() deletes the session data on the server and sets the session cookie to expire, effectively logging the user out.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "session_destroy() deletes the session data on the server and sets the session cookie to expire, effectively logging the user out." ⏎ } ⏎ ``` | неверно верный: «yes» | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.09 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION superglobal is only populated after calling session_start().
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The $_SESSION superglobal is only populated after calling session_start()." ⏎ } ⏎ ``` | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 0.08 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «7.3» Пояснение: The array_find() function was introduced in PHP version 7.3.
Raw```json ⏎ { ⏎ "answer": "7.3", ⏎ "explanation": "The array_find() function was introduced in PHP version 7.3." ⏎ } ⏎ ``` | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 0.09 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «no» Пояснение: Property hooks (get/set accessors) were introduced in PHP 8.1.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Property hooks (get/set accessors) were introduced in PHP 8.1." ⏎ } ⏎ ``` | неверно верный: «yes» | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.1 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «no» Пояснение: Asymmetric visibility with `public`, `private`, and `protected` has been a feature in PHP for a long time.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Asymmetric visibility with `public`, `private`, and `protected` has been a feature in PHP for a long time." ⏎ } ⏎ ``` | неверно верный: «yes» | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 0.08 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.0» Пояснение: The #[NoDiscard] attribute was introduced in PHP version 8.0.
Raw```json ⏎ { ⏎ "answer": "8.0", ⏎ "explanation": "The #[NoDiscard] attribute was introduced in PHP version 8.0." ⏎ } ⏎ ``` | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 0.08 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.0» Пояснение: The pipe operator |> was introduced in PHP version 8.0.
Raw```json ⏎ { ⏎ "answer": "8.0", ⏎ "explanation": "The pipe operator |> was introduced in PHP version 8.0." ⏎ } ⏎ ``` | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 0.09 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «7.4» Пояснение: The syntax clone($obj, $attributes) was introduced in PHP 7.4.
Raw```json ⏎ { ⏎ "answer": "7.4", ⏎ "explanation": "The syntax clone($obj, $attributes) was introduced in PHP 7.4." ⏎ } ⏎ ``` | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 0.08 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.0» Пояснение: The array_first() and array_last() functions were introduced in PHP version 8.0.
Raw```json ⏎ { ⏎ "answer": "8.0", ⏎ "explanation": "The array_first() and array_last() functions were introduced in PHP version 8.0." ⏎ } ⏎ ``` | неверно верный: «8.5» | PHP 8.5. |
VC-L8 0.08 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «7.4» Пояснение: RFC Partial Function Application v2 was adopted in PHP 7.4.
Raw```json ⏎ { ⏎ "answer": "7.4", ⏎ "explanation": "RFC Partial Function Application v2 was adopted in PHP 7.4." ⏎ } ⏎ ``` | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.08 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «7.4» Пояснение: The clamp() function was introduced in PHP version 7.4.
Raw```json ⏎ { ⏎ "answer": "7.4", ⏎ "explanation": "The clamp() function was introduced in PHP version 7.4." ⏎ } ⏎ ``` | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 0.08 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: RFC Context Managers v2 has not been adopted in PHP as of the knowledge cutoff.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "RFC Context Managers v2 has not been adopted in PHP as of the knowledge cutoff." ⏎ } ⏎ ``` | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 0.08 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: There is no public record of an RFC declining generic types in 2026.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "There is no public record of an RFC declining generic types in 2026." ⏎ } ⏎ ``` | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 0.1 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «no» Пояснение: The ZTS extension has not been enabled by default in PHP as of the time of this knowledge cutoff.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The ZTS extension has not been enabled by default in PHP as of the time of this knowledge cutoff." ⏎ } ⏎ ``` | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 0.12 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «no» Пояснение: PHP introduced native generics through union types and template types in later versions, although full compile-time generics are still evolving.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "PHP introduced native generics through union types and template types in later versions, although full compile-time generics are still evolving." ⏎ } ⏎ ``` | неверно верный: «yes» | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 0.11 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «no» Пояснение: The prompt states PHP 8.5 is the latest stable version as of 2026-11-07, implying 8.6 has not been released yet.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The prompt states PHP 8.5 is the latest stable version as of 2026-11-07, implying 8.6 has not been released yet." ⏎ } ⏎ ``` | неверно верный: «yes» | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 0.1 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «no» Пояснение: PHP 6.0 was released and supported for a period, although PHP 7.0 arrived later.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "PHP 6.0 was released and supported for a period, although PHP 7.0 arrived later." ⏎ } ⏎ ``` | неверно верный: «yes» | Исторический факт: ветка 6 не была релизнута. |
VF-L8 0.08 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: There is no widely known RFC that specifically adds a #[\Deprecated] attribute to the core.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "There is no widely known RFC that specifically adds a #[\Deprecated] attribute to the core." ⏎ } ⏎ ``` | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.09 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: This principle is central to Clean Architecture, ensuring dependencies flow inward.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "This principle is central to Clean Architecture, ensuring dependencies flow inward." ⏎ } ⏎ ``` | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 0.08 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities primarily depend on the language and standard library, not specific frameworks like Doctrine or Symfony.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Domain entities primarily depend on the language and standard library, not specific frameworks like Doctrine or Symfony." ⏎ } ⏎ ``` | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 0.09 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers handle request/response and view rendering, while business logic usually resides in services or use cases.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Controllers handle request/response and view rendering, while business logic usually resides in services or use cases." ⏎ } ⏎ ``` | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 0.09 c | Clean architecture | What sits at the very center of the onion architecture? | «controller» Пояснение: The controller is at the center of the onion architecture, handling requests and coordinating responses.
Raw```json ⏎ { ⏎ "answer": "Controller", ⏎ "explanation": "The controller is at the center of the onion architecture, handling requests and coordinating responses." ⏎ } ⏎ ``` | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 0.08 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Layer-dependency analyzers are designed to catch violations like forbidden calls.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Layer-dependency analyzers are designed to catch violations like forbidden calls." ⏎ } ⏎ ``` | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 0.09 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «yes» Пояснение: Depending on the context, accepting either an HTTP request or an EntityManager can simplify the use case.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Depending on the context, accepting either an HTTP request or an EntityManager can simplify the use case." ⏎ } ⏎ ``` | неверно верный: «no» | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.09 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository abstracts the data access logic, providing a collection of domain objects.
Raw```json ⏎ { ⏎ "answer": "Repository", ⏎ "explanation": "A Repository abstracts the data access logic, providing a collection of domain objects." ⏎ } ⏎ ``` | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 0.1 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «no» Пояснение: Changing the database technology requires changes in the infrastructure/adapter layer to maintain separation.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Changing the database technology requires changes in the infrastructure/adapter layer to maintain separation." ⏎ } ⏎ ``` | неверно верный: «yes» | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 0.08 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a conceptual boundary in Domain-Driven Design, not directly a database table.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "An aggregate is a conceptual boundary in Domain-Driven Design, not directly a database table." ⏎ } ⏎ ``` | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.07 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are immutable and compared based on their attribute values.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Value Objects are immutable and compared based on their attribute values." ⏎ } ⏎ ``` | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.09 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: The aggregate root is the single entity representing the aggregate and the entry point for all changes.
Raw```json ⏎ { ⏎ "answer": "aggregate root", ⏎ "explanation": "The aggregate root is the single entity representing the aggregate and the entry point for all changes." ⏎ } ⏎ ``` | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 0.07 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: Repositories are typically defined to manage the persistence of an entire aggregate root.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Repositories are typically defined to manage the persistence of an entire aggregate root." ⏎ } ⏎ ``` | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.09 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous language is the shared language used by both developers and domain experts in software development.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Ubiquitous language is the shared language used by both developers and domain experts in software development." ⏎ } ⏎ ``` | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 0.09 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «vocabulary» Пояснение: Vocabulary refers to the set of words a model is trained on and consistently uses.
Raw```json ⏎ { ⏎ "answer": "vocabulary", ⏎ "explanation": "Vocabulary refers to the set of words a model is trained on and consistently uses." ⏎ } ⏎ ``` | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 0.1 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: Anemic models are generally not the recommended style for Domain-Driven Design (DDD); rich domain objects are preferred.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Anemic models are generally not the recommended style for Domain-Driven Design (DDD); rich domain objects are preferred." ⏎ } ⏎ ``` | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 0.08 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: Bounded contexts enforce a specific model for a concept within a specific context.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Bounded contexts enforce a specific model for a concept within a specific context." ⏎ } ⏎ ``` | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.1 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Services in the Symfony DI container are lazy-loaded by default, meaning they are instantiated only when first requested.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Services in the Symfony DI container are lazy-loaded by default, meaning they are instantiated only when first requested." ⏎ } ⏎ ``` | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.08 c | Symfony | Which Symfony console command lists all registered routes? | «no» Пояснение: There is no standard built-in Symfony console command specifically named to list all registered routes.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "There is no standard built-in Symfony console command specifically named to list all registered routes." ⏎ } ⏎ ``` | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 0.09 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring automatically discovers and wires services based on their type hints.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony autowiring automatically discovers and wires services based on their type hints." ⏎ } ⏎ ``` | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 0.12 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «no» Пояснение: Twig templates are compiled into PHP code during the request or startup, but they are not generally cached between requests in the same way PHP opcode is.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Twig templates are compiled into PHP code during the request or startup, but they are not generally cached between requests in the same way PHP opcode is." ⏎ } ⏎ ``` | неверно верный: «yes» | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 0.08 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «no» Пояснение: The DI container is rebuilt on every request in the Symfony dev environment by default.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The DI container is rebuilt on every request in the Symfony dev environment by default." ⏎ } ⏎ ``` | неверно верный: «yes» | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.07 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: The APP_ENV environment variable is used by Symfony to select the active environment.
Raw```json ⏎ { ⏎ "answer": "APP_ENV", ⏎ "explanation": "The APP_ENV environment variable is used by Symfony to select the active environment." ⏎ } ⏎ ``` | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 0.12 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony routing typically relies on public methods or specific annotations/attributes to map URLs to controller actions.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Symfony routing typically relies on public methods or specific annotations/attributes to map URLs to controller actions." ⏎ } ⏎ ``` | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 0.1 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: The order of event subscription and listening depends on the event management system's implementation, not inherently on the interface priority.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The order of event subscription and listening depends on the event management system's implementation, not inherently on the interface priority." ⏎ } ⏎ ``` | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 0.09 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: Modern Symfony authentication relies on AuthenticatorInterface and is decoupled from the old Guard system.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Modern Symfony authentication relies on AuthenticatorInterface and is decoupled from the old Guard system." ⏎ } ⏎ ``` | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 0.1 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «no» Пояснение: Symfony typically uses security voters or attributes like @IsGranted for role/permission checks.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony typically uses security voters or attributes like @IsGranted for role/permission checks." ⏎ } ⏎ ``` | неверно верный: «isgranted» | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 0.11 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «no» Пояснение: Voters are the mechanism Symfony uses to check authorization based on an access decision, not specifically for checking access to a specific object like this.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Voters are the mechanism Symfony uses to check authorization based on an access decision, not specifically for checking access to a specific object like this." ⏎ } ⏎ ``` | неверно верный: «yes» | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 0.08 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: Modern Symfony uses PHP attributes for validation constraints, replacing Doctrine annotations.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Modern Symfony uses PHP attributes for validation constraints, replacing Doctrine annotations." ⏎ } ⏎ ``` | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.09 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «no» Пояснение: CSRF protection in Symfony forms requires explicit configuration, not default enabling.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "CSRF protection in Symfony forms requires explicit configuration, not default enabling." ⏎ } ⏎ ``` | неверно верный: «yes» | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 0.08 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony's form validation runs on the server to ensure data integrity.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Symfony's form validation runs on the server to ensure data integrity." ⏎ } ⏎ ``` | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.09 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «php bin/console make:form» Пояснение: The make:form command is used to generate a FormType class.
Raw```json ⏎ { ⏎ "answer": "php bin/console make:form", ⏎ "explanation": "The make:form command is used to generate a FormType class." ⏎ } ⏎ ``` | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 0.1 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony typically uses secure methods like hashing for passwords and stores session data securely.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony typically uses secure methods like hashing for passwords and stores session data securely." ⏎ } ⏎ ``` | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.1 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «no» Пояснение: Symfony bundle configuration is typically defined in config/packages/framework.yaml or specific bundle configuration files, not strictly one file per bundle.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Symfony bundle configuration is typically defined in config/packages/framework.yaml or specific bundle configuration files, not strictly one file per bundle." ⏎ } ⏎ ``` | неверно верный: «yes» | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 0.1 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «no» Пояснение: Environment variables containing secrets should generally be excluded from version control, regardless of whether they are committed or not.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Environment variables containing secrets should generally be excluded from version control, regardless of whether they are committed or not." ⏎ } ⏎ ``` | неверно верный: «yes» | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.09 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «service:list» Пояснение: The `service:list` command lists all registered services and their aliases in the Symfony container.
Raw```json ⏎ { ⏎ "answer": "service:list", ⏎ "explanation": "The `service:list` command lists all registered services and their aliases in the Symfony container." ⏎ } ⏎ ``` | неверно верный: «debug:container» | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 0.09 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: The setParameter method is available in the container and can be called from controllers.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The setParameter method is available in the container and can be called from controllers." ⏎ } ⏎ ``` | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.08 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: By default, Symfony services are private unless explicitly configured otherwise.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "By default, Symfony services are private unless explicitly configured otherwise." ⏎ } ⏎ ``` | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 0.07 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «yes» Пояснение: Configuration is mandatory for every bundle in Symfony.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Configuration is mandatory for every bundle in Symfony." ⏎ } ⏎ ``` | неверно верный: «no» | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.08 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: The %env(VAR)% syntax is commonly used in configuration files like services.yaml to inject environment variable values.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The %env(VAR)% syntax is commonly used in configuration files like services.yaml to inject environment variable values." ⏎ } ⏎ ``` | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.09 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «true» Пояснение: The SYMFONY_ENV=debug setting enables debug mode.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The SYMFONY_ENV=debug setting enables debug mode." ⏎ } ⏎ ``` | неверно верный: «app_debug» | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 0.07 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: A single message can be configured to be handled by multiple handlers.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "A single message can be configured to be handled by multiple handlers." ⏎ } ⏎ ``` | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 0.09 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: Sync transport blocks the calling thread until the message is processed, whereas async transport does not block.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Sync transport blocks the calling thread until the message is processed, whereas async transport does not block." ⏎ } ⏎ ``` | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.11 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «php bin/console messenger:consume» Пояснение: The `messenger:consume` command is used to start the worker that processes the message queue.
Raw```json ⏎ { ⏎ "answer": "php bin/console messenger:consume", ⏎ "explanation": "The `messenger:consume` command is used to start the worker that processes the message queue." ⏎ } ⏎ ``` | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 0.08 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: Retry strategies are typically configured on a per-transport basis in Messenger.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Retry strategies are typically configured on a per-transport basis in Messenger." ⏎ } ⏎ ``` | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 0.07 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Messenger uses JSON for serializing messages by default.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Messenger uses JSON for serializing messages by default." ⏎ } ⏎ ``` | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 0.08 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: The Symfony Scheduler is used to schedule tasks that dispatch messages via the Messenger component.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The Symfony Scheduler is used to schedule tasks that dispatch messages via the Messenger component." ⏎ } ⏎ ``` | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.09 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «no» Пояснение: Messenger itself uses various transports, but it doesn't inherently store messages in database tables via Doctrine.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Messenger itself uses various transports, but it doesn't inherently store messages in database tables via Doctrine." ⏎ } ⏎ ``` | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 0.08 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Custom middleware can be inserted before or after built-in middleware in the Messenger pipeline.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Custom middleware can be inserted before or after built-in middleware in the Messenger pipeline." ⏎ } ⏎ ``` | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 0.1 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony releases happen more frequently than that, with various release schedules.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony releases happen more frequently than that, with various release schedules." ⏎ } ⏎ ``` | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 0.08 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «7.4» Пояснение: Symfony 8 requires PHP 7.4 or higher.
Raw```json ⏎ { ⏎ "answer": "7.4", ⏎ "explanation": "Symfony 8 requires PHP 7.4 or higher." ⏎ } ⏎ ``` | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 0.08 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 deprecated docblock annotations in favor of attributes.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Symfony 7.0 deprecated docblock annotations in favor of attributes." ⏎ } ⏎ ``` | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 0.09 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: importmap.php is a mechanism used to manage CSS/JS assets without requiring Node or webpack.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "importmap.php is a mechanism used to manage CSS/JS assets without requiring Node or webpack." ⏎ } ⏎ ``` | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 0.09 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony releases often have support cycles, and LTS versions are specifically provided for long-term support.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Symfony releases often have support cycles, and LTS versions are specifically provided for long-term support." ⏎ } ⏎ ``` | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 0.09 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Major Symfony releases often introduce breaking changes that can remove deprecated features.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Major Symfony releases often introduce breaking changes that can remove deprecated features." ⏎ } ⏎ ``` | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 0.11 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «no» Пояснение: While major releases have documentation, a comprehensive, mandatory upgrade guide for every single change is not guaranteed.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "While major releases have documentation, a comprehensive, mandatory upgrade guide for every single change is not guaranteed." ⏎ } ⏎ ``` | неверно верный: «yes» | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 0.1 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «asset_loader» Пояснение: The AssetLoader component manages assets and importmaps in Symfony applications.
Raw```json ⏎ { ⏎ "answer": "asset_loader", ⏎ "explanation": "The AssetLoader component manages assets and importmaps in Symfony applications." ⏎ } ⏎ ``` | неверно верный: «asset-mapper» | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 0.08 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony 8.2 has not been released as of the current date.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony 8.2 has not been released as of the current date." ⏎ } ⏎ ``` | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 0.1 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «no» Пояснение: The information provided is a prediction about a future release schedule, not a statement of current fact.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The information provided is a prediction about a future release schedule, not a statement of current fact." ⏎ } ⏎ ``` | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 0.09 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony 8.2 is the next major version after 8.1.
Raw```json ⏎ { ⏎ "answer": "8.2", ⏎ "explanation": "Symfony 8.2 is the next major version after 8.1." ⏎ } ⏎ ``` | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 0.12 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony releases typically introduce new features and improvements, but major releases don't always mandate rewriting applications immediately.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony releases typically introduce new features and improvements, but major releases don't always mandate rewriting applications immediately." ⏎ } ⏎ ``` | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 0.1 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «no» Пояснение: Updating between major versions often requires code changes to accommodate breaking API or syntax changes.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Updating between major versions often requires code changes to accommodate breaking API or syntax changes." ⏎ } ⏎ ``` | неверно верный: «yes» | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 0.1 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: The 8.4 minor version is the last one released on the 8.x branch before Symfony 9.0.
Raw```json ⏎ { ⏎ "answer": "8.4", ⏎ "explanation": "The 8.4 minor version is the last one released on the 8.x branch before Symfony 9.0." ⏎ } ⏎ ``` | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 0.1 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.2 supports PHP 8.1 and above, and PHP 8.5 is not a mandatory requirement for it.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony 8.2 supports PHP 8.1 and above, and PHP 8.5 is not a mandatory requirement for it." ⏎ } ⏎ ``` | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 0.11 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «no» Пояснение: Deprecations are generally removed when a major version is released, regardless of the branch they were added in.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Deprecations are generally removed when a major version is released, regardless of the branch they were added in." ⏎ } ⏎ ``` | неверно верный: «yes» | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 0.09 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's templating engine is sandboxed and does not allow arbitrary PHP code execution.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Twig's templating engine is sandboxed and does not allow arbitrary PHP code execution." ⏎ } ⏎ ``` | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.07 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig automatically escapes variables by default to prevent XSS attacks.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Twig automatically escapes variables by default to prevent XSS attacks." ⏎ } ⏎ ``` | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.07 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The |e filter escapes the string for safe output in an HTML context.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The |e filter escapes the string for safe output in an HTML context." ⏎ } ⏎ ``` | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.08 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «number» Пояснение: The `number` filter from twig/intl-extra formats a number according to a locale.
Raw```json ⏎ { ⏎ "answer": "number", ⏎ "explanation": "The `number` filter from twig/intl-extra formats a number according to a locale." ⏎ } ⏎ ``` | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 0.08 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter tells PHP to output the value without escaping.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The |raw filter tells PHP to output the value without escaping." ⏎ } ⏎ ``` | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.11 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: Double curly braces are used for variable/expression output, and curly braces with percent signs are used for control structures.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Double curly braces are used for variable/expression output, and curly braces with percent signs are used for control structures." ⏎ } ⏎ ``` | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.1 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Variables can be declared and manipulated within a Twig template using the `{% set ... %}` tag.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Variables can be declared and manipulated within a Twig template using the `{% set ... %}` tag." ⏎ } ⏎ ``` | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.08 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The `dump` function in Twig is used to output the debug structure of a variable.
Raw```json ⏎ { ⏎ "answer": "dump", ⏎ "explanation": "The `dump` function in Twig is used to output the debug structure of a variable." ⏎ } ⏎ ``` | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.09 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end framework for responsive design and UI components, not a full Single Page Application (SPA) framework.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap is a front-end framework for responsive design and UI components, not a full Single Page Application (SPA) framework." ⏎ } ⏎ ``` | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.09 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The 'container' class creates a responsive container with a fixed maximum width on different screen sizes.
Raw```json ⏎ { ⏎ "answer": "container", ⏎ "explanation": "The 'container' class creates a responsive container with a fixed maximum width on different screen sizes." ⏎ } ⏎ ``` | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 0.09 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: Bootstrap's grid system is built on CSS Flexbox, not CSS floats.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Bootstrap's grid system is built on CSS Flexbox, not CSS floats." ⏎ } ⏎ ``` | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 0.1 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «no» Пояснение: Bootstrap has several breakpoints, more than just sm, md, lg, xl, xxl.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Bootstrap has several breakpoints, more than just sm, md, lg, xl, xxl." ⏎ } ⏎ ``` | неверно верный: «yes» | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 0.09 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: Utility classes like .mt-3 use spacing values that are multiples of the configured spacing scale.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Utility classes like .mt-3 use spacing values that are multiples of the configured spacing scale." ⏎ } ⏎ ``` | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.09 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: The data-bs-toggle attribute is used to indicate an interactive component in Bootstrap.
Raw```json ⏎ { ⏎ "answer": "data-bs-toggle", ⏎ "explanation": "The data-bs-toggle attribute is used to indicate an interactive component in Bootstrap." ⏎ } ⏎ ``` | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.08 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 components can be used with plain JavaScript for functionality.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Bootstrap 5 components can be used with plain JavaScript for functionality." ⏎ } ⏎ ``` | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 0.08 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «yes» Пояснение: Bootstrap supports dark mode by adding the 'dark' class to the root HTML element.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Bootstrap supports dark mode by adding the 'dark' class to the root HTML element." ⏎ } ⏎ ``` | неверно верный: «no» | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 0.12 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine uses schema migration tools or explicit configuration to create tables, not on the fly during the first runtime usage.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Doctrine uses schema migration tools or explicit configuration to create tables, not on the fly during the first runtime usage." ⏎ } ⏎ ``` | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.07 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: The persist method marks a new object as managed by the EntityManager.
Raw```json ⏎ { ⏎ "answer": "persist", ⏎ "explanation": "The persist method marks a new object as managed by the EntityManager." ⏎ } ⏎ ``` | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 0.09 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: EntityManager::merge() is used to merge a detached entity into the persistence context, making it managed.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "EntityManager::merge() is used to merge a detached entity into the persistence context, making it managed." ⏎ } ⏎ ``` | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.08 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL queries focus on data entities and their fields rather than specific table and column names.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "DQL queries focus on data entities and their fields rather than specific table and column names." ⏎ } ⏎ ``` | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.08 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «false» Пояснение: If no record is found, the find method typically returns false or null.
Raw```json ⏎ { ⏎ "answer": false, ⏎ "explanation": "If no record is found, the find method typically returns false or null." ⏎ } ⏎ ``` | неверно верный: «null» | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 0.09 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: Doctrine does not automatically call flush() at the end of every request; it must be explicitly called.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Doctrine does not automatically call flush() at the end of every request; it must be explicitly called." ⏎ } ⏎ ``` | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 0.09 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «no» Пояснение: While a managed entity change is tracked, flush() is typically what explicitly commits the changes to the database.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "While a managed entity change is tracked, flush() is typically what explicitly commits the changes to the database." ⏎ } ⏎ ``` | неверно верный: «yes» | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.09 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: The remove() method typically queues the delete operation, which is then executed when flush() is called.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The remove() method typically queues the delete operation, which is then executed when flush() is called." ⏎ } ⏎ ``` | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 0.1 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC allows readers to proceed while writers are active, and vice versa, minimizing blocking.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "MVCC allows readers to proceed while writers are active, and vice versa, minimizing blocking." ⏎ } ⏎ ``` | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.08 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command is used in SQL to show the execution plan of a query.
Raw```json ⏎ { ⏎ "answer": "EXPLAIN", ⏎ "explanation": "The EXPLAIN command is used in SQL to show the execution plan of a query." ⏎ } ⏎ ``` | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 0.1 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL and GENERATED AS IDENTITY are different syntax options used in different SQL dialects for auto-incrementing primary keys.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "SERIAL and GENERATED AS IDENTITY are different syntax options used in different SQL dialects for auto-incrementing primary keys." ⏎ } ⏎ ``` | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 0.08 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, a PostgreSQL UNIQUE constraint allows multiple rows with NULL values in the column.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "By default, a PostgreSQL UNIQUE constraint allows multiple rows with NULL values in the column." ⏎ } ⏎ ``` | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.08 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: string_agg is the PostgreSQL aggregate function used to concatenate strings.
Raw```json ⏎ { ⏎ "answer": "string_agg", ⏎ "explanation": "string_agg is the PostgreSQL aggregate function used to concatenate strings." ⏎ } ⏎ ``` | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 0.1 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: VACUUM marks dead tuples as reusable within the table, it does not immediately return space to the OS.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "VACUUM marks dead tuples as reusable within the table, it does not immediately return space to the OS." ⏎ } ⏎ ``` | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.09 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause specifies the groups into which the window function is partitioned.
Raw```json ⏎ { ⏎ "answer": "PARTITION BY", ⏎ "explanation": "The PARTITION BY clause specifies the groups into which the window function is partitioned." ⏎ } ⏎ ``` | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 0.08 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: The READ COMMITTED isolation level primarily protects against dirty reads, not non-repeatable reads.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The READ COMMITTED isolation level primarily protects against dirty reads, not non-repeatable reads." ⏎ } ⏎ ``` | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.09 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «no» Пояснение: PostgreSQL defaults to transaction control based on session settings, not implicit autocommit for every statement.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "PostgreSQL defaults to transaction control based on session settings, not implicit autocommit for every statement." ⏎ } ⏎ ``` | неверно верный: «yes» | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.08 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT command permanently saves any changes made during the current transaction.
Raw```json ⏎ { ⏎ "answer": "COMMIT", ⏎ "explanation": "The COMMIT command permanently saves any changes made during the current transaction." ⏎ } ⏎ ``` | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.11 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes significantly speed up SELECT operations, and they can also benefit UPDATE and DELETE operations when used to locate rows.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Indexes significantly speed up SELECT operations, and they can also benefit UPDATE and DELETE operations when used to locate rows." ⏎ } ⏎ ``` | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.09 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: PostgreSQL uses SAVEPOINTs to establish points to which a transaction can be rolled back.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "PostgreSQL uses SAVEPOINTs to establish points to which a transaction can be rolled back." ⏎ } ⏎ ``` | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.08 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «yes» Пояснение: EXPLAIN ANALYZE shows the execution plan and the actual runtime statistics of the query.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "EXPLAIN ANALYZE shows the execution plan and the actual runtime statistics of the query." ⏎ } ⏎ ``` | неверно верный: «no» | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.09 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds vector types and indexes for vector similarity search.
Raw```json ⏎ { ⏎ "answer": "pgvector", ⏎ "explanation": "pgvector is the PostgreSQL extension that adds vector types and indexes for vector similarity search." ⏎ } ⏎ ``` | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.08 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index only includes rows that satisfy the specified WHERE clause condition.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "A partial index only includes rows that satisfy the specified WHERE clause condition." ⏎ } ⏎ ``` | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 0.11 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: SERIALIZABLE isolation level in PostgreSQL uses snapshot isolation and stricter checks to prevent write conflicts, not just row locking on reads.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "SERIALIZABLE isolation level in PostgreSQL uses snapshot isolation and stricter checks to prevent write conflicts, not just row locking on reads." ⏎ } ⏎ ``` | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.1 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status code 201 signifies that the request has succeeded and a new resource has been created.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "HTTP status code 201 signifies that the request has succeeded and a new resource has been created." ⏎ } ⏎ ``` | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.11 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: The 204 No Content status code indicates successful processing where no content is returned.
Raw```json ⏎ { ⏎ "answer": 204, ⏎ "explanation": "The 204 No Content status code indicates successful processing where no content is returned." ⏎ } ⏎ ``` | верно | 204 No Content; RFC 9110. |
T19-L3 0.09 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «no» Пояснение: DELETE is generally not idempotent; subsequent DELETE requests might result in a 404 if the resource is already deleted.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "DELETE is generally not idempotent; subsequent DELETE requests might result in a 404 if the resource is already deleted." ⏎ } ⏎ ``` | неверно верный: «yes» | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.09 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server to indicate which origins are allowed to access the resource.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The Access-Control-Allow-Origin header is sent by the server to indicate which origins are allowed to access the resource." ⏎ } ⏎ ``` | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.1 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: Status code 429 is specifically used to indicate that the user has sent too many requests in a given amount of time.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Status code 429 is specifically used to indicate that the user has sent too many requests in a given amount of time." ⏎ } ⏎ ``` | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.07 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: 5xx codes indicate server errors, while 4xx codes indicate client errors.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "5xx codes indicate server errors, while 4xx codes indicate client errors." ⏎ } ⏎ ``` | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.09 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the media type of the resource being sent in the response body.
Raw```json ⏎ { ⏎ "answer": "Content-Type", ⏎ "explanation": "The Content-Type header specifies the media type of the resource being sent in the response body." ⏎ } ⏎ ``` | верно | Content-Type: application/json и т.п. |
T19-L8 0.08 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «no» Пояснение: Both PUT and PATCH can be designed to be idempotent according to their respective specifications.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Both PUT and PATCH can be designed to be idempotent according to their respective specifications." ⏎ } ⏎ ``` | неверно верный: «yes» | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 0.11 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using a plain equality check is insecure against timing attacks; use password_verify() instead.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Using a plain equality check is insecure against timing attacks; use password_verify() instead." ⏎ } ⏎ ``` | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.09 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are indeed issued by the server, tied to the session, and validated on state-changing requests.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "CSRF tokens are indeed issued by the server, tied to the session, and validated on state-changing requests." ⏎ } ⏎ ``` | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.09 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy header is used to define the CSP policy.
Raw```json ⏎ { ⏎ "answer": "Content-Security-Policy", ⏎ "explanation": "The Content-Security-Policy header is used to define the CSP policy." ⏎ } ⏎ ``` | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 0.09 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization framework, not an authentication protocol, though it facilitates authentication.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "OAuth 2.0 is an authorization framework, not an authentication protocol, though it facilitates authentication." ⏎ } ⏎ ``` | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 0.1 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS prevention primarily involves output encoding when rendering data, not just server-side input validation.
Raw```json ⏎ { ⏎ "answer": false, ⏎ "explanation": "XSS prevention primarily involves output encoding when rendering data, not just server-side input validation." ⏎ } ⏎ ``` | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.08 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «authorization_code» Пояснение: The authorization code is the temporary credential exchanged for an access token.
Raw```json ⏎ { ⏎ "answer": "authorization_code", ⏎ "explanation": "The authorization code is the temporary credential exchanged for an access token." ⏎ } ⏎ ``` | неверно верный: «code» | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.08 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are long-lived and are used to obtain new access tokens.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Refresh tokens are long-lived and are used to obtain new access tokens." ⏎ } ⏎ ``` | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 0.09 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: The password salt does not need to be kept secret; it is typically stored alongside the hashed password.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The password salt does not need to be kept secret; it is typically stored alongside the hashed password." ⏎ } ⏎ ``` | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.09 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: Extending TestCase is generally required to gain access to useful testing features provided by PHPUnit.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Extending TestCase is generally required to gain access to useful testing features provided by PHPUnit." ⏎ } ⏎ ``` | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.08 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each individual test method.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "setUp() runs before each individual test method." ⏎ } ⏎ ``` | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.08 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider can be configured to run with multiple sets of arguments.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "A data provider can be configured to run with multiple sets of arguments." ⏎ } ⏎ ``` | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.09 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: The expectException method is used in PHPUnit to assert that a specific exception is thrown.
Raw```json ⏎ { ⏎ "answer": "expectException", ⏎ "explanation": "The expectException method is used in PHPUnit to assert that a specific exception is thrown." ⏎ } ⏎ ``` | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.09 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: Mocks verify interactions, while stubs provide canned answers for methods.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Mocks verify interactions, while stubs provide canned answers for methods." ⏎ } ⏎ ``` | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.09 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: The #[DataProvider] attribute is the modern and recommended way to provide data to tests in PHPUnit 10+.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The #[DataProvider] attribute is the modern and recommended way to provide data to tests in PHPUnit 10+." ⏎ } ⏎ ``` | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.1 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies through various mechanisms, such as setup methods or test fixtures.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "PHPUnit supports test dependencies through various mechanisms, such as setup methods or test fixtures." ⏎ } ⏎ ``` | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.08 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «random» Пояснение: The --random option in PHPUnit makes tests run in a random order.
Raw```json ⏎ { ⏎ "answer": "random", ⏎ "explanation": "The --random option in PHPUnit makes tests run in a random order." ⏎ } ⏎ ``` | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 2.54 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «-4» Пояснение: intdiv performs integer division, truncating the result towards zero.
Raw```json ⏎ { ⏎ "answer": "-4", ⏎ "explanation": "intdiv performs integer division, truncating the result towards zero." ⏎ } ⏎ ``` | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.08 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «9» Пояснение: The expression calculates the square of -3, which is 9.
Raw```json ⏎ { ⏎ "answer": 9, ⏎ "explanation": "The expression calculates the square of -3, which is 9." ⏎ } ⏎ ``` | неверно верный: «-9» | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 0.08 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «false» Пояснение: The string '1e1' is not equal to the string '10'.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The string '1e1' is not equal to the string '10'." ⏎ } ⏎ ``` | неверно верный: «true» | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 0.08 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: Since 'a' does not match the case '0', the default case is executed.
Raw```json ⏎ { ⏎ "answer": "other", ⏎ "explanation": "Since 'a' does not match the case '0', the default case is executed." ⏎ } ⏎ ``` | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 0.08 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «1» Пояснение: strtr replaces characters in the string based on the provided mapping.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "strtr replaces characters in the string based on the provided mapping." ⏎ } ⏎ ``` | неверно верный: «2c» | strtr with an array prefers the longest matching key. |
T03-L10 0.22 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «['o']» Пояснение: substr('hello', -10) extracts the last 10 characters from the string 'hello', which results in 'hello' itself if the requested length is greater than the string length, but in this context with a negative length, it extracts from the end. Since the string length is 5, substr('hello', -10) will return the entire string 'hello'.
Raw```json ⏎ { ⏎ "answer": "['o']", ⏎ "explanation": "substr('hello', -10) extracts the last 10 characters from the string 'hello', which results in 'hello' itself if the requested length is greater than the string length, but in this context with a negative length, it extracts from the end. Since the string length is 5, substr('hello', -10) will return the entire string 'hello'." ⏎ } ⏎ ``` | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 0.14 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,m» Пояснение: The '+' operator for arrays merges the arrays, and array_keys gets the keys of the resulting array, which are then joined by a comma.
Raw```json ⏎ { ⏎ "answer": "k,m", ⏎ "explanation": "The '+' operator for arrays merges the arrays, and array_keys gets the keys of the resulting array, which are then joined by a comma." ⏎ } ⏎ ``` | неверно верный: «k,n,m» | The + operator: on duplicate string keys the left array wins. |
T04-L10 0.11 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «xyz» Пояснение: The array is sorted based on the third element (index 2) of each inner array, resulting in the concatenation of the second elements.
Raw```json ⏎ { ⏎ "answer": "xyz", ⏎ "explanation": "The array is sorted based on the third element (index 2) of each inner array, resulting in the concatenation of the second elements." ⏎ } ⏎ ``` | неверно верный: «yxz» | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 2.7 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «0» Пояснение: The spread operator unpacks the array into arguments, but the function expects two integer arguments, and the call uses the first two values from the array.
Raw```json ⏎ { ⏎ "answer": "0", ⏎ "explanation": "The spread operator unpacks the array into arguments, but the function expects two integer arguments, and the call uses the first two values from the array." ⏎ } ⏎ ``` | неверно верный: «4» | String keys of a spread array become named arguments. |
T05-L9 0.23 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «null» Пояснение: Calling a method on a null object results in a fatal error or a warning, but in the context of this simplified execution flow where $f$ is a function call, attempting to call $f()$ when $f$ is null will result in a fatal error or undefined behavior, but given the structure, it points towards the final state of the object being null.
Raw```json ⏎ { ⏎ "answer": "NULL", ⏎ "explanation": "Calling a method on a null object results in a fatal error or a warning, but in the context of this simplified execution flow where $f$ is a function call, attempting to call $f()$ when $f$ is null will result in a fatal error or undefined behavior, but given the structure, it points towards the final state of the object being null." ⏎ } ⏎ ``` | неверно верный: «3» | First-class callable syntax binds $this at creation time. |
T06-L9 0.09 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: The static call returns the class name of the class where the method is called, which is B.
Raw```json ⏎ { ⏎ "answer": "B", ⏎ "explanation": "The static call returns the class name of the class where the method is called, which is B." ⏎ } ⏎ ``` | верно | Late static binding: static::class is the receiver's class. |
T06-L10 0.1 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The setter method multiplies the input value by 2, so 5 becomes 10.
Raw```json ⏎ { ⏎ "answer": 10, ⏎ "explanation": "The setter method multiplies the input value by 2, so 5 becomes 10." ⏎ } ⏎ ``` | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 0.13 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: The trait with the most specific method overrides the others, and the method with `insteadof` is accessible via the original trait's name.
Raw```json ⏎ { ⏎ "answer": "BA", ⏎ "explanation": "The trait with the most specific method overrides the others, and the method with `insteadof` is accessible via the original trait's name." ⏎ } ⏎ ``` | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 0.08 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «1» Пояснение: The static property is shared across classes using the trait.
Raw```json ⏎ { ⏎ "answer": 1, ⏎ "explanation": "The static property is shared across classes using the trait." ⏎ } ⏎ ``` | неверно верный: «0» | A trait's static property is copied into each consuming class. |
T08-L10 0.08 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: The finally block's return value overrides the return value of the try block.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "The finally block's return value overrides the return value of the try block." ⏎ } ⏎ ``` | верно | A return in finally overrides the return from try. |
T08-L9 0.08 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The LogicException thrown in the finally block is caught and its message is echoed.
Raw```json ⏎ { ⏎ "answer": "second", ⏎ "explanation": "The LogicException thrown in the finally block is caught and its message is echoed." ⏎ } ⏎ ``` | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 0.12 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «n\app\foo|n\app\foo» Пояснение: The code echoes the fully qualified class names of Baz twice, separated by a pipe.
Raw```json ⏎ { ⏎ "answer": "N\\App\\Foo|N\\App\\Foo", ⏎ "explanation": "The code echoes the fully qualified class names of Baz twice, separated by a pipe." ⏎ } ⏎ ``` | неверно верный: «app\foo|baz» | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 0.15 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «json» Пояснение: ```json
{
"answer": "no",
"explanation": "class_exists($c) is false because \$c is a string 'Foo', not a class name, and class_exists(\"Ns\\Foo\") is false because the class Foo is not defined in the current scope."
}
```
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "class_exists($c) is false because \$c is a string 'Foo', not a class name, and class_exists(\"Ns\\Foo\") is false because the class Foo is not defined in the current scope." ⏎ } ⏎ ``` | неверно верный: «noyes» парсинг: текст (фолбэк) | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 0.12 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,3» Пояснение: Modifying the reference variable $v modifies the elements within the array $a, but implode uses the original array values.
Raw```json ⏎ { ⏎ "answer": "1,2,3", ⏎ "explanation": "Modifying the reference variable $v modifies the elements within the array $a, but implode uses the original array values." ⏎ } ⏎ ``` | неверно верный: «1,2,99» | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 0.1 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «2» Пояснение: The static variable $n is shared by all instances of class A and is incremented sequentially.
Raw```json ⏎ { ⏎ "answer": "2", ⏎ "explanation": "The static variable $n is shared by all instances of class A and is incremented sequentially." ⏎ } ⏎ ``` | неверно верный: «3» | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 0.18 c | Generators, iterators, SPL | What does this code output?
```php
function g(): Generator
{
$x = yield 1;
return $x + 1;
}
$g = g();
$g->send(10);
echo $g->getReturn();
``` | «12» Пояснение: The generator yields 1, and then the return value is 1 + 1 (from the send value 10, which is not used in the calculation, but the yield returns the next value). However, the return value is determined by the final expression after yield.
Raw```json ⏎ { ⏎ "answer": "12", ⏎ "explanation": "The generator yields 1, and then the return value is 1 + 1 (from the send value 10, which is not used in the calculation, but the yield returns the next value). However, the return value is determined by the final expression after yield." ⏎ } ⏎ ``` | неверно верный: «11» | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 0.09 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2» Пояснение: The outer generator yields the results from the inner generator, which are 1 and 2.
Raw```json ⏎ { ⏎ "answer": "1,2", ⏎ "explanation": "The outer generator yields the results from the inner generator, which are 1 and 2." ⏎ } ⏎ ``` | неверно верный: «ok,2» | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 0.1 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «no» Пояснение: The current hash was created with a cost of 4, so it does not need rehashing for cost 5.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The current hash was created with a cost of 4, so it does not need rehashing for cost 5." ⏎ } ⏎ ``` | неверно верный: «noyes» | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 0.12 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: The bitwise AND operation results in a non-zero value, so the ternary operator returns the 'strict-out' string.
Raw```json ⏎ { ⏎ "answer": "strict-out", ⏎ "explanation": "The bitwise AND operation results in a non-zero value, so the ternary operator returns the 'strict-out' string." ⏎ } ⏎ ``` | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 0.1 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: The code checks if the 'X-Token' header value matches 'abc', which it does.
Raw```json ⏎ { ⏎ "answer": "mapped", ⏎ "explanation": "The code checks if the 'X-Token' header value matches 'abc', which it does." ⏎ } ⏎ ``` | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 0.14 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bac» Пояснение: Event listeners are executed in order of their priority (lower number first), so the listener with priority 5 runs first, followed by priority 10, and then the second listener.
Raw```json ⏎ { ⏎ "answer": "BAC", ⏎ "explanation": "Event listeners are executed in order of their priority (lower number first), so the listener with priority 5 runs first, followed by priority 10, and then the second listener." ⏎ } ⏎ ``` | неверно верный: «bca» | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 0.09 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: find() retrieves the same entity instance from the EntityManager.
Raw```json ⏎ { ⏎ "answer": "same", ⏎ "explanation": "find() retrieves the same entity instance from the EntityManager." ⏎ } ⏎ ``` | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 0.09 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: The user is persisted and then removed, so the table remains empty after flushing.
Raw```json ⏎ { ⏎ "answer": "0", ⏎ "explanation": "The user is persisted and then removed, so the table remains empty after flushing." ⏎ } ⏎ ``` | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.13 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «2» Пояснение: The count function counts all non-NULL values in the column x, which are 1 and the second row's NULL value is excluded.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "The count function counts all non-NULL values in the column x, which are 1 and the second row's NULL value is excluded." ⏎ } ⏎ ``` | неверно верный: «1» | count(column) skips NULLs; count(*) would return 2. |
T15-L9 0.63 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,50» Пояснение: The query calculates the cumulative sum of 'x' values and then aggregates the 'id' and the cumulative sum into a comma-separated string, but the provided query actually calculates the cumulative sum and then aggregates the *ID* and the *cumulative sum* itself. Wait, let's re-evaluate the inner query: it selects `id` and the cumulative sum `s`. The outer query then aggregates the cumulative sum (`s` cast to text) ordered by `id`. Since the cumulative sums are 10, 30, and 60 (10, 10+20=30, 30+30=60), the output is '10,30,60'. Wait, my manual calculation was wrong. Let's trace: id=1, x=10, s=10. id=2, x=20, s=30. id=3, x=30, s=60. The final result is string_agg('10', ',') + string_agg('30', ',') + string_agg('60', ',') which is '10,30,60'. Rereading the query: `string_agg(s::text, ',' ORDER BY id)`. This will aggregate the values of `s` ordered by `id`. So it should be '10,30,60'.
Raw```json ⏎ { ⏎ "answer": "10,30,50", ⏎ "explanation": "The query calculates the cumulative sum of 'x' values and then aggregates the 'id' and the cumulative sum into a comma-separated string, but the provided query actually calculates the cumulative sum and then aggregates the *ID* and the *cumulative sum* itself. Wait, let's re-evaluate the inner query: it selects `id` and the cumulative sum `s`. The outer query then aggregates the cumulative sum (`s` cast to text) ordered by `id`. Since the cumulative sums are 10, 30, and 60 (10, 10+20=30, 30+30=60), the output is '10,30,60'. Wait, my manual calculation was wrong. Let's trace: id=1, x=10, s=10. id=2, x=20, s=30. id=3, x=30, s=60. The final result is string_agg('10', ',') + string_agg('30', ',') + string_agg('60', ',') which is '10,30,60'. Rereading the query: `string_agg(s::text, ',' ORDER BY id)`. This will aggregate the values of `s` ordered by `id`. So it should be '10,30,60'." ⏎ } ⏎ ``` | неверно верный: «10,30,60» | With ORDER BY the default window frame is running (start to current row). |
T16-L9 0.1 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: The Trace middleware prints its tag before passing the message to the next middleware in the stack.
Raw```json ⏎ { ⏎ "answer": "M1M2", ⏎ "explanation": "The Trace middleware prints its tag before passing the message to the next middleware in the stack." ⏎ } ⏎ ``` | верно | The first-added middleware runs first (outermost). |
T16-L10 0.11 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «10» Пояснение: The first handler increments $n by 1, and the second handler increments it by 10, resulting in a final value of 10.
Raw```json ⏎ { ⏎ "answer": "10", ⏎ "explanation": "The first handler increments $n by 1, and the second handler increments it by 10, resulting in a final value of 10." ⏎ } ⏎ ``` | неверно верный: «11» | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 0.13 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The `ON CONFLICT DO NOTHING` clause prevents the second insertion of the duplicate value, leaving only one row in the table.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "The `ON CONFLICT DO NOTHING` clause prevents the second insertion of the duplicate value, leaving only one row in the table." ⏎ } ⏎ ``` | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 0.1 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «1» Пояснение: The UNIQUE constraint prevents the second insert of the duplicate value from succeeding.
Raw```json ⏎ { ⏎ "answer": 1, ⏎ "explanation": "The UNIQUE constraint prevents the second insert of the duplicate value from succeeding." ⏎ } ⏎ ``` | неверно верный: «2» | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 0.1 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «1» Пояснение: The --filter flag limits the execution to tests matching 'test_sum'.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "The --filter flag limits the execution to tests matching 'test_sum'." ⏎ } ⏎ ``` | неверно верный: «6» | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 0.12 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2,2» Пояснение: The DataProvider runs the test twice, and both tests will fail because the assertion is incorrect.
Raw```json ⏎ { ⏎ "answer": "2,2", ⏎ "explanation": "The DataProvider runs the test twice, and both tests will fail because the assertion is incorrect." ⏎ } ⏎ ``` | неверно верный: «2,1» | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.1 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The `-d` option in curl is used to send data in the body of an HTTP request, typically for POST requests.
Raw```json ⏎ { ⏎ "answer": "POST", ⏎ "explanation": "The `-d` option in curl is used to send data in the body of an HTTP request, typically for POST requests." ⏎ } ⏎ ``` | верно | -d/-F switches curl to POST by default. |
T19-L10 0.1 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The `-d` flag in curl sends data in the body of the request, typically used with POST requests.
Raw```json ⏎ { ⏎ "answer": "POST", ⏎ "explanation": "The `-d` flag in curl sends data in the body of the request, typically used with POST requests." ⏎ } ⏎ ``` | неверно верный: «get» | -G turns -d data into the query string; the method stays GET. |
T20-L9 0.09 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «401» Пояснение: A 401 Unauthorized status code is typically returned for invalid client credentials.
Raw```json ⏎ { ⏎ "answer": 401, ⏎ "explanation": "A 401 Unauthorized status code is typically returned for invalid client credentials." ⏎ } ⏎ ``` | неверно верный: «invalid_client» | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 0.12 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «no» Пояснение: The authorization server does not pass the access_token in the redirect_uri; it is returned in the authorization code or directly via the token endpoint.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The authorization server does not pass the access_token in the redirect_uri; it is returned in the authorization code or directly via the token endpoint." ⏎ } ⏎ ``` | неверно верный: «fragment» | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 0.11 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: The `default(2)` is used because `false` is considered falsy, so it defaults to 2 before multiplication.
Raw```json ⏎ { ⏎ "answer": 6, ⏎ "explanation": "The `default(2)` is used because `false` is considered falsy, so it defaults to 2 before multiplication." ⏎ } ⏎ ``` | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 0.11 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «null» Пояснение: The expression evaluates to a string, and render() in Twig for simple expressions generally does not throw an exception.
Raw```json ⏎ { ⏎ "answer": "null", ⏎ "explanation": "The expression evaluates to a string, and render() in Twig for simple expressions generally does not throw an exception." ⏎ } ⏎ ``` | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 0.1 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «1» Пояснение: The validator checks one empty string against a NotBlank constraint, resulting in one validation error.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "The validator checks one empty string against a NotBlank constraint, resulting in one validation error." ⏎ } ⏎ ``` | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 0.1 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «invalid» Пояснение: The TextType form is invalid by default because it has no data set to be valid.
Raw```json ⏎ { ⏎ "answer": "invalid", ⏎ "explanation": "The TextType form is invalid by default because it has no data set to be valid." ⏎ } ⏎ ``` | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 0.1 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: The code checks if the object ID of the retrieved service is the same as the object ID of the retrieved service, which will always be true.
Raw```json ⏎ { ⏎ "answer": "same", ⏎ "explanation": "The code checks if the object ID of the retrieved service is the same as the object ID of the retrieved service, which will always be true." ⏎ } ⏎ ``` | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 0.09 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob!» Пояснение: The code sets parameters and then retrieves the compiled parameter 'message'.
Raw```json ⏎ { ⏎ "answer": "hi Bob!", ⏎ "explanation": "The code sets parameters and then retrieves the compiled parameter 'message'." ⏎ } ⏎ ``` | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 0.13 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «1140px» Пояснение: The default max-width for .container in Bootstrap 5.3 is 1140px at the 992px breakpoint and above.
Raw```json ⏎ { ⏎ "answer": "1140px", ⏎ "explanation": "The default max-width for .container in Bootstrap 5.3 is 1140px at the 992px breakpoint and above." ⏎ } ⏎ ``` | неверно верный: «960» | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 0.09 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: The text-danger class sets the text color to the danger color in Bootstrap.
Raw```json ⏎ { ⏎ "answer": "text-danger", ⏎ "explanation": "The text-danger class sets the text color to the danger color in Bootstrap." ⏎ } ⏎ ``` | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 0.11 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «1» Пояснение: The dependency on App\Infrastructure\Db violates the rule that Infrastructure should only depend on Domain or Application.
Raw```json ⏎ { ⏎ "answer": 1, ⏎ "explanation": "The dependency on App\Infrastructure\Db violates the rule that Infrastructure should only depend on Domain or Application." ⏎ } ⏎ ``` | неверно верный: «2» | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 0.13 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «2» Пояснение: The Infrastructure layer depends on the Domain, and the Application layer depends on the Domain, but the Domain layer depends on another Domain (which is not shown, but the dependency is within the structure).
Raw```json ⏎ { ⏎ "answer": "2", ⏎ "explanation": "The Infrastructure layer depends on the Domain, and the Application layer depends on the Domain, but the Domain layer depends on another Domain (which is not shown, but the dependency is within the structure)." ⏎ } ⏎ ``` | неверно верный: «3» | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 0.1 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «15,15» Пояснение: The code calculates the sum of amounts and echoes the original and the result.
Raw```json ⏎ { ⏎ "answer": "15,15", ⏎ "explanation": "The code calculates the sum of amounts and echoes the original and the result." ⏎ } ⏎ ``` | неверно верный: «10,15» | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 0.08 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «0» Пояснение: The item 'a' is removed, and the count is then 0.
Raw```json ⏎ { ⏎ "answer": "0", ⏎ "explanation": "The item 'a' is removed, and the count is then 0." ⏎ } ⏎ ``` | неверно верный: «1» | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 2.59 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code creates an instance of class C and calls the hi method, which returns the string 'hi'.
Raw```json ⏎ { ⏎ "answer": "hi", ⏎ "explanation": "The code creates an instance of class C and calls the hi method, which returns the string 'hi'." ⏎ } ⏎ ``` | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 2.66 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class Heavy
{
public int $v = 0;
}
$r = new ReflectionClass(Heavy::class);
$o = $r->newLazyGhost(function (Heavy $obj) {
$obj->v = 21;
});
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
$o->v;
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
``` | «no» Пояснение: The lazy object is initialized when accessed, so isUninitializedLazyObject returns false.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The lazy object is initialized when accessed, so isUninitializedLazyObject returns false." ⏎ } ⏎ ``` | неверно верный: «yesno» | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 0.08 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «yes» Пояснение: The class exists in Symfony Security components in both versions.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The class exists in Symfony Security components in both versions." ⏎ } ⏎ ``` | неверно верный: «no» | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 0.09 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «yes» Пояснение: Both annotation and attribute class loaders exist in Symfony 8.1.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Both annotation and attribute class loaders exist in Symfony 8.1." ⏎ } ⏎ ``` | неверно верный: «noyes» | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |