Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 1.59 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings interpolate variables and process more escape sequences, while single-quoted strings do not.
Raw{"answer": "no", "explanation": "Double-quoted strings interpolate variables and process more escape sequences, while single-quoted strings do not."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.53 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator suppresses undefined-variable warnings and behaves like isset().
Raw{"answer":"yes","explanation":"The null coalescing operator suppresses undefined-variable warnings and behaves like isset()."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 1.26 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: echo outputs each argument consecutively, so 'a' and 'b' print as 'ab'.
Raw{"answer":"ab","explanation":"echo outputs each argument consecutively, so 'a' and 'b' print as 'ab'."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.7 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print is an expression that returns 1, so it can be used inside expressions.
Raw{"answer":"yes","explanation":"In PHP, print is an expression that returns 1, so it can be used inside expressions."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.57 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The elvis operator returns its left operand when it is truthy, not falsy.
Raw{"answer":"no","explanation":"The elvis operator returns its left operand when it is truthy, not falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.81 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction.
Raw{"answer":"yes","explanation":"In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 2.16 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: PHP's ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 512, not 64.
Raw{"answer":"no","explanation":"PHP's ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 2.56 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: In PHP 8, addition has higher precedence than concatenation, so 2 + 3 is evaluated first.
Raw{"answer":"sum: 5","explanation":"In PHP 8, addition has higher precedence than concatenation, so 2 + 3 is evaluated first."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.76 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: Strict array comparison requires the same key/value pairs in the same order and of the same types.
Raw{"answer":"no","explanation":"Strict array comparison requires the same key/value pairs in the same order and of the same types."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.55 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: In PHP, 0 == false is a loose comparison and evaluates to true, not false.
Raw{"answer":"no","explanation":"In PHP, 0 == false is a loose comparison and evaluates to true, not false."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.52 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, non-numeric strings are no longer converted to 0 when compared with numbers, so "abc" == 0 is false.
Raw{"answer":"no","explanation":"In PHP 8, non-numeric strings are no longer converted to 0 when compared with numbers, so \"abc\" == 0 is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 4.01 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP loose comparison, null == 0, null == "", and null == false all evaluate to true.
Raw{"answer":"yes","explanation":"In PHP loose comparison, null == 0, null == \"\", and null == false all evaluate to true."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 1.71 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP casts the leading numeric portion '42' to an integer and stops at the non-numeric character.
Raw{"answer": 42, "explanation": "PHP casts the leading numeric portion '42' to an integer and stops at the non-numeric character."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 1.36 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP coerces the numeric string '5' to an integer, so 5 + 5 equals 10.
Raw{"answer": 10, "explanation": "PHP coerces the numeric string '5' to an integer, so 5 + 5 equals 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.47 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: Casting false to string in PHP yields an empty string, not "0".
Raw{"answer":"no","explanation":"Casting false to string in PHP yields an empty string, not \"0\"."} | верно | false → "", true → "1". |
T02-L8 1.82 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 is not exactly equal to 0.3, so the strict comparison returns false.
Raw{"answer":"yes","explanation":"Due to floating-point precision, 0.1 + 0.2 is not exactly equal to 0.3, so the strict comparison returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.36 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses bytes, so it does not correctly reverse multibyte UTF-8 characters.
Raw{"answer": "no", "explanation": "strrev() reverses bytes, so it does not correctly reverse multibyte UTF-8 characters."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 1.36 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The substring 'world' occurs in 'Hello world', so str_contains returns true.
Raw{"answer":"yes","explanation":"The substring 'world' occurs in 'Hello world', so str_contains returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.41 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() supports STR_PAD_LEFT, STR_PAD_RIGHT, and STR_PAD_BOTH.
Raw{"answer":"no","explanation":"str_pad() supports STR_PAD_LEFT, STR_PAD_RIGHT, and STR_PAD_BOTH."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.47 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default trim() strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs.
Raw{"answer":"no","explanation":"By default trim() strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.77 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen() counts bytes, and é is two bytes in UTF-8, so h(1)+é(2)+l+l+o = 6.
Raw{"answer": 6, "explanation": "strlen() counts bytes, and é is two bytes in UTF-8, so h(1)+é(2)+l+l+o = 6."} | верно | 6 букв по 2 байта: 12. |
T03-L6 1.17 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: A negative start counts from the end of the string, so it returns the last three characters.
Raw{"answer":"def","explanation":"A negative start counts from the end of the string, so it returns the last three characters."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.03 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string and does not modify the original argument in place.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string and does not modify the original argument in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.55 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc interpolates variables, while nowdoc does not.
Raw{"answer": "yes", "explanation": "Heredoc interpolates variables, while nowdoc does not."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.67 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() reindexes the array numerically and does not preserve key-to-value associations.
Raw{"answer": "no", "explanation": "sort() reindexes the array numerically and does not preserve key-to-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.39 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: PHP casts numeric string array keys like '5' to integer keys.
Raw{"answer": "yes", "explanation": "PHP casts numeric string array keys like '5' to integer keys."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.39 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: By default in_array() uses loose comparison; strict comparison requires passing true as the third argument.
Raw{"answer":"no","explanation":"By default in_array() uses loose comparison; strict comparison requires passing true as the third argument."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.52 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() keeps only elements that are truthy, removing all falsy values.
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() keeps only elements that are truthy, removing all falsy values."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.69 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default array_slice() reindexes numeric keys; it preserves them only when preserve_keys is true.
Raw{"answer":"no","explanation":"By default array_slice() reindexes numeric keys; it preserves them only when preserve_keys is true."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 2.07 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice returns the two elements starting at index 1, namely 20 and 30.
Raw{"answer":"[20, 30]","explanation":"array_slice returns the two elements starting at index 1, namely 20 and 30."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.62 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The union operator keeps the left array's 'a' key and adds 'b', resulting in two elements.
Raw{"answer": 2, "explanation": "The union operator keeps the left array's 'a' key and adds 'b', resulting in two elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.75 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 added support for unpacking arrays with string keys using the spread operator.
Raw{"answer":"yes","explanation":"PHP 8.1 added support for unpacking arrays with string keys using the spread operator."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 4.79 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: PHP allows named arguments to be combined with argument unpacking in a single call, subject to ordering rules.
Raw{"answer":"no","explanation":"PHP allows named arguments to be combined with argument unpacking in a single call, subject to ordering rules."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.58 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: PHP closures do not capture outer-scope variables unless they are explicitly imported with use.
Raw{"answer":"no","explanation":"PHP closures do not capture outer-scope variables unless they are explicitly imported with use."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 1.59 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 total number of arguments passed to the function, including those beyond declared parameters.
Raw{"answer": 3, "explanation": "func_num_args() returns the total number of arguments passed to the function, including those beyond declared parameters."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.62 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: PHP arrow functions can only contain a single expression, not a brace-delimited block of multiple expressions.
Raw{"answer":"no","explanation":"PHP arrow functions can only contain a single expression, not a brace-delimited block of multiple expressions."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.44 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions capture outer variables by value automatically, not by reference.
Raw{"answer":"no","explanation":"PHP arrow functions capture outer variables by value automatically, not by reference."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 1.88 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static closure cannot be bound to an object, so it does not capture $this.
Raw{"answer":"yes","explanation":"A static closure cannot be bound to an object, so it does not capture $this."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.35 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure captures $x by value at definition time, so it retains 5.
Raw{"answer": 5, "explanation": "The closure captures $x by value at definition time, so it retains 5."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.39 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 coerces numeric strings like "5" to int for int parameters.
Raw{"answer": "yes", "explanation": "In weak typing mode, PHP coerces numeric strings like \"5\" to int for int parameters."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 1.32 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion was introduced in PHP 8.0 and allows declaring properties directly in the constructor parameters.
Raw{"answer":"yes","explanation":"Constructor property promotion was introduced in PHP 8.0 and allows declaring properties directly in the constructor parameters."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 1.52 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: Declaring a method final prevents subclasses from overriding it.
Raw{"answer": "final", "explanation": "Declaring a method final prevents subclasses from overriding it."} | верно | final. |
T06-L3 1.67 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, a final method cannot be overridden by a subclass.
Raw{"answer":"yes","explanation":"In PHP, a final method cannot be overridden by a subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 1.28 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private parent properties are not accessible in a subclass.
Raw{"answer": "no", "explanation": "Private parent properties are not accessible in a subclass."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 2.53 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@anonymous» Пояснение: PHP names anonymous classes with a generated name whose portion before the NUL byte is "class@anonymous".
Raw{"answer":"class@anonymous","explanation":"PHP names anonymous classes with a generated name whose portion before the NUL byte is \"class@anonymous\"."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 2.33 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. | «yes» Пояснение: Private methods are not inherited, so a child can declare a same-named method with any visibility.
Raw{"answer":"yes","explanation":"Private methods are not inherited, so a child can declare a same-named method with any visibility."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.92 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is also invoked when reading inaccessible (protected or private) properties, not only non-existent ones.
Raw{"answer":"no","explanation":"__get() is also invoked when reading inaccessible (protected or private) properties, not only non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.88 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning an initialized readonly property throws an Error, not an Exception.
Raw{"answer": "Error", "explanation": "Reassigning an initialized readonly property throws an Error, not an Exception."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 1.27 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces may declare constants, which implementing classes inherit.
Raw{"answer": "yes", "explanation": "PHP interfaces may declare constants, which implementing classes inherit."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 1.56 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator checks if an object is an instance of a class or interface.
Raw{"answer":"instanceof","explanation":"The instanceof operator checks if an object is an instance of a class or interface."} | верно | instanceof. |
T07-L3 1.83 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare static methods, which implementing classes must define as static.
Raw{"answer":"yes","explanation":"PHP interfaces can declare static methods, which implementing classes must define as static."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.19 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator also returns true for implemented interfaces, not just class inheritance.
Raw{"answer": "no", "explanation": "The instanceof operator also returns true for implemented interfaces, not just class inheritance."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.71 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: PHP interfaces only declare method signatures and cannot provide default implementations.
Raw{"answer":"no","explanation":"PHP interfaces only declare method signatures and cannot provide default implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.52 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: PHP allows abstract methods in abstract classes to have public or protected visibility, but not private.
Raw{"answer": "yes", "explanation": "PHP allows abstract methods in abstract classes to have public or protected visibility, but not private."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 1.55 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns an array containing all three enum cases.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array containing all three enum cases."} | верно | Статический метод cases(): 3. |
T07-L8 2.21 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: As of PHP 8.2, traits can declare constants.
Raw{"answer":"yes","explanation":"As of PHP 8.2, traits can declare constants."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 1.61 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP, Throwable is the base interface implemented by both Exception and Error.
Raw{"answer":"yes","explanation":"In PHP, Throwable is the base interface implemented by both Exception and Error."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.32 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError extends Error, not Exception, so a catch (Exception $e) block will not catch it.
Raw{"answer": "no", "explanation": "TypeError extends Error, not Exception, so a catch (Exception $e) block will not catch it."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.72 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator suppresses error messages, not exceptions.
Raw{"answer": "no", "explanation": "The @ operator suppresses error messages, not exceptions."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.61 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv() with a zero divisor throws a DivisionByZeroError in PHP.
Raw{"answer":"DivisionByZeroError","explanation":"intdiv() with a zero divisor throws a DivisionByZeroError in PHP."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.74 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: A finally block always runs, even if the exception is not caught.
Raw{"answer": "no", "explanation": "A finally block always runs, even if the exception is not caught."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.76 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 overrides any exception or return value from the try block, so it does affect the result.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block overrides any exception or return value from the try block, so it does affect the result."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.72 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: Casting any object to bool in PHP yields true.
Raw{"answer": "yes", "explanation": "Casting any object to bool in PHP yields true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.72 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Registered shutdown functions are executed when the script terminates, including when exit() or die() is called.
Raw{"answer":"yes","explanation":"Registered shutdown functions are executed when the script terminates, including when exit() or die() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.75 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: A use statement only imports/aliases a name; it does not autoload or include the class file.
Raw{"answer":"no","explanation":"A use statement only imports/aliases a name; it does not autoload or include the class file."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 1.39 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, functions are imported with the `use function` statement, while `use const` imports constants.
Raw{"answer": "function", "explanation": "In PHP, functions are imported with the `use function` statement, while `use const` imports constants."} | верно | use function ...; (и use const для констант). |
T09-L3 1.64 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: The PSR-4 prefix App\ maps to src/, so the remaining namespace becomes the subpath plus .php.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "The PSR-4 prefix App\\ maps to src/, so the remaining namespace becomes the subpath plus .php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 2.01 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php initializes and registers the generated autoloader with spl_autoload_register().
Raw{"answer":"yes","explanation":"Composer's vendor/autoload.php initializes and registers the generated autoloader with spl_autoload_register()."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 1.22 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: In PHP, __NAMESPACE__ evaluates to the name of the current namespace as a string.
Raw{"answer":"yes","explanation":"In PHP, __NAMESPACE__ evaluates to the name of the current namespace as a string."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.45 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: In a namespace, an unqualified class name in new resolves relative to the current namespace, not the global root.
Raw{"answer": "no", "explanation": "In a namespace, an unqualified class name in new resolves relative to the current namespace, not the global root."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.3 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» Пояснение: Under PSR-4, the namespace prefix App\ maps to src/, so App\Model\User corresponds to src/Model/User.php.
Raw{"answer": "yes", "explanation": "Under PSR-4, the namespace prefix App\\ maps to src/, so App\\Model\\User corresponds to src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 2.28 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: PHP namespace/class imports via use must be at the outermost scope, so block-scoped importing inside a function is not supported.
Raw{"answer":"no","explanation":"PHP namespace/class imports via use must be at the outermost scope, so block-scoped importing inside a function is not supported."} | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.89 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: PHP arrays have value semantics, so assignment copies the array (using copy-on-write) rather than passing it by reference.
Raw{"answer": "yes", "explanation": "PHP arrays have value semantics, so assignment copies the array (using copy-on-write) rather than passing it by reference."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.58 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are assigned by value, so appending to $b does not change $a.
Raw{"answer": 2, "explanation": "PHP arrays are assigned by value, so appending to $b does not change $a."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.61 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: PHP functions have local scope, so global variables require global, $GLOBALS, or parameters to be accessed.
Raw{"answer":"yes","explanation":"PHP functions have local scope, so global variables require global, $GLOBALS, or parameters to be accessed."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.96 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: Unsetting $GLOBALS['x'] removes the global variable from the global scope, not just within the function.
Raw{"answer":"no","explanation":"Unsetting $GLOBALS['x'] removes the global variable from the global scope, not just within the function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 1.68 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The parameter is passed by reference, so inc() increments $n to 6.
Raw{"answer": 6, "explanation": "The parameter is passed by reference, so inc() increments $n to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 3.17 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 by value iterates over a copy, so changes to the array inside the loop are not visible in the same pass.
Raw{"answer":"no","explanation":"A foreach by value iterates over a copy, so changes to the array inside the loop are not visible in the same pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 1.32 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 and are shared across all instances, so changes are visible in other objects.
Raw{"answer": "no", "explanation": "Static properties belong to the class and are shared across all instances, so changes are visible in other objects."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.47 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: Boolean array keys are cast to integers in PHP, so true becomes 1, not a boolean key.
Raw{"answer": "no", "explanation": "Boolean array keys are cast to integers in PHP, so true becomes 1, not a boolean key."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.26 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: A generator can return a value, which is retrieved with getReturn() after iteration completes.
Raw{"answer": "yes", "explanation": "A generator can return a value, which is retrieved with getReturn() after iteration completes."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.55 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: A PHP generator cannot be rewound after it has started or been fully consumed; calling rewind() then throws an exception.
Raw{"answer": "no", "explanation": "A PHP generator cannot be rewound after it has started or been fully consumed; calling rewind() then throws an exception."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.71 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: PHP's yield from delegates iteration to another generator or iterable.
Raw{"answer":"yes","explanation":"PHP's yield from delegates iteration to another generator or iterable."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.28 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: A function containing yield returns a Generator object, so get_class() reports its class name.
Raw{"answer":"Generator","explanation":"A function containing yield returns a Generator object, so get_class() reports its class name."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.46 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields the three elements 1, 2, and 3, so iterator_to_array produces an array with 3 elements.
Raw{"answer": 3, "explanation": "The generator yields the three elements 1, 2, and 3, so iterator_to_array produces an array with 3 elements."} | верно | yield from делегирует все 3 элемента. |
T11-L6 1.58 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack is a LIFO stack, not a FIFO queue.
Raw{"answer":"no","explanation":"SplStack is a LIFO stack, not a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 1.62 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator implements Iterator and can wrap an array for traversal.
Raw{"answer":"yes","explanation":"ArrayIterator implements Iterator and can wrap an array for traversal."} | верно | Объектная обёртка над массивом. |
T11-L8 1.46 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements IteratorAggregate, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements IteratorAggregate, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.4 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates a secure salt, so you do not need to provide one separately.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates a secure salt, so you do not need to provide one separately."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.54 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT uses bcrypt (not MD5) and handles salting automatically.
Raw{"answer":"no","explanation":"PASSWORD_DEFAULT uses bcrypt (not MD5) and handles salting automatically."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 1.89 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify returns true when the plaintext password matches the stored hash.
Raw{"answer": "yes", "explanation": "password_verify returns true when the plaintext password matches the stored hash."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.59 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags and does not prevent SQL injection, which requires proper escaping or prepared statements.
Raw{"answer":"no","explanation":"strip_tags() removes HTML/PHP tags and does not prevent SQL injection, which requires proper escaping or prepared statements."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.05 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: Regenerating the session ID on login prevents session fixation by giving the authenticated session a new ID.
Raw{"answer":"yes","explanation":"Regenerating the session ID on login prevents session fixation by giving the authenticated session a new ID."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.25 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: php_sapi_name() returns the current Server API name, such as cli.
Raw{"answer":"php_sapi_name","explanation":"php_sapi_name() returns the current Server API name, such as cli."} | верно | php_sapi_name(). |
T12-L7 1.81 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() removes server-side session data but does not delete the session cookie from the browser.
Raw{"answer": "yes", "explanation": "session_destroy() removes server-side session data but does not delete the session cookie from the browser."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.72 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: Session data is only populated after session_start() is called (or session auto-start is enabled).
Raw{"answer":"no","explanation":"Session data is only populated after session_start() is called (or session auto-start is enabled)."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 1.54 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «8.4» Пояснение: The array_find() function was introduced in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The array_find() function was introduced in PHP 8.4."} | верно | PHP 8.4 (RFC array_find). |
VC-L2 0.98 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks were introduced in PHP 8.4, allowing get and set logic directly in property declarations.
Raw{"answer": "yes", "explanation": "Property hooks were introduced in PHP 8.4, allowing get and set logic directly in property declarations."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.51 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced asymmetric property visibility, such as public private(set) string $name.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced asymmetric property visibility, such as public private(set) string $name."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 1.5 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.5» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.5.
Raw{"answer":"8.5","explanation":"The #[\NoDiscard] attribute was introduced in PHP 8.5."} | верно | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 1.22 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.5» Пояснение: The pipe operator |> was introduced in PHP 8.5.
Raw{"answer":"8.5","explanation":"The pipe operator |> was introduced in PHP 8.5."} | верно | Pipe operator — PHP 8.5 (2025). |
VC-L6 4.82 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. | «8.5» Пояснение: The clone-with syntax was introduced in PHP 8.5.
Raw{"answer":"8.5","explanation":"The clone-with syntax was introduced in PHP 8.5."} | верно | Clone with v2 — PHP 8.5. |
VC-L7 1.4 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.5» Пояснение: The array_first() and array_last() functions were introduced in PHP 8.5.
Raw{"answer": "8.5", "explanation": "The array_first() and array_last() functions were introduced in PHP 8.5."} | верно | PHP 8.5. |
VC-L8 8.72 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. | «8.6» Пояснение: RFC Partial Function Application v2 was adopted for PHP 8.6.
Raw{"answer":"8.6","explanation":"RFC Partial Function Application v2 was adopted for PHP 8.6."} | верно | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 3.46 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. | «8.5» Пояснение: The clamp_v2 RFC was implemented in PHP 8.5.
Raw{"answer":"8.5","explanation":"The clamp_v2 RFC was implemented in PHP 8.5."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 3.83 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: No PHP RFC named Context Managers v2 has been adopted; the stated date is also in the future.
Raw{"answer":"no","explanation":"No PHP RFC named Context Managers v2 has been adopted; the stated date is also in the future."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 9.55 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: The Bound-Erased Generic Types RFC was declined in 2026.
Raw{"answer":"yes","explanation":"The Bound-Erased Generic Types RFC was declined in 2026."} | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 5.25 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» Пояснение: No PHP RFC making ZTS (thread safety) the default build has been accepted as of 2026-11-07.
Raw{"answer":"no","explanation":"No PHP RFC making ZTS (thread safety) the default build has been accepted as of 2026-11-07."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.43 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 still does not support native generics/parameterized types.
Raw{"answer":"yes","explanation":"PHP 8.5 still does not support native generics/parameterized types."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 1.7 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). | «yes» Пояснение: PHP 8.6's GA date is after 2026-11-07, so the latest stable release on that date is PHP 8.5.
Raw{"answer":"yes","explanation":"PHP 8.6's GA date is after 2026-11-07, so the latest stable release on that date is PHP 8.5."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.75 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 6 was developed but never released, and PHP 7.0 followed PHP 5.6.
Raw{"answer":"yes","explanation":"PHP 6 was developed but never released, and PHP 7.0 followed PHP 5.6."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 2.19 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «yes» Пояснение: The RFC for the core #[\Deprecated] attribute was adopted and implemented in PHP 8.4.
Raw{"answer":"yes","explanation":"The RFC for the core #[\Deprecated] attribute was adopted and implemented in PHP 8.4."} | верно | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.42 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In clean and onion architecture, dependencies point inward, so inner layers know nothing about outer layers.
Raw{"answer": "yes", "explanation": "In clean and onion architecture, dependencies point inward, so inner layers know nothing about outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.82 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities should remain framework-agnostic, depending only on the language and possibly the standard library.
Raw{"answer": "yes", "explanation": "Domain entities should remain framework-agnostic, depending only on the language and possibly the standard library."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.63 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation/interface layer, not the business-logic layer, even if controllers invoke use cases.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation/interface layer, not the business-logic layer, even if controllers invoke use cases."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.6 c | Clean architecture | What sits at the very center of the onion architecture? | «the domain model» Пояснение: In onion architecture, the domain model (entities/business rules) sits at the center, with dependencies pointing inward.
Raw{"answer": "The domain model", "explanation": "In onion architecture, the domain model (entities/business rules) sits at the center, with dependencies pointing inward."} | верно | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.75 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Tools like deptrac statically analyze dependencies and can fail builds when a forbidden layer call is detected.
Raw{"answer": "yes", "explanation": "Tools like deptrac statically analyze dependencies and can fail builds when a forbidden layer call is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.09 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: Use cases should not depend on framework-specific HTTP requests or ORM EntityManagers; that couples business logic to infrastructure.
Raw{"answer":"no","explanation":"Use cases should not depend on framework-specific HTTP requests or ORM EntityManagers; that couples business logic to infrastructure."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.44 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 provides collection-like access to aggregates while encapsulating persistence behind an interface.
Raw{"answer": "Repository", "explanation": "A repository provides collection-like access to aggregates while encapsulating persistence behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.25 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In clean architecture, database details belong to the outer layer, so replacing PostgreSQL should not affect domain or use-case code.
Raw{"answer":"yes","explanation":"In clean architecture, database details belong to the outer layer, so replacing PostgreSQL should not affect domain or use-case code."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.33 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a consistency boundary around domain objects, not a database table.
Raw{"answer": "no", "explanation": "An aggregate is a consistency boundary around domain objects, not a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.66 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are immutable and equality is based on their field values rather than object identity.
Raw{"answer": "yes", "explanation": "Value Objects are immutable and equality is based on their field values rather than object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 1.65 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In domain-driven design, the aggregate root is the only external entry point through which all changes to an aggregate must pass.
Raw{"answer": "aggregate root", "explanation": "In domain-driven design, the aggregate root is the only external entry point through which all changes to an aggregate must pass."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.45 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: A repository is defined for an aggregate root, not for every entity within the aggregate.
Raw{"answer": "yes", "explanation": "A repository is defined for an aggregate root, not for every entity within the aggregate."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.53 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous language is a shared domain language used by developers and domain experts.
Raw{"answer":"yes","explanation":"Ubiquitous language is a shared domain language used by developers and domain experts."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 2.36 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «universe of discourse» Пояснение: The boundary within which a model and its language remain consistent is called the universe of discourse.
Raw{"answer":"universe of discourse","explanation":"The boundary within which a model and its language remain consistent is called the universe of discourse."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.43 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends rich domain models, not anemic ones with logic in services.
Raw{"answer": "no", "explanation": "DDD recommends rich domain models, not anemic ones with logic in services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.42 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: A bounded context defines a model boundary, so the same real-world concept can be modeled as distinct classes in different contexts.
Raw{"answer": "yes", "explanation": "A bounded context defines a model boundary, so the same real-world concept can be modeled as distinct classes in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.93 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «no» Пояснение: Symfony services are not lazy by default; they are instantiated when fetched from the container unless marked lazy.
Raw{"answer":"no","explanation":"Symfony services are not lazy by default; they are instantiated when fetched from the container unless marked lazy."} | неверно верный: «yes» | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 1.35 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command debug:router lists all registered routes.
Raw{"answer": "debug:router", "explanation": "The Symfony console command debug:router lists all registered routes."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.7 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring lets services be registered automatically via resource loading and autoconfigure, so you don't need to declare every service manually.
Raw{"answer": "no", "explanation": "Symfony autowiring lets services be registered automatically via resource loading and autoconfigure, so you don't need to declare every service manually."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.58 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes and caches them between requests.
Raw{"answer":"yes","explanation":"Twig compiles templates into PHP classes and caches them between requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 2.14 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: Symfony caches the dev container and rebuilds it only when tracked resource files change, not on every request.
Raw{"answer": "yes", "explanation": "Symfony caches the dev container and rebuilds it only when tracked resource files change, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 1.6 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: Symfony reads the active environment from the APP_ENV environment variable.
Raw{"answer":"APP_ENV","explanation":"Symfony reads the active environment from the APP_ENV environment variable."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 2.63 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony controller methods used by routes must be public; private methods are not callable by the controller resolver.
Raw{"answer":"no","explanation":"Symfony controller methods used by routes must be public; private methods are not callable by the controller resolver."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 1.95 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Event subscribers are not automatically prioritized over listeners; ordering depends on registered priority values.
Raw{"answer": "no", "explanation": "Event subscribers are not automatically prioritized over listeners; ordering depends on registered priority values."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.97 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» Пояснение: Symfony 6.0 removed the old Guard authentication system in favor of authenticator classes implementing AuthenticatorInterface.
Raw{"answer":"yes","explanation":"Symfony 6.0 removed the old Guard authentication system in favor of authenticator classes implementing AuthenticatorInterface."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.82 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute enforces role or permission checks on a controller method and returns 403 if not granted.
Raw{"answer":"IsGranted","explanation":"The #[IsGranted] attribute enforces role or permission checks on a controller method and returns 403 if not granted."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.57 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony voters are used by isGranted() to decide whether access to a specific object is granted.
Raw{"answer":"yes","explanation":"Symfony voters are used by isGranted() to decide whether access to a specific object is granted."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 1.8 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» Пояснение: Symfony 7 removed support for Doctrine-style annotations, so validation constraints must use PHP attributes.
Raw{"answer": "yes", "explanation": "Symfony 7 removed support for Doctrine-style annotations, so validation constraints must use PHP attributes."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 1.65 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms enable CSRF protection by default and validate the token on submission.
Raw{"answer": "yes", "explanation": "Symfony forms enable CSRF protection by default and validate the token on submission."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.67 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony form validation always runs server-side; HTML5 client checks are only a convenience and can be bypassed.
Raw{"answer": "yes", "explanation": "Symfony form validation always runs server-side; HTML5 client checks are only a convenience and can be bypassed."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 1.65 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command make:form generates a FormType class.
Raw{"answer":"make:form","explanation":"The Symfony MakerBundle command make:form generates a FormType class."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.51 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony does not store the user's plain-text password in the session; authentication state is tracked without exposing the password.
Raw{"answer": "no", "explanation": "Symfony does not store the user's plain-text password in the session; authentication state is tracked without exposing the password."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.25 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: Symfony recommends placing bundle configuration in config/packages, typically with one file per bundle or topic.
Raw{"answer":"yes","explanation":"Symfony recommends placing bundle configuration in config/packages, typically with one file per bundle or topic."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 1.66 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. | «yes» Пояснение: This matches Symfony's convention: .env is committed with defaults, while .env.local is ignored and holds local secrets.
Raw{"answer": "yes", "explanation": "This matches Symfony's convention: .env is committed with defaults, while .env.local is ignored and holds local secrets."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 1.54 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The debug:container command lists registered services and their aliases in the Symfony container.
Raw{"answer":"debug:container","explanation":"The debug:container command lists registered services and their aliases in the Symfony container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 3.07 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: In a compiled Symfony container, parameters are immutable, so setParameter() throws a LogicException at runtime.
Raw{"answer": "no", "explanation": "In a compiled Symfony container, parameters are immutable, so setParameter() throws a LogicException at runtime."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 1.56 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, not public, so they cannot be fetched directly from the container.
Raw{"answer": "no", "explanation": "By default, Symfony services are private, not public, so they cannot be fetched directly from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.55 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Bundles can work with default configuration and do not require a config file in config/packages.
Raw{"answer": "no", "explanation": "Bundles can work with default configuration and do not require a config file in config/packages."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 1.83 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: Symfony supports referencing environment variables in services.yaml using the %env(VAR)% syntax.
Raw{"answer": "yes", "explanation": "Symfony supports referencing environment variables in services.yaml using the %env(VAR)% syntax."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.41 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: Symfony uses the APP_DEBUG environment variable to enable debug mode, which activates the profiler and Twig debugging.
Raw{"answer":"APP_DEBUG","explanation":"Symfony uses the APP_DEBUG environment variable to enable debug mode, which activates the profiler and Twig debugging."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 2.41 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows multiple handlers for the same message, and all matching handlers are called.
Raw{"answer":"no","explanation":"Symfony Messenger allows multiple handlers for the same message, and all matching handlers are called."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.48 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport handles the message immediately in the current process, unlike async transports that queue messages for a worker.
Raw{"answer": "no", "explanation": "The sync transport handles the message immediately in the current process, unlike async transports that queue messages for a worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 1.45 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: The Symfony Messenger worker is started with the messenger:consume command.
Raw{"answer":"messenger:consume","explanation":"The Symfony Messenger worker is started with the messenger:consume command."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.6 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, retry_strategy is configured per transport under the messenger transports configuration.
Raw{"answer":"yes","explanation":"In Symfony Messenger, retry_strategy is configured per transport under the messenger transports configuration."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.64 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «no» Пояснение: Symfony Messenger uses the PHP serializer by default, not JSON.
Raw{"answer": "no", "explanation": "Symfony Messenger uses the PHP serializer by default, not JSON."} | верно | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 1.26 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler generates messages according to a schedule and dispatches them via Messenger.
Raw{"answer": "yes", "explanation": "Symfony Scheduler generates messages according to a schedule and dispatches them via Messenger."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.64 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: The Doctrine transport stores Messenger messages in database tables via Doctrine DBAL.
Raw{"answer": "Doctrine", "explanation": "The Doctrine transport stores Messenger messages in database tables via Doctrine DBAL."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.34 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger allows custom middleware to be added to the bus middleware chain, including before or after built-in middleware.
Raw{"answer": "yes", "explanation": "Symfony Messenger allows custom middleware to be added to the bus middleware chain, including before or after built-in middleware."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 1.69 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a two-year major release cycle and six-month minor releases in May and November.
Raw{"answer":"yes","explanation":"Symfony follows a two-year major release cycle and six-month minor releases in May and November."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.17 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires PHP 8.4 as its minimum supported version.
Raw{"answer":"8.4","explanation":"Symfony 8 requires PHP 8.4 as its minimum supported version."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.72 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations; attributes are required.
Raw{"answer":"no","explanation":"Symfony 7.0 removed support for docblock annotations; attributes are required."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.35 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper uses importmap.php to manage CSS/JS assets without requiring Node.js or Webpack.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper uses importmap.php to manage CSS/JS assets without requiring Node.js or Webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.67 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is a long-term support (LTS) release, not a regular release.
Raw{"answer":"no","explanation":"Symfony 6.4 is a long-term support (LTS) release, not a regular release."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.43 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» Пояснение: Symfony major releases remove deprecations introduced in the previous major branch, so they do not keep working.
Raw{"answer": "no", "explanation": "Symfony major releases remove deprecations introduced in the previous major branch, so they do not keep working."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.75 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony publishes UPGRADE guides for each major release documenting backward-incompatible changes.
Raw{"answer":"yes","explanation":"Symfony publishes UPGRADE guides for each major release documenting backward-incompatible changes."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.42 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component manages assets and importmaps without Node.js or Webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component manages assets and importmaps without Node.js or Webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 3.04 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony 8.2 is scheduled for release in November 2026, typically late in the month, so it would not yet be released on 2026-11-07.
Raw{"answer":"no","explanation":"Symfony 8.2 is scheduled for release in November 2026, typically late in the month, so it would not yet be released on 2026-11-07."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 2.44 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. | «yes» Пояснение: Symfony follows a six-month minor release cycle, so after 8.0 in November 2025 and 8.1 in May 2026, 8.2 is scheduled for November 2026.
Raw{"answer":"yes","explanation":"Symfony follows a six-month minor release cycle, so after 8.0 in November 2025 and 8.1 in May 2026, 8.2 is scheduled for November 2026."} | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 2.71 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony follows a six-month minor release cycle, so the release after 8.1 is 8.2.
Raw{"answer":"8.2","explanation":"Symfony follows a six-month minor release cycle, so the release after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 1.67 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 would be a minor release, not a major release requiring applications to be rewritten.
Raw{"answer": "no", "explanation": "Symfony 8.2 would be a minor release, not a major release requiring applications to be rewritten."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 2.47 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP minor releases generally preserve backward compatibility, though deprecations may encourage future changes.
Raw{"answer":"yes","explanation":"PHP minor releases generally preserve backward compatibility, though deprecations may encourage future changes."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 3.02 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony 8.4 is the final minor release in the 8.x branch before Symfony 9.0.
Raw{"answer":"8.4","explanation":"Symfony 8.4 is the final minor release in 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 3.47 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 minor releases generally keep the same PHP requirement as the major release, so Symfony 8.2 is expected to require PHP 8.4, not PHP 8.5.
Raw{"answer":"no","explanation":"Symfony minor releases generally keep the same PHP requirement as the major release, so Symfony 8.2 is expected to require PHP 8.4, not PHP 8.5."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 1.94 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony deprecations introduced in 8.x are only removed in the next major version, 9.0.
Raw{"answer": "yes", "explanation": "Symfony deprecations introduced in 8.x are only removed in the next major version, 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.17 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig expressions cannot call arbitrary PHP directly; only exposed functions, filters, and variables are available.
Raw{"answer": "no", "explanation": "Twig expressions cannot call arbitrary PHP directly; only exposed functions, filters, and variables are available."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 2.0 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig enables autoescaping by default, escaping printed variables for HTML context.
Raw{"answer":"yes","explanation":"Twig enables autoescaping by default, escaping printed variables for HTML context."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.57 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: Twig's |e filter escapes output for HTML by default, making it safe in HTML contexts.
Raw{"answer": "yes", "explanation": "Twig's |e filter escapes output for HTML by default, making it safe in HTML contexts."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 2.1 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «format_number» Пояснение: The format_number filter formats a number according to the given locale.
Raw{"answer":"format_number","explanation":"The format_number filter formats a number according to the given locale."} | верно | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.57 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter marks a value as safe so Twig does not auto-escape it.
Raw{"answer":"yes","explanation":"The |raw filter marks a value as safe so Twig does not auto-escape it."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.58 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: Twig uses {{ }} for outputting expression values and {% %} for executing tags such as conditions, loops, and assignments.
Raw{"answer": "yes", "explanation": "Twig uses {{ }} for outputting expression values and {% %} for executing tags such as conditions, loops, and assignments."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.25 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows declaring variables in templates using the set tag, not only via the controller.
Raw{"answer": "no", "explanation": "Twig allows declaring variables in templates using the set tag, not only via the controller."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 1.19 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: Twig's dump() function outputs the debug structure of a variable when debug is enabled.
Raw{"answer": "dump", "explanation": "Twig's dump() function outputs the debug structure of a variable when debug is enabled."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.6 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap provides ready-made CSS and JavaScript UI components and is not a single-page application framework.
Raw{"answer":"yes","explanation":"Bootstrap provides ready-made CSS and JavaScript UI components and is not a single-page application framework."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.33 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: Bootstrap's .container sets a responsive fixed max-width at each breakpoint.
Raw{"answer": "container", "explanation": "Bootstrap's .container sets a responsive fixed max-width at each breakpoint."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.76 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: Bootstrap's grid uses 12 columns, not 16, and newer versions use flexbox rather than floats.
Raw{"answer":"no","explanation":"Bootstrap's grid uses 12 columns, not 16, and newer versions use flexbox rather than floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.21 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap 5 defines five named breakpoint infixes: sm, md, lg, xl, and xxl.
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines five named breakpoint infixes: sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 2.18 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: Bootstrap's spacing utilities map each number to a value in the $spacers scale, which is defined as multiples (or fractions) of $spacer.
Raw{"answer":"yes","explanation":"Bootstrap's spacing utilities map each number to a value in the $spacers scale, which is defined as multiples (or fractions) of $spacer."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 1.67 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: Bootstrap 5 uses data-bs-toggle to initialize interactive components like dropdowns.
Raw{"answer": "data-bs-toggle", "explanation": "Bootstrap 5 uses data-bs-toggle to initialize interactive components like dropdowns."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 1.77 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 components are implemented in vanilla JavaScript and do not require jQuery.
Raw{"answer": "yes", "explanation": "Bootstrap 5 components are implemented in vanilla JavaScript and do not require jQuery."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.69 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: Bootstrap 5.3 enables dark mode with the data-bs-theme="dark" attribute on the root element, not a .dark class.
Raw{"answer":"no","explanation":"Bootstrap 5.3 enables dark mode with the data-bs-theme=\"dark\" attribute on the root element, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.3 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not create tables automatically at runtime; schema creation is done explicitly via tools or migrations.
Raw{"answer":"no","explanation":"Doctrine ORM does not create tables automatically at runtime; schema creation is done explicitly via tools or migrations."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.53 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() schedules a new entity for insertion and defers SQL until flush().
Raw{"answer": "persist", "explanation": "EntityManager::persist() schedules a new entity for insertion and defers SQL until flush()."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.38 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: EntityManager::merge() was deprecated in Doctrine ORM 2.x and removed in ORM 3.0.
Raw{"answer": "no", "explanation": "EntityManager::merge() was deprecated in Doctrine ORM 2.x and removed in ORM 3.0."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.72 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL is written using entity names and their mapped fields rather than database table and column names.
Raw{"answer":"yes","explanation":"DQL is written using entity names and their mapped fields rather than database table and column names."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 1.58 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: Doctrine's find() returns null when no matching record exists.
Raw{"answer": "null", "explanation": "Doctrine's find() returns null when no matching record exists."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 1.61 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle does not automatically call flush() at the end of each request; you must flush explicitly.
Raw{"answer":"no","explanation":"DoctrineBundle does not automatically call flush() at the end of each request; you must flush explicitly."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.6 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. | «yes» Пояснение: Doctrine's Unit of Work tracks changes to managed entities, so flush() updates them without an explicit persist().
Raw{"answer": "yes", "explanation": "Doctrine's Unit of Work tracks changes to managed entities, so flush() updates them without an explicit persist()."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.71 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: remove() only marks the entity for deletion; the SQL DELETE is executed on flush().
Raw{"answer": "no", "explanation": "remove() only marks the entity for deletion; the SQL DELETE is executed on flush()."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.37 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC allows readers and writers to operate concurrently without blocking each other.
Raw{"answer":"no","explanation":"PostgreSQL's MVCC allows readers and writers to operate concurrently without blocking each other."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.73 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: EXPLAIN displays the execution plan without running the query (in databases like MySQL and PostgreSQL).
Raw{"answer": "EXPLAIN", "explanation": "EXPLAIN displays the execution plan without running the query (in databases like MySQL and PostgreSQL)."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 1.97 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is a PostgreSQL pseudo-type using a sequence default, while GENERATED ... AS IDENTITY is the SQL-standard identity mechanism with different semantics.
Raw{"answer":"no","explanation":"SERIAL is a PostgreSQL pseudo-type using a sequence default, while GENERATED ... AS IDENTITY is the SQL-standard identity mechanism with different semantics."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.7 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default PostgreSQL UNIQUE constraints treat NULLs as distinct, so multiple rows with NULL are allowed.
Raw{"answer": "no", "explanation": "By default PostgreSQL UNIQUE constraints treat NULLs as distinct, so multiple rows with NULL are allowed."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 1.24 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg aggregate concatenates string values using a specified separator.
Raw{"answer":"string_agg","explanation":"PostgreSQL's string_agg aggregate concatenates string values using a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.61 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM marks space from dead tuples as reusable inside the database but does not return it to the operating system; VACUUM FULL does.
Raw{"answer":"no","explanation":"Plain VACUUM marks space from dead tuples as reusable inside the database but does not return it to the operating system; VACUUM FULL does."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 1.49 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause divides rows into groups over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause divides rows into groups over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.53 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED prevents dirty reads but allows non-repeatable reads because each statement sees a new snapshot.
Raw{"answer":"no","explanation":"READ COMMITTED prevents dirty reads but allows non-repeatable reads because each statement sees a new snapshot."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.57 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL runs each SQL statement in its own implicit transaction unless you explicitly start a transaction block.
Raw{"answer": "yes", "explanation": "PostgreSQL runs each SQL statement in its own implicit transaction unless you explicitly start a transaction block."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 1.52 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT command permanently saves all changes made during the current transaction.
Raw{"answer": "COMMIT", "explanation": "The COMMIT command permanently saves all changes made during the current transaction."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.24 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 can also speed up UPDATE and DELETE statements that use an indexed column in their search condition.
Raw{"answer":"yes","explanation":"Indexes can also speed up UPDATE and DELETE statements that use an indexed column in their search condition."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.64 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: PostgreSQL uses SAVEPOINT to roll back part of a transaction to a marked point.
Raw{"answer": "yes", "explanation": "PostgreSQL uses SAVEPOINT to roll back part of a transaction to a marked point."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.34 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query and reports runtime statistics.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query and reports runtime statistics."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 1.73 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: The pgvector extension adds vector data types and vector indexes for embedding similarity search in PostgreSQL.
Raw{"answer":"pgvector","explanation":"The pgvector extension adds vector data types and vector indexes for embedding similarity search in PostgreSQL."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.63 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index includes only table rows that satisfy its WHERE predicate.
Raw{"answer": "yes", "explanation": "A partial index includes only table rows that satisfy its WHERE predicate."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.75 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation with predicate locks, not by locking the rows a transaction reads.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation with predicate locks, not by locking the rows a transaction reads."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 1.2 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 Created indicates that the request successfully resulted in a new resource being created.
Raw{"answer":"yes","explanation":"HTTP 201 Created indicates that the request successfully resulted in a new resource being created."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.45 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 No Content indicates a successful request with no response body.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with no response body."} | верно | 204 No Content; RFC 9110. |
T19-L3 1.42 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. | «yes» Пояснение: DELETE is idempotent because repeating the same request leaves the resource in the same final state.
Raw{"answer": "yes", "explanation": "DELETE is idempotent because repeating the same request leaves the resource in the same final state."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.43 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, not the client, to indicate allowed origins.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server, not the client, to indicate allowed origins."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 1.43 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 Too Many Requests indicates the client has exceeded a rate limit.
Raw{"answer":"yes","explanation":"HTTP 429 Too Many Requests indicates the client has exceeded a rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 1.32 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It is the reverse: 4xx codes indicate client errors and 5xx codes indicate server-side errors.
Raw{"answer":"no","explanation":"It is the reverse: 4xx codes indicate client errors and 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 1.15 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 MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.5 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 states PATCH is not necessarily idempotent, whereas PUT is idempotent.
Raw{"answer": "yes", "explanation": "RFC 5789 states PATCH is not necessarily idempotent, whereas PUT is idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.46 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Use hash_equals for constant-time comparison, since == is vulnerable to timing attacks and type juggling.
Raw{"answer": "no", "explanation": "Use hash_equals for constant-time comparison, since == is vulnerable to timing attacks and type juggling."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.41 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 typically session-bound and checked server-side for state-changing requests such as POST.
Raw{"answer":"yes","explanation":"CSRF tokens are typically session-bound and checked server-side for state-changing requests such as POST."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 1.45 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The CSP policy is delivered via the Content-Security-Policy HTTP response header.
Raw{"answer":"Content-Security-Policy","explanation":"The CSP policy is delivered via the Content-Security-Policy HTTP response header."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.55 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, and an access token grants access rather than identifying the user.
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization framework, and an access token grants access rather than identifying the user."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.7 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is prevented mainly by escaping output at render time, not by validating input before database storage.
Raw{"answer":"no","explanation":"XSS is prevented mainly by escaping output at render time, not by validating input before database storage."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.65 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? | «code» Пояснение: The authorization server redirects back with an authorization code that the client exchanges for an access token.
Raw{"answer":"code","explanation":"The authorization server redirects back with an authorization code that the client exchanges for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.3 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 credentials used to obtain new access tokens without requiring the user to log in again.
Raw{"answer":"yes","explanation":"Refresh tokens are long-lived credentials used to obtain new access tokens without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.64 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt does not need to be secret; it is stored alongside the hash and is required to verify it, but secrecy is not required.
Raw{"answer": "no", "explanation": "A salt does not need to be secret; it is stored alongside the hash and is required to verify it, but secrecy is not required."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 4.36 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit test classes must extend PHPUnit\Framework\TestCase (or implement the Test interface) for its test methods to be discovered and run.
Raw{"answer":"no","explanation":"PHPUnit test classes must extend PHPUnit\\Framework\\TestCase (or implement the Test interface) for its test methods to be discovered and run."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 1.47 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method, while setUpBeforeClass() runs once before all tests.
Raw{"answer":"no","explanation":"setUp() runs before each test method, while setUpBeforeClass() runs once before all tests."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.41 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider can supply multiple sets of arguments, causing the test to run once per set.
Raw{"answer": "no", "explanation": "A data provider can supply multiple sets of arguments, causing the test to run once per set."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 1.62 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method declares that a specified exception class is expected to be thrown.
Raw{"answer":"expectException","explanation":"PHPUnit's expectException() method declares that a specified exception class is expected to be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.36 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It is reversed: stubs return canned data, while mocks can verify method calls and expectations.
Raw{"answer": "no", "explanation": "It is reversed: stubs return canned data, while mocks can verify method calls and expectations."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 1.06 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» Пояснение: PHPUnit 10+ recommends the #[DataProvider] attribute, while the @dataProvider annotation is deprecated.
Raw{"answer":"yes","explanation":"PHPUnit 10+ recommends the #[DataProvider] attribute, while the @dataProvider annotation is deprecated."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.43 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit allows tests to depend on other tests using the @depends annotation.
Raw{"answer":"no","explanation":"PHPUnit allows tests to depend on other tests using the @depends annotation."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.74 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--order-by=random» Пояснение: PHPUnit's --order-by=random option runs tests in a random order.
Raw{"answer":"--order-by=random","explanation":"PHPUnit's --order-by=random option runs tests in a random order."} | верно | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 1.56 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) is 3 and intdiv(-7,2) is -3, so concatenation produces "3-3".
Raw{"answer":"3-3","explanation":"intdiv(7,2) is 3 and intdiv(-7,2) is -3, so concatenation produces \"3-3\"."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.67 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, exponentiation has higher precedence than unary minus, so it evaluates as -(3 ** 2) = -9.
Raw{"answer": -9, "explanation": "In PHP, exponentiation has higher precedence than unary minus, so it evaluates as -(3 ** 2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 1.76 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both strings are numeric, so PHP compares them numerically: 1e1 equals 10.
Raw{"answer":"true","explanation":"Both strings are numeric, so PHP compares them numerically: 1e1 equals 10."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 1.82 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: In PHP 8, 'a' does not loosely equal 0, so the default branch runs and prints 'other'.
Raw{"answer":"other","explanation":"In PHP 8, 'a' does not loosely equal 0, so the default branch runs and prints 'other'."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 1.58 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr() with an array replaces the longest matching substring first, so 'ab' becomes '2' and 'c' remains.
Raw{"answer":"2c","explanation":"strtr() with an array replaces the longest matching substring first, so 'ab' becomes '2' and 'c' remains."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 2.75 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: A negative start beyond the string length is treated as 0, so substr returns the whole string.
Raw{"answer":"[hello]","explanation":"A negative start beyond the string length is treated as 0, so substr returns the whole string."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.34 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,n,m» Пояснение: The array union preserves keys from the left array and adds non-conflicting keys from the right, so array_keys() returns k, n, m.
Raw{"answer":"k,n,m","explanation":"The array union preserves keys from the left array and adds non-conflicting keys from the right, so array_keys() returns k, n, m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.4 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));
``` | «yxz» Пояснение: Sorting by the third element puts 'y' first, then the two equal-key elements 'x' and 'z' in stable order.
Raw{"answer":"yxz","explanation":"Sorting by the third element puts 'y' first, then the two equal-key elements 'x' and 'z' in stable order."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 3.17 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]);
``` | «4» Пояснение: The associative array is unpacked as named arguments, so $a=5 and $b=1, returning 4.
Raw{"answer": 4, "explanation": "The associative array is unpacked as named arguments, so $a=5 and $b=1, returning 4."} | верно | String keys of a spread array become named arguments. |
T05-L9 2.06 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();
``` | «3» Пояснение: The first-class callable closure keeps the object alive and calls g(), returning the private property value 3.
Raw{"answer": 3, "explanation": "The first-class callable closure keeps the object alive and calls g(), returning the private property value 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.62 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» Пояснение: static::class uses late static binding, so it resolves to the runtime class B.
Raw{"answer":"B","explanation":"static::class uses late static binding, so it resolves to the runtime class B."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 11.57 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 set hook writes $value * 2 (5 * 2) to the property's backing value, so reading $c->x returns 10.
Raw{"answer": 10, "explanation": "The set hook writes $value * 2 (5 * 2) to the property's backing value, so reading $c->x returns 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 2.04 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» Пояснение: TB::f is used as f and TA::f is aliased to g, so concatenating returns 'B' . 'A' = 'BA'.
Raw{"answer":"BA","explanation":"TB::f is used as f and TA::f is aliased to g, so concatenating returns 'B' . 'A' = 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.68 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;
``` | «0» Пояснение: Each class using the trait gets its own separate copy of the static property, so CY::$n remains 0.
Raw{"answer": 0, "explanation": "Each class using the trait gets its own separate copy of the static property, so CY::$n remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 2.58 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: A return in the finally block overrides the return value from the try block.
Raw{"answer": 2, "explanation": "A return in the finally block overrides the return value from the try block."} | верно | A return in finally overrides the return from try. |
T08-L9 1.95 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 overrides the RuntimeException and is caught by the outer catch, so getMessage() outputs "second".
Raw{"answer":"second","explanation":"The LogicException thrown in the finally block overrides the RuntimeException and is caught by the outer catch, so getMessage() outputs \"second\"."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 2.12 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: The imported alias Baz resolves to App\Foo, while \Baz::class is the fully qualified global name Baz.
Raw{"answer":"App\\Foo|Baz","explanation":"The imported alias Baz resolves to App\\Foo, while \\Baz::class is the fully qualified global name Baz."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 4.4 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');
``` | «noyes» Пояснение: class_exists('Foo') checks the global Foo class, while class_exists('Ns\Foo') finds the namespaced class.
Raw{"answer":"noyes","explanation":"class_exists('Foo') checks the global Foo class, while class_exists('Ns\\Foo') finds the namespaced class."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.46 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,99» Пояснение: After the by-reference foreach, $v still references the last element, so assigning 99 changes $a[2].
Raw{"answer":"1,2,99","explanation":"After the by-reference foreach, $v still references the last element, so assigning 99 changes $a[2]."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 16.21 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();
``` | «3» Пояснение: In PHP 8.1+ the inherited method shares its static $n between A and B, so the three calls increment it to 3.
Raw{"answer":3,"explanation":"In PHP 8.1+ the inherited method shares its static $n between A and B, so the three calls increment it to 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 6.91 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();
``` | «11» Пояснение: send(10) resumes the generator, assigns 10 to $x, and the generator returns 11.
Raw{"answer":11,"explanation":"send(10) resumes the generator, assigns 10 to $x, and the generator returns 11."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 2.46 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,ok» Пояснение: The inner generator yields 1 and 2, returns 'ok' to the yield from expression, and outer then yields 'ok' as the third value.
Raw{"answer":"1,2,ok","explanation":"The inner generator yields 1 and 2, returns 'ok' to the yield from expression, and outer then yields 'ok' as the third value."} | неверно верный: «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 1.67 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';
``` | «noyes» Пояснение: The first check matches cost 4 so it prints 'no', while the second sees cost 5 and prints 'yes', concatenating to 'noyes'.
Raw{"answer":"noyes","explanation":"The first check matches cost 4 so it prints 'no', while the second sees cost 5 and prints 'yes', concatenating to 'noyes'."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 15.5 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» Пояснение: In PHP 8.5, E_ALL no longer includes the deprecated E_STRICT bit (2048), so the bitwise AND is 0 and the ternary prints 'strict-out'.
Raw{"answer":"strict-out","explanation":"In PHP 8.5, E_ALL no longer includes the deprecated E_STRICT bit (2048), so the bitwise AND is 0 and the ternary prints 'strict-out'."} | верно | 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 3.91 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 HTTP_X_TOKEN server header is exposed as X-Token by Symfony and retrieved successfully.
Raw{"answer":"mapped","explanation":"The HTTP_X_TOKEN server header is exposed as X-Token by Symfony and retrieved successfully."} | верно | 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 1.69 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;
``` | «bca» Пояснение: Listeners run in descending priority: B (10), C (5), then A (0).
Raw{"answer":"BCA","explanation":"Listeners run in descending priority: B (10), C (5), then A (0)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 1.28 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» Пояснение: Doctrine's identity map returns the same managed entity instance for the same ID.
Raw{"answer":"same","explanation":"Doctrine's identity map returns the same managed entity instance for the same ID."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 6.32 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» Пояснение: Persisting then removing the new entity before flush cancels the pending insert, so the users table remains empty.
Raw{"answer": 0, "explanation": "Persisting then removing the new entity before flush cancels the pending insert, so the users table remains empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.29 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;
``` | «1» Пояснение: COUNT(x) counts only non-NULL values, so the NULL row is ignored.
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values, so the NULL row is ignored."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.77 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,60» Пояснение: The window sum is cumulative (10, 30, 60), and string_agg concatenates them in id order.
Raw{"answer":"10,30,60","explanation":"The window sum is cumulative (10, 30, 60), and string_agg concatenates them in id order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 11.23 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 middleware are executed in the order provided, so M1 echoes before M2.
Raw{"answer":"M1M2","explanation":"The middleware are executed in the order provided, so M1 echoes before M2."} | верно | The first-added middleware runs first (outermost). |
T16-L10 4.63 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;
``` | «11» Пояснение: Both handlers are invoked for the dispatched message, so $n becomes 1 + 10 = 11.
Raw{"answer": 11, "explanation": "Both handlers are invoked for the dispatched message, so $n becomes 1 + 10 = 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.31 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 second insert conflicts with the unique index and is skipped, leaving one row.
Raw{"answer": 1, "explanation": "The second insert conflicts with the unique index and is skipped, leaving one row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 4.96 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;
``` | «2» Пояснение: The unique constraint is deferred, so the duplicate insert is allowed and the SELECT counts both rows before any constraint check.
Raw{"answer": 2, "explanation": "The unique constraint is deferred, so the duplicate insert is allowed and the SELECT counts both rows before any constraint check."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 2.12 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) | «6» Пояснение: The filter matches both test_sum and test_sum_abs, each with 3 data provider cases, totaling 6 tests.
Raw{"answer":6,"explanation":"The filter matches both test_sum and test_sum_abs, each with 3 data provider cases, totaling 6 tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 16.1 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) | «1, 1» Пояснение: PHPUnit 10.5 requires data provider methods to be static, so the invalid provider causes one test to be reported as errored/failed.
Raw{"answer":"1, 1","explanation":"PHPUnit 10.5 requires data provider methods to be static, so the invalid provider causes one test to be reported as errored/failed."} | неверно верный: «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 1.08 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: curl sends a POST request when data is provided with -d.
Raw{"answer": "POST", "explanation": "curl sends a POST request when data is provided with -d."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.63 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G option makes curl append the -d data as a query string and send a GET request.
Raw{"answer": "GET", "explanation": "The -G option makes curl append the -d data as a query string and send a GET request."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 1.52 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? | «invalid_client» Пояснение: RFC 6749 specifies that an unknown client_id at the token endpoint results in the invalid_client error.
Raw{"answer": "invalid_client", "explanation": "RFC 6749 specifies that an unknown client_id at the token endpoint results in the invalid_client error."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.17 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? | «fragment» Пояснение: With response_type=token, the access token is returned in the URI fragment of the redirect_uri.
Raw{"answer": "fragment", "explanation": "With response_type=token, the access token is returned in the URI fragment of the redirect_uri."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 2.15 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: The default filter treats false as empty, so it returns 2, and 2 * 3 equals 6.
Raw{"answer": 6, "explanation": "The default filter treats false as empty, so it returns 2, and 2 * 3 equals 6."} | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 8.62 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «twig\error\runtimeerror» Пояснение: The expression parses as ('a' ~ 1) + 2, causing a PHP TypeError during rendering that Twig wraps in a RuntimeError.
Raw{"answer":"Twig\\Error\\RuntimeError","explanation":"The expression parses as ('a' ~ 1) + 2, causing a PHP TypeError during rendering that Twig wraps in a RuntimeError."} | верно | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 21.49 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()]));
``` | «unexpectedtypeexception» Пояснение: NotBlank cannot validate an array, so Symfony throws an UnexpectedTypeException before any count is echoed.
Raw{"answer":"UnexpectedTypeException","explanation":"NotBlank cannot validate an array, so Symfony throws an UnexpectedTypeException before any count is echoed."} | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 3.45 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);
}
``` | «symfony\component\form\exception\logicexception» Пояснение: Calling isValid() on an unsubmitted form throws a Symfony Form LogicException.
Raw{"answer":"Symfony\\Component\\Form\\Exception\\LogicException","explanation":"Calling isValid() on an unsubmitted form throws a Symfony Form LogicException."} | верно | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 1.68 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» Пояснение: Services are shared by default, so both get('a') calls return the same object instance.
Raw{"answer":"same","explanation":"Services are shared by default, so both get('a') calls return the same object instance."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 2.73 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!» Пояснение: Compiling the container resolves nested parameter placeholders, so %greeting% becomes hi %name% and then hi Bob.
Raw{"answer":"hi Bob!","explanation":"Compiling the container resolves nested parameter placeholders, so %greeting% becomes hi %name% and then hi Bob."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.39 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960px» Пояснение: At the lg breakpoint (992px), Bootstrap 5.3's .container has a max-width of 960px.
Raw{"answer": "960px", "explanation": "At the lg breakpoint (992px), Bootstrap 5.3's .container has a max-width of 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 2.55 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» Пояснение: Both utilities have equal specificity, so the later-generated .text-danger rule overrides .text-primary in Bootstrap 5.3.
Raw{"answer":"text-danger","explanation":"Both utilities have equal specificity, so the later-generated .text-danger rule overrides .text-primary in Bootstrap 5.3."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.98 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,
) {}
}
``` | «2» Пояснение: The Domain class depends on both Application and Infrastructure classes, violating Domain → Domain only.
Raw{"answer": 2, "explanation": "The Domain class depends on both Application and Infrastructure classes, violating Domain → Domain only."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 2.37 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,
) {}
}
``` | «3» Пояснение: BillingService in Domain depends on one Application class and two Infrastructure classes, each violating the Domain → Domain only rule.
Raw{"answer": 3, "explanation": "BillingService in Domain depends on one Application class and two Infrastructure classes, each violating the Domain → Domain only rule."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.35 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;
``` | «10,15» Пояснение: The original Money object remains 10, while add() returns a new Money object with amount 15.
Raw{"answer":"10,15","explanation":"The original Money object remains 10, while add() returns a new Money object with amount 15."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.56 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();
``` | «1» Пояснение: The exception is thrown before unsetting the only item, so count() remains 1.
Raw{"answer": 1, "explanation": "The exception is thrown before unsetting the only item, so count() remains 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 4.0 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» Пояснение: PHP 8.4+ allows dereferencing `new C()` without extra parentheses, so `hi()` returns and echoes 'hi'.
Raw{"answer":"hi","explanation":"PHP 8.4+ allows dereferencing `new C()` without extra parentheses, so `hi()` returns and echoes 'hi'."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 2.61 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';
``` | «yesno» Пояснение: The lazy ghost starts uninitialized, so the first check prints 'yes'; accessing $o->v triggers initialization, so the second check prints 'no'.
Raw{"answer":"yesno","explanation":"The lazy ghost starts uninitialized, so the first check prints 'yes'; accessing $o->v triggers initialization, so the second check prints 'no'."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.93 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';
``` | «no» Пояснение: The Security Guard component and its AbstractGuardAuthenticator class were removed in Symfony 6.0, so they do not exist in Symfony 8.1.
Raw{"answer":"no","explanation":"The Security Guard component and its AbstractGuardAuthenticator class were removed in Symfony 6.0, so they do not exist in Symfony 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 2.38 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';
``` | «noyes» Пояснение: AnnotationClassLoader was removed after Symfony 6.4, while AttributeClassLoader exists, so the two echoes print "no" then "yes".
Raw{"answer":"noyes","explanation":"AnnotationClassLoader was removed after Symfony 6.4, while AttributeClassLoader exists, so the two echoes print \"no\" then \"yes\"."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |