Карта знаний PHP — qwen3.8:latest, run-37 · think: medium

{"answer": "no", "explanation": "Single-quoted strings treat content literally (only \\\\ and \\\' are escapes) while double-quoted strings interpret escape sequences and perform variable interpolation, so they are not processed identically."}

{"answer": "yes", "explanation": "The ?? operator is syntactic sugar for isset($var) ? $var : default, so it uses isset() semantics and does not trigger warnings for undefined variables."}

{"answer": "ab", "explanation": "In PHP, echo accepts multiple comma-separated arguments and outputs them concatenated together, so it prints 'ab'."}

{"answer": "yes", "explanation": "In PHP, print is a language construct that always returns the integer 1 and, unlike echo, can be used within an expression (e.g., $x = print 'hello';)."}

{"answer": "no", "explanation": "The elvis operator ($a ?: $b) returns the left operand when it is truthy, not falsy; when the left operand is falsy, it returns the right operand."}

{"answer": "yes", "explanation": "In PHP, the concatenation operator (.) sits lower in the precedence table than arithmetic operators like + and -, so e.g. 1 + 2 . 'foo' is parsed as (1+2) . 'foo'."}

{"answer": "no", "explanation": "In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64."}

{"answer": 3, "explanation": "Concatenation '.' has higher precedence than '+', so it's parsed as ('sum: ' . 2) + 3, which is 'sum: 2' + 3; the non-numeric string casts to 0, giving 0 + 3 = 3."}

{"answer": "no", "explanation": "With ===, arrays must have the same key/value pairs in the same order to be considered equal; order does not matter only with the loose == operator."}

{"answer": "no", "explanation": "0 == false uses loose comparison (==) and actually returns true, since false is cast to 0 in a numeric context."}

{"answer": "no", "explanation": "In PHP 8, when comparing a non-numeric string to an integer with ==, the integer is cast to a string, so 'abc' == 0 becomes 'abc' == '0', which is false."}

{"answer": "yes", "explanation": "In PHP, under loose comparison (==), null is considered equal to 0, '', and false all simultaneously."}

{"answer": 42, "explanation": "PHP's (int) cast parses the leading numeric portion of the string and stops at the first non-digit character, so '42abc' becomes 42."}

{"answer": 10, "explanation": "In PHP, the + operator coerces the numeric string '5' to the integer 5, then performs arithmetic addition: 5 + 5 = 10."}

{"answer": "no", "explanation": "In PHP, casting false to a string results in an empty string (\"\"), not \"0\"."}

{"answer": "yes", "explanation": "Due to IEEE 754 floating-point precision, 0.1 + 0.2 does not exactly equal 0.3, so the strict comparison (===) returns false."}

{"answer": "no", "explanation": "strrev() reverses a string at the byte level, which breaks multi-byte UTF-8 characters."}

{"answer": "yes", "explanation": "str_contains() checks if the needle 'world' exists in the haystack 'Hello world', and it does, so it returns true."}

{"answer": "no", "explanation": "str_pad() can pad on the right (default), left, or both sides via the $side parameter (STR_PAD_RIGHT, STR_PAD_LEFT, STR_PAD_BOTH)."}

{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs, not just spaces."}

{"answer": 6, "explanation": "strlen counts bytes: 'h'(1) + 'é'(2 in UTF-8) + 'l'(1) + 'l'(1) + 'o'(1) = 6 bytes."}

{"answer": "def", "explanation": "substr with a start offset of -3 begins 3 characters from the end of 'abcdef', returning 'def'."}

{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased and does not modify the original string, since PHP strings are passed by value."}

{"answer": "yes", "explanation": "In PHP, heredoc (<<<EOT) interpolates variables, while nowdoc (<<<'EOT') treats the content as a literal string with no variable interpolation."}

{"answer": "no", "explanation": "PHP's sort() function reindexes the array with sequential integer keys, discarding the original key-to-value associations; use asort() instead to preserve keys."}

{"answer": "yes", "explanation": "In PHP, string keys that represent valid integers (like '5') are automatically cast to integer keys."}

{"answer": "no", "explanation": "in_array() uses loose comparison (==) by default; the third parameter $strict must be set to true to enable === comparison."}

{"answer": "yes", "explanation": "Without a callback, array_filter() removes all falsy elements (false, 0, '0', '', null, []) and keeps only truthy values."}

{"answer": "no", "explanation": "By default, the $preserve_keys parameter of array_slice() is false, meaning numeric keys are reindexed starting from 0."}

{"answer": "[20, 30]", "explanation": "array_slice with offset 1 and length 2 returns elements at indices 1 and 2, which are 20 and 30."}

{"answer": 2, "explanation": "The + operator keeps the left array's value for duplicate keys, so the result is ['a' => 1, 'b' => 2], which has 2 elements."}

{"answer": "no", "explanation": "PHP 8.1's array spread operator only supports arrays with integer keys (lists); using it on arrays with string keys throws an Error."}

{"answer": "no", "explanation": "In PHP 8.0+, named arguments can be combined with argument unpacking (e.g., foo(a: 1, ...$args)) as long as named arguments appear before the unpacking."}

{"answer": "no", "explanation": "In PHP, closures do not inherit variables from the outer scope; they must be explicitly imported with the 'use' keyword."}

{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function (3), regardless of the number of declared parameters."}

{"answer": "no", "explanation": "PHP arrow functions (fn) can only contain a single expression as their body; they cannot have a curly-brace block with multiple expressions."}

{"answer": "no", "explanation": "PHP arrow functions (fn) implicitly capture outer variables by value at the time the fn expression is created, not by reference or lazily at use time."}

{"answer": "yes", "explanation": "In PHP, a static closure (static function () {}) does not capture $this from the enclosing scope, similar to how static methods cannot use $this."}

{"answer": 5, "explanation": "The use ($x) keyword captures the value of $x (which is 5) by value at closure creation time, so the later reassignment to 7 does not affect the closure."}

{"answer": "yes", "explanation": "In PHP's default weak (coercive) typing mode, a numeric string like \"5\" is automatically cast to int 5 when passed to an int-typed parameter."}

{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing parameters to be declared as properties directly in the constructor signature."}

{"answer": "final", "explanation": "In PHP, the 'final' keyword before a method declaration prevents it from being overridden in any subclass."}

{"answer": "yes", "explanation": "In PHP, a final method cannot be overridden by any subclass, which is the defining purpose of the final keyword."}

{"answer": "no", "explanation": "Private properties are only accessible within the class that declares them; subclasses cannot access them (only protected or public properties are inherited)."}

{"answer": "class@anonymous", "explanation": "In PHP, get_class() on an anonymous class returns a name like 'class@anonymous\\0/file.php:LINE', so the part before the NUL byte is 'class@anonymous'."}

{"answer": "yes", "explanation": "In PHP, private methods are not inherited and are invisible to child classes, so a child class is free to declare a method with the same name and any visibility without violating any inheritance contract."}

{"answer": "no", "explanation": "__get() is called for both non-existent AND inaccessible (private/protected) properties, not only for non-existent ones."}

{"answer": "Error", "explanation": "Reassigning a readonly property in PHP throws an Error (specifically a 'Cannot modify readonly property' Error), not an Exception."}

{"answer": "yes", "explanation": "In PHP, interfaces can declare constants, which are always public and immutable."}

{"answer": "instanceof", "explanation": "In PHP, the instanceof operator checks whether an object is an instance of a particular class or interface."}

{"answer": "no", "explanation": "PHP interfaces cannot contain static methods; declaring one results in a fatal error."}

{"answer": "no", "explanation": "In PHP, the instanceof operator checks both class inheritance and interface implementation, so it does not ignore interfaces."}

{"answer": "no", "explanation": "In PHP, interface methods must be abstract and cannot have a body/implementation; only traits and abstract classes can provide concrete method implementations."}

{"answer": "yes", "explanation": "In PHP, abstract methods in an abstract class can be declared as either public or protected visibility."}

{"answer": 3, "explanation": "The enum Foo defines three cases (A, B, C), so Foo::cases() returns an array of 3 elements."}

{"answer": "yes", "explanation": "In PHP, traits can declare constants (as well as methods and properties), which are inherited by any class that uses the trait."}

{"answer": "yes", "explanation": "In PHP 7+, both the Exception and Error classes implement the Throwable interface, making it their common ancestor."}

{"answer": "no", "explanation": "In PHP, TypeError inherits directly from Throwable, not from Exception, so a catch(Exception) block will not catch a TypeError."}

{"answer": "no", "explanation": "The @ operator only suppresses PHP errors (warnings, notices); exceptions are still thrown and must be caught with try/catch."}

{"answer": "DivisionByZeroError", "explanation": "In PHP, intdiv(5, 0) throws a DivisionByZeroError, which is a subclass of ArithmeticError."}

{"answer": "no", "explanation": "The finally block always executes regardless of whether an exception was thrown, caught, or not thrown at all."}

{"answer": "no", "explanation": "In PHP, an exception thrown inside a finally block will replace any exception being propagated from the try/catch block, so it does have an effect on the result."}

{"answer": "yes", "explanation": "In PHP, casting any object (including an Exception) to boolean always yields true."}

{"answer": "yes", "explanation": "Functions registered with register_shutdown_function() are executed when the script shuts down, which includes when exit() or die() is called."}

{"answer": "no", "explanation": "The 'use' statement only creates an alias for a fully-qualified class name; the file is actually loaded by the autoloader when the class is first referenced (e.g., instantiated)."}

{"answer": "function", "explanation": "In PHP, importing a function uses the syntax 'use function Namespace\\function;', while 'const' is used for importing constants."}

{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 strips the 'App\\' prefix, converts the remaining namespace segments 'Controller\\Api\\User' into directory paths, and appends the class name with .php, giving src/Controller/Api/UserController.php."}

{"answer": "yes", "explanation": "Composer's vendor/autoload.php calls spl_autoload_register() to register its autoloader so PHP invokes it for undefined classes."}

{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string if no namespace is declared)."}

{"answer": "no", "explanation": "An unqualified class name in a `new` expression is resolved relative to the current namespace, not the global root (unless you are already in the global namespace)."}

{"answer": "yes", "explanation": "PSR-4 maps the sub-namespace Model\\User to the relative path Model/User.php under the base directory src/, giving src/Model/User.php."}

{"answer": "yes", "explanation": "In PHP, a namespace use statement placed inside a function body is scoped to that function only."}

{"answer": "yes", "explanation": "In PHP, arrays are value types; assigning an array to a new variable creates a copy (using copy-on-write internally) rather than a reference, and functions receive arrays by value unless explicitly passed by reference with &."}

{"answer": 2, "explanation": "PHP arrays are copied by value on assignment, so modifying $b does not affect $a, which still has 2 elements."}

{"answer": "yes", "explanation": "In PHP, function-local scope isolates variables, so global variables must be accessed via the global keyword, $GLOBALS superglobal, or passed as parameters."}

{"answer": "no", "explanation": "$GLOBALS always references the true global scope, so unset($GLOBALS['x']) permanently removes the global variable $x, not just within the function."}

{"answer": 6, "explanation": "The function modifies $n by reference, incrementing it from 5 to 6."}

{"answer": "no", "explanation": "A by-value foreach iterates over a snapshot of the array; modifications inside the loop do not affect the current iteration pass."}

{"answer": "no", "explanation": "A static property belongs to the class itself (only one copy exists), so changes made through any instance are visible to all instances."}

{"answer": "no", "explanation": "In PHP, boolean array keys are cast to integers (true becomes 1, false becomes 0), so the key is stored as an integer, not a boolean."}

{"answer": "yes", "explanation": "PHP generators allow a return statement with a value, and that value is accessible via the Generator object's getReturn() method after the generator is fully exhausted."}

{"answer": "no", "explanation": "PHP generators are one-shot iterators; once fully consumed, they cannot be rewound or re-traversed."}

{"answer": "yes", "explanation": "PHP's yield from (introduced in PHP 7.0) delegates iteration to another generator or Traversable, yielding each value from it as part of the current generator."}

{"answer": "Generator", "explanation": "Calling a generator function returns a Generator object, and get_class() on that object returns the string 'Generator'."}

{"answer": 3, "explanation": "The generator yields from [1,2,3] producing 3 elements, iterator_to_array converts them to an array of 3 elements, and count returns 3."}

{"answer": "no", "explanation": "SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO queue; SplQueue is the one that implements a FIFO queue."}

{"answer": "yes", "explanation": "ArrayIterator is an SPL class that wraps an array and implements the Iterator interface, allowing traversal via foreach, current(), next(), key(), and valid()."}

{"answer": "no", "explanation": "ArrayObject implements IteratorAggregate (via Traversable), so it can be traversed with foreach."}

{"answer": "yes", "explanation": "PHP's password_hash() automatically generates and embeds a random salt in the returned hash string, so no separate salt needs to be supplied."}

{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is bcrypt (PASSWORD_BCRYPT), not md5; md5 is a simple non-salted hash algorithm not suitable for password storage."}

{"answer": "yes", "explanation": "password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) returns true because the plaintext matches the hash, which corresponds to 'yes' in this format."}

{"answer": "no", "explanation": "strip_tags() removes HTML/PHP tags and is meant to mitigate XSS, not SQL injection; SQL injection is prevented by using prepared statements or parameterized queries."}

{"answer": "yes", "explanation": "session_regenerate_id() creates a new session ID, invalidating the old one, which prevents an attacker from exploiting a pre-known session ID (session fixation) after a user logs in."}

{"answer": "php_sapi_name()", "explanation": "The built-in function php_sapi_name() returns the SAPI (Server API) name of the current PHP interface, such as 'cli', 'apache2', or 'fpm-fcgi'."}

{"answer": "yes", "explanation": "session_destroy() only removes session data from the server; the session cookie in the browser must be deleted separately via setcookie() with a past expiration time."}

{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() has been called; without it, $_SESSION remains empty."}

{"answer": "not introduced", "explanation": "PHP has no built-in array_find() function; it was never introduced in any PHP version."}

{"answer": "yes", "explanation": "PHP 8.4 introduced property hooks, allowing get/set logic to be declared directly on a property definition."}

{"answer": "yes", "explanation": "Asymmetric visibility (e.g., public private(set) string $name) was indeed introduced as a new feature in PHP 8.4."}

{"answer": "8.4", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4."}

{"answer": "no", "explanation": "PHP has never included a |> pipe operator in any version; the | symbol in PHP is the bitwise OR operator."}

{"answer": "none", "explanation": "The 'clone-with' syntax clone($obj, ['x' => 1]) does not exist in any PHP version; PHP's clone operator only performs a shallow copy without accepting modification parameters."}

{"answer": "not a real PHP function", "explanation": "array_first() and array_last() are not built-in PHP functions in any released version of PHP; they do not exist in the standard library."}

{"answer": "8.5", "explanation": "The RFC Partial Function Application v2 was adopted for PHP 8.5."}

{"answer": "8.4", "explanation": "The clamp() function (RFC clamp_v2) was implemented in PHP 8.4."}

{"answer": "no", "explanation": "There is no known 'RFC Context Managers v2' that has been adopted into PHP; this appears to be a fabricated RFC title."}

{"answer": "no", "explanation": "There is no known PHP RFC titled 'Bound-Erased Generic Types' that was declined in 2026; this appears to be a fabricated claim."}

{"answer": "no", "explanation": "As of the latest available information, no RFC has been accepted in PHP to make the Zend Thread-Safe (ZTS) build the default; NTS remains the default build."}

{"answer": "yes", "explanation": "PHP has never included native generics/parameterized types, and none were introduced in any release up to and including PHP 8.5."}

{"answer": "yes", "explanation": "PHP follows a November release cadence; PHP 8.5 was released in November 2025, and PHP 8.6's GA on 2026-11-19 means it is not yet out as of 2026-11-07."}

{"answer": "yes", "explanation": "PHP 6 was a planned version that was never released; the development team skipped it and went directly from PHP 5.6 to PHP 7.0."}

{"answer": "no", "explanation": "The RFC for adding a #[\\Deprecated] attribute to PHP core was not adopted; no such built-in attribute exists in PHP as of 8.4."}

{"answer": "yes", "explanation": "In both Clean and Onion architecture, the dependency rule states that dependencies always point inward toward the domain center, and inner layers have no knowledge of outer layers."}

{"answer": "yes", "explanation": "In proper Domain-Driven Design, domain entities are pure PHP classes that must not depend on frameworks like Doctrine or Symfony, relying only on the language and standard library."}

{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (UI) layer, not the business-logic layer; they simply translate HTTP requests into use-case calls and results into views."}

{"answer": "Business Rules", "explanation": "In Onion Architecture, the core Business Rules (domain entities) sit at the very center, with all other layers depending inward toward them."}

{"answer": "yes", "explanation": "Tools like Deptrac are specifically designed to enforce layer-dependency rules and will fail the build when a forbidden call between layers is detected."}

{"answer": "no", "explanation": "A use case (interactor) should remain framework-agnostic and depend on abstractions, not on concrete HTTP request objects or ORM EntityManagers, which are adapter-level concerns."}

{"answer": "Repository", "explanation": "A Repository provides a collection of aggregates/entities and hides the storage mechanism behind an interface, following the Repository pattern."}

{"answer": "yes", "explanation": "In Clean Architecture, the database is an outermost-layer (Frameworks & Drivers) detail; the domain and use cases depend only on interfaces, so swapping the concrete driver requires changes only in the outer layer."}

{"answer": "no", "explanation": "In DDD, an aggregate is a cluster of domain objects (entities and value objects) bounded by a root entity to enforce invariants; it is a domain modeling concept, not a database table, and can span multiple tables or share tables with other aggregates."}

{"answer": "yes", "explanation": "In Domain-Driven Design, a Value Object is defined as immutable and is considered equal to another if all its field values are the same, rather than being distinguished by a unique identity like an Entity."}

{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single external entry point of an aggregate through which all changes must be directed to maintain consistency."}

{"answer": "yes", "explanation": "In DDD, a repository is defined per aggregate root to preserve the aggregate boundary; individual entities inside the aggregate are accessed through the root, not via their own repositories."}

{"answer": "yes", "explanation": "In Domain-Driven Design, the Ubiquitous Language is indeed the shared vocabulary used consistently by both developers and domain experts across the model, code, and conversation."}

{"answer": "domain", "explanation": "In model theory, the domain (or universe of discourse) is the set within which a language is consistently interpreted by a model; outside it, the same symbols can be interpreted by different models."}

{"answer": "no", "explanation": "DDD recommends rich domain models where entities and value objects encapsulate their own business logic, not anemic models with logic pushed into services."}

{"answer": "yes", "explanation": "In DDD, a Bounded Context defines a boundary within which a domain model applies, so the same real-world concept (e.g., 'Customer') can be different classes in different bounded contexts."}

{"answer": "yes", "explanation": "Symfony's DI container instantiates services lazily by default, meaning they are only created when first requested rather than at container build time."}

{"answer": "debug:router", "explanation": "In Symfony, the command 'bin/console debug:router' lists all registered routes with their paths, methods, and controllers."}

{"answer": "no", "explanation": "Symfony autowiring eliminates the need to manually wire dependencies by resolving them from type hints, and combined with auto-registration, services can be discovered automatically from a directory without individual declarations."}

{"answer": "yes", "explanation": "Twig compiles templates into PHP classes (extending Twig\\Template) and caches the compiled output on disk to avoid recompilation on subsequent requests."}

{"answer": "yes", "explanation": "In Symfony's dev environment, the compiled DI container is cached and only recompiled when tracked files (e.g., service configs, classes) change, not on every request."}

{"answer": "SYMFONY_ENV", "explanation": "The SYMFONY_ENV environment variable (or APP_ENV in Symfony 4+) selects the active Symfony environment such as dev or prod."}

{"answer": "no", "explanation": "Symfony's controller resolver invokes the target method from outside the class, so controller action methods must be public; private (or protected) methods will cause an error."}

{"answer": "no", "explanation": "Listeners and subscribers are ordered by their assigned priority value, not by their registration type; a listener can have higher priority than a subscriber."}

{"answer": "yes", "explanation": "Symfony 6.0 removed the legacy guard authentication system and introduced a new security architecture built around authenticator classes implementing AuthenticatorInterface."}

{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute from Symfony SecurityBundle checks a role or permission on a controller method and returns 403 Forbidden if the user lacks the required authorization."}

{"answer": "yes", "explanation": "Voters in Symfony are specifically designed to evaluate access to a particular object (subject), as demonstrated by isGranted('EDIT', $post), unlike simple role checks which have no subject."}

{"answer": "yes", "explanation": "Symfony 7 removed support for Doctrine Annotations; validation constraints must now be declared using PHP 8 attributes (or XML/YAML mapping), as annotations were deprecated in 6.0 and dropped in 7.0."}

{"answer": "yes", "explanation": "Symfony forms include CSRF protection by default; a CSRF token is automatically added to the form and validated on submission unless explicitly disabled."}

{"answer": "yes", "explanation": "Symfony always performs server-side form validation regardless of whether HTML5 client-side checks passed, as client-side validation is only a UX enhancement and cannot be trusted."}

{"answer": "maker:form", "explanation": "The Symfony MakerBundle command 'maker:form' generates a FormType class for creating form classes."}

{"answer": "no", "explanation": "Symfony never stores the password in the session; it only stores an authentication token (user ID, roles, etc.), and passwords are kept hashed in the database."}

{"answer": "yes", "explanation": "In modern Symfony (4+), the recommended convention is to place each bundle's configuration in its own file under config/packages/ (e.g., framework.yaml, doctrine.yaml, security.yaml)."}

{"answer": "yes", "explanation": "This is the Symfony convention: .env (with safe dev defaults) is committed, while .env.local (holding real secrets) is gitignored."}

{"answer": "debug:container", "explanation": "The Symfony command `debug:container` (accessible via `bin/console debug:container`) lists all registered services and their aliases in the service container."}

{"answer": "no", "explanation": "The Symfony container is compiled (immutable) before runtime; setParameter() from a controller has no effect on already-resolved parameter values."}

{"answer": "no", "explanation": "Since Symfony 4.0, services are private (public: false) by default; you must explicitly set public: true to fetch them from the container."}

{"answer": "no", "explanation": "Many Symfony bundles work perfectly fine without a config file in config/packages; configuration is only needed when a bundle requires specific settings."}

{"answer": "yes", "explanation": "In Symfony, environment variables are referenced in services.yaml (and other config files) using the %env(VAR)% syntax, e.g. %env(DATABASE_URL)%."}

{"answer": "APP_DEBUG", "explanation": "In Symfony, the APP_DEBUG environment variable controls whether debug mode is enabled, affecting the profiler and Twig's debug features."}

{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers to be registered for the same message class; all matching handlers will be invoked (in priority order) when the message is dispatched."}

{"answer": "no", "explanation": "The sync transport processes the message immediately in the same process without queuing it for a worker."}

{"answer": "bin/console messenger:consume", "explanation": "The Symfony Messenger component uses the messenger:consume command to start the worker that processes queued messages."}

{"answer": "yes", "explanation": "In Symfony Messenger, each transport can define its own retry_strategy (max_retries, delay, multiplier, max_delay) in the messenger configuration."}

{"answer": "yes", "explanation": "Symfony Messenger's default Serializer uses JSON as the serialization format for messages."}

{"answer": "yes", "explanation": "Symfony Scheduler (introduced in 6.3) defines scheduled tasks that, when their trigger time arrives, produce and dispatch Messenger messages through the Symfony Messenger component."}

{"answer": "doctrine", "explanation": "Symfony Messenger's Doctrine transport persists messages in database tables using Doctrine DBAL/ORM."}

{"answer": "yes", "explanation": "Symfony Messenger's pipeline is designed to be extensible; you can register custom middleware at any position (before or after built-in middleware) via the messenger.bus configuration."}

{"answer": "yes", "explanation": "Symfony follows a predictable release cycle: major versions (e.g., 6.0, 7.0) every two years in May, and minor versions (e.g., 6.1, 6.2) every six months in May and November."}

{"answer": "8.4", "explanation": "Symfony 8 requires PHP 8.4 as the minimum version, following the pattern of requiring the two most recent PHP major versions."}

{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations (e.g., @Route, @Assert) in favor of native PHP 8 attributes; the annotation-based approach was deprecated in 6.4 and dropped in 7.0."}

{"answer": "yes", "explanation": "Symfony's AssetMapper component manages CSS/JS assets in pure PHP using an importmap.php (or importmap.json) file, eliminating the need for Node.js or webpack."}

{"answer": "no", "explanation": "Symfony 6.4 is actually a Long-Term Support (LTS) release, supported until November 2027, following the .4 minor version LTS pattern (3.4, 4.4, 5.4, 6.4)."}

{"answer": "no", "explanation": "Symfony's deprecation policy states that deprecations introduced in one major version are removed in the following major version, not kept indefinitely."}

{"answer": "yes", "explanation": "Symfony provides an UPGRADE-<version>.md file for every major (and minor) release in its repository, documenting breaking changes and deprecations."}

{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component manages assets and the importmap without requiring Node.js or Webpack."}

{"answer": "no", "explanation": "Following Symfony's biannual release cycle (May and November), Symfony 8.0 would be released in May 2026 and 8.1 in November 2026; version 8.2 would not appear until approximately May 2027, so it has not been released by 2026-11-07."}

{"answer": "no", "explanation": "Following Symfony's six-month cycle (alternating May/November), Symfony 8.2 would be scheduled for May 2027, not November 2026 (which would be Symfony 8.1)."}

{"answer": "8.2", "explanation": "Following Symfony's minor version numbering, the version immediately after 8.1 is 8.2."}

{"answer": "no", "explanation": "Symfony 8.2 does not exist; as of current knowledge Symfony is in the 7.x series, and even major releases involve migration rather than a complete rewrite."}

{"answer": "yes", "explanation": "Within the same major PHP version (8.x), minor updates (e.g., 8.1 → 8.2) guarantee backward compatibility, so existing code should not need changes."}

{"answer": 8.2, "explanation": "Following Symfony's typical release cadence (new minor every six months), 8.2 is the last minor release in the 8.x line before the 9.0 major version."}

{"answer": "no", "explanation": "As of current knowledge, Symfony 8.x has not been released, and no official requirement of Symfony 8.2 demanding PHP 8.5 has been confirmed; the statement is not verifiable as true."}

{"answer": "yes", "explanation": "Symfony's deprecation policy guarantees that deprecations introduced in a major version (8.x) will not be removed until the next major version (9.0)."}

{"answer": "no", "explanation": "Twig is a template engine that restricts expressions to safe operations (variable access, method calls on exposed objects, filters, etc.) and does not allow executing arbitrary PHP code inside {{ }}."}

{"answer": "yes", "explanation": "Twig enables auto-escaping with the 'html' strategy by default, so variables printed with {{ }} are HTML-escaped automatically."}

{"answer": "yes", "explanation": "The Twig |e (escape) filter, by default, escapes a string for safe output in an HTML context using htmlspecialchars with ENT_QUOTES."}

{"answer": "number_format", "explanation": "The number_format filter from twig/intl-extra formats a number according to a given locale."}

{"answer": "yes", "explanation": "The |raw filter (also known as |safe in Twig) explicitly marks a value as trusted and disables the templating engine's automatic output escaping."}

{"answer": "yes", "explanation": "In Twig, {{ }} is the output tag for printing expression values, and {% %} is the statement tag for executing control structures like if, for, and set."}

{"answer": "no", "explanation": "Twig allows declaring variables inside a template using the {% set %} tag, so values are not limited to what the controller passes."}

{"answer": "dump", "explanation": "The Twig debug function `dump()` outputs the debug structure of a variable (array, object, etc.) for inspection."}

{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS library providing ready-made UI components (grid, navbar, modals, etc.), not an SPA framework like React, Angular, or Vue."}

{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive, centered container with a fixed max-width that changes at each breakpoint."}

{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns (not 16), and modern Bootstrap (v4+) uses CSS Flexbox rather than floats."}

{"answer": "yes", "explanation": "In Bootstrap 5, the five named breakpoint infixes used in responsive utility classes are sm, md, lg, xl, and xxl."}

{"answer": "no", "explanation": "The numbers (0–5) are indices into a predefined spacing scale (e.g., .mt-3 = $spacer × 1, .mt-1 = $spacer × 0.25), not direct multiples of $spacer."}

{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, popovers, and collapse elements."}

{"answer": "yes", "explanation": "Bootstrap 5 dropped its jQuery dependency and reimplements all interactive components (modals, tooltips, dropdowns, etc.) in plain vanilla JavaScript."}

{"answer": "no", "explanation": "Bootstrap 5 dark mode is enabled with the data-bs-theme=\"dark\" attribute on the <html> element, not a .dark class."}

{"answer": "no", "explanation": "Doctrine ORM does not auto-create tables at runtime; you must explicitly generate schema via migrations, SchemaTool, or manual DDL scripts."}

{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed so it will be inserted on the next flush() call, without executing SQL immediately."}

{"answer": "no", "explanation": "EntityManager::merge() was deprecated in Doctrine ORM 2 and removed entirely in Doctrine ORM 3."}

{"answer": "yes", "explanation": "DQL (Doctrine Query Language) is an object-oriented query language that references entities and their fields, not the underlying database tables and columns."}

{"answer": "null", "explanation": "In Doctrine, the repository's find() method returns null when no entity with the given identifier exists in the database."}

{"answer": "no", "explanation": "DoctrineBundle in modern Symfony does not automatically call flush() at the end of a request; developers must explicitly call $entityManager->flush() to persist changes (the old auto_commit feature was removed)."}

{"answer": "yes", "explanation": "In Doctrine ORM, once an entity is managed, the Unit of Work tracks all property changes, so flush() will detect and commit modifications without needing another persist() call."}

{"answer": "no", "explanation": "Doctrine's remove() only marks the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called."}

{"answer": "no", "explanation": "MVCC in PostgreSQL means readers do NOT block writers and writers do NOT block readers; that non-blocking concurrency is the primary benefit of MVCC."}

{"answer": "EXPLAIN", "explanation": "The EXPLAIN command displays the query's execution plan (join order, indexes used, etc.) without actually running the query."}

{"answer": "no", "explanation": "SERIAL is syntactic sugar that creates a separate sequence and sets a default expression, while GENERATED AS IDENTITY is a SQL-standard column-level feature; they are different mechanisms that achieve a similar outcome."}

{"answer": "no", "explanation": "In PostgreSQL, a UNIQUE constraint treats NULLs as distinct from each other, so multiple rows can have NULL in that column."}

{"answer": "string_agg", "explanation": "PostgreSQL's string_agg(value, delimiter) aggregate function concatenates string values with a specified separator."}

{"answer": "no", "explanation": "Plain VACUUM only marks dead tuple space as reusable within the table file; it does not shrink the file or return space to the OS (that requires VACUUM FULL)."}

{"answer": "PARTITION", "explanation": "In a window function definition, the PARTITION BY clause divides rows into groups over which the window function is computed."}

{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; non-repeatable reads can still occur because another transaction can modify and commit a row between two reads within the same transaction."}

{"answer": "yes", "explanation": "PostgreSQL has autocommit enabled by default, meaning each individual SQL statement is wrapped in its own implicit transaction and committed immediately upon successful execution."}

{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction and permanently saves all changes made within it."}

{"answer": "yes", "explanation": "Indexes are used by the query engine to locate rows for any statement (SELECT, UPDATE, DELETE) whose WHERE clause references the indexed column, avoiding a full table scan."}

{"answer": "yes", "explanation": "SAVEPOINT in PostgreSQL allows you to roll back to a specific point within a transaction without aborting the entire transaction, enabling partial rollback of statements."}

{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to collect real timing and row-count statistics; only plain EXPLAIN shows the plan without execution."}

{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that adds a vector data type and index support for performing similarity searches on embeddings."}

{"answer": "yes", "explanation": "A partial index in PostgreSQL stores entries only for rows that satisfy the specified WHERE condition, reducing index size and improving performance for targeted queries."}

{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE via Serializable Snapshot Isolation (SSI), which uses conflict detection at commit time rather than locking rows read during the transaction."}

{"answer": "yes", "explanation": "HTTP 201 Created is the standard response indicating that a new resource has been successfully created as a result of the request."}

{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with an empty response body, commonly returned after a DELETE operation."}

{"answer": "yes", "explanation": "Per RFC 9110 (and previously RFC 7231), DELETE is explicitly listed as an idempotent method: repeating the request after the resource is already removed does not further change the server state."}

{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server in its response to indicate which origin is allowed to access the resource, not by the client."}

{"answer": "yes", "explanation": "HTTP 429 Too Many Requests, defined in RFC 6585, is specifically used to indicate that a client has sent too many requests in a given time period, i.e., a rate limit has been exceeded."}

{"answer": "no", "explanation": "It is the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors."}

{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type (media type) of the request or response body."}

{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent by default, whereas PUT (RFC 9110) is required to be idempotent."}

{"answer": "no", "explanation": "Using == for hash comparison is vulnerable to timing attacks; hash_equals() should be used for constant-time comparison."}

{"answer": "yes", "explanation": "CSRF tokens are indeed generated server-side, tied to the user's session, and validated on the server when handling state-changing (unsafe) HTTP methods such as POST, PUT, or DELETE."}

{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to declare which resources are allowed to load and execute on a web page, enabling the CSP mechanism."}

{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol (granting access to resources), not an authentication protocol; the access token conveys permissions/scopes, while identifying the user is the role of an ID token (e.g., via OpenID Connect)."}

{"answer": "no", "explanation": "XSS is primarily prevented by output encoding (escaping) when rendering data in HTML, not by input validation before database storage; valid input for a database can still be dangerous in an HTML context."}

{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the authorization code (parameter 'code') is appended to the redirect_uri, and the client then exchanges it at the token endpoint for an access token."}

{"answer": "yes", "explanation": "A refresh token has a longer lifetime than an access token and is used to obtain a new access token without requiring the user to log in again."}

{"answer": "no", "explanation": "A salt does not need to be kept secret; it is typically stored alongside the hash (e.g., in the same database row) and its purpose is to prevent rainbow-table attacks, not to provide secrecy."}

{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase in order to discover and run test methods."}

{"answer": "no", "explanation": "setUp() runs before each individual test method, while setUpBeforeClass() (a static method) runs once before all tests in the class."}

{"answer": "no", "explanation": "A data provider can supply multiple sets of arguments, causing the test to run once per set, not just exactly one."}

{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares that a specific exception class is expected to be thrown during the test."}

{"answer": "no", "explanation": "The statement is reversed: a stub simply returns pre-defined data, while a mock verifies (asserts) which methods were called and how."}

{"answer": "yes", "explanation": "PHPUnit 10 requires PHP 8.1+ and introduces the #[DataProvider] attribute as the modern replacement for the deprecated @dataProvider docblock annotation."}

{"answer": "no", "explanation": "PHPUnit does allow test dependencies via the @depends annotation or the depends() method, passing the return value of one test as an argument to another."}

{"answer": "--random-order", "explanation": "The --random-order command-line option in PHPUnit makes tests execute in a random order rather than their defined sequence."}

{"answer": "3-3", "explanation": "intdiv(7,2) is 3 and intdiv(-7,2) is -3 (truncates toward zero), concatenated as a string '3-3'."}

{"answer": -9, "explanation": "In PHP, the ** operator has higher precedence than unary minus, so -3 ** 2 is parsed as -(3**2) = -9."}

{"answer": "true", "explanation": "In PHP (prior to 8), both '1e1' and '10' are numeric strings, so they are compared numerically: '1e1' is scientific notation for 10, making 10 == 10 true."}

{"answer": "other", "explanation": "In PHP 8, the loose comparison 'a' == 0 is false (the integer 0 is cast to string '0', which doesn't equal 'a'), so the default case executes."}

{"answer": "2c", "explanation": "strtr with an array matches the longest key first, so 'ab' is replaced by '2' before 'a' could be replaced, yielding '2c'."}

{"answer": "[]", "explanation": "substr('hello', -10) returns an empty string because the negative offset (-10) exceeds the string length (5), so the result is '[' + '' + ']' = '[]'."}

{"answer": "k,n,m", "explanation": "The + operator performs array union keeping left-side values for duplicate keys, so the keys are k, n, m in that order."}

{"answer": "yxz", "explanation": "After sorting by index 2 (values 2,1,2 → 1,2,2), the second column becomes ['y','x','z'], which implodes to 'yxz'."}

{"answer": 4, "explanation": "The spread operator with a string-keyed array passes named arguments (a: 5, b: 1), so f returns 5 - 1 = 4."}

{"answer": 3, "explanation": "The first-class callable $p->g(...) creates a closure bound to the object $p, holding a strong reference to it, so the object survives even after $p = null, and calling $f() returns $this->v which is 3."}

{"answer": "B", "explanation": "static::class uses late static binding, so it returns the name of the class the object was instantiated from, which is B."}

{"answer": "infinite recursion (fatal error)", "explanation": "Assigning to $this->x inside its own set hook re-triggers the hook, causing infinite recursion and a fatal error, as explicitly documented in the PHP 8.4 property hooks RFC."}

{"answer": "BA", "explanation": "TB::f insteadof TA makes f() return 'B', and TA::f as g aliases it to g() returning 'A', so the concatenation is 'BA'."}

{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of the trait's static properties, so setting CX::$n does not affect CY::$n."}

{"answer": 2, "explanation": "In PHP, a return statement in a finally block overrides the return value of the try block, so the function returns 2."}

{"answer": "second", "explanation": "When the finally block throws a new exception (LogicException), it replaces the original RuntimeException and propagates to the outer catch, which prints 'second'."}

{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves via the use alias to App\\Foo, while \\Baz::class refers to the global-namespace class Baz, yielding 'Baz'."}

{"answer": "noyes", "explanation": "class_exists('Foo') is false because Foo is in namespace Ns (not global), but class_exists('Ns\\\\Foo') is true since the class is defined there, concatenating to 'noyes'."}

{"answer": "1,2,99", "explanation": "After a foreach by reference, $v remains a reference to the last element of $a, so $v = 99 modifies $a[2] to 99."}

{"answer": 3, "explanation": "The static variable $n is shared per defining class (A), so all three calls increment the same variable: 1, 2, 3; the last call echoes 3."}

{"answer": 11, "explanation": "send(10) makes the yield expression evaluate to 10, so $x=10, and the generator returns 10+1=11, which getReturn() retrieves."}

{"answer": "1,2,ok", "explanation": "yield from inner() yields 1 and 2 from the inner generator, captures its return value 'ok' in $r, then outer yields 'ok', so implode produces '1,2,ok'."}

{"answer": "noyes", "explanation": "The first call checks rehash with the same cost (4), so it returns false ('no'); the second call checks with a different cost (5), so it returns true ('yes')."}

{"answer": "strict-in", "explanation": "E_ALL in PHP 8.5 still includes the E_STRICT bit (2048), so E_ALL & 2048 equals 2048 (not 0), making the condition false and printing 'strict-in'."}

{"answer": "mapped", "explanation": "Symfony's Request::create stores HTTP_X_TOKEN as the x-token header, and the header bag is case-insensitive, so get('X-Token') returns 'abc'."}

{"answer": "BCA", "explanation": "Symfony EventDispatcher executes listeners in descending priority order (higher priority first): B (10), C (5), A (0)."}

{"answer": "same", "explanation": "Doctrine ORM's identity map (UnitOfWork) guarantees that calling find() with the same class and ID within the same EntityManager returns the same object instance."}

{"answer": 0, "explanation": "Persisting then removing a new entity before flush cancels the scheduled INSERT, so no row is ever written to the users table."}

{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x; there is one row with x=1 and one with x=NULL, so the result is 1."}

{"answer": "10,30,60", "explanation": "The window function sum(x) OVER (ORDER BY id) produces a running total (10, 30, 60), and string_agg concatenates them as text in id order with commas."}

{"answer": "M1M2", "explanation": "The MessageBus processes middlewares in order: M1 echoes 'M1' then calls next, M2 echoes 'M2' then calls next (the final handler), producing 'M1M2'."}

{"answer": 11, "explanation": "HandleMessageMiddleware calls all handlers in the HandlersLocator for Ping (first adds 1, then adds 10), so $n = 0 + 1 + 10 = 11."}

{"answer": 1, "explanation": "The first INSERT succeeds, the second INSERT is skipped due to the unique index conflict with ON CONFLICT DO NOTHING, so count(*) returns 1."}

{"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so the uniqueness check is postponed until COMMIT, meaning both INSERTs succeed and SELECT count(*) returns 2."}

{"answer": 6, "explanation": "The --filter 'test_sum' matches both test_sum (3 data sets) and test_sum_abs (3 data sets) since it's a regex substring match, totaling 6 tests."}

{"answer": "2, 1", "explanation": "The DataProvider supplies two cases (1 and -1); the assertion $x > 0 passes for 1 but fails for -1, giving 2 ran and 1 failed."}

{"answer": "POST", "explanation": "The -d flag in curl sends data in the request body and automatically switches the HTTP method to POST."}

{"answer": "GET", "explanation": "The -G flag forces curl to use the GET method, placing the -d data into the query string rather than the request body."}

{"answer": "invalid_client", "explanation": "RFC 6749 §5.2 specifies that a non-existent or invalid client_id at the token endpoint results in the error 'invalid_client'."}

{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the authorization server returns the access token in the URI fragment (the part after '#') of the redirect_uri."}

{"answer": 0, "explanation": "The default filter only substitutes for null/undefined values, not falsy values like false, so false|default(2) yields false, and false * 3 equals 0."}

{"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than ~, so the expression is evaluated as 'a' ~ (1+2) = 'a' ~ 3 = 'a3'."}

{"answer": 0, "explanation": "The array [''] has one element, so it is not considered blank by Assert\\NotBlank, resulting in zero violations."}

{"answer": "Symfony\\Component\\Form\\Exception\\LogicException", "explanation": "Calling isValid() on a Symfony form that has not been submitted throws a LogicException, which is caught and its class name is echoed."}

{"answer": "same", "explanation": "Symfony DI container services are singletons by default, so calling get('a') twice returns the same stdClass instance with the same spl_object_id."}

{"answer": "hi Bob!", "explanation": "Symfony's DI container resolves nested parameter references: %name% → 'Bob', %greeting% → 'hi Bob', and %greeting%! → 'hi Bob!'."}

{"answer": "960px", "explanation": "In Bootstrap 5.3, at the ≥992px (lg) breakpoint, .container has a max-width of 960px."}

{"answer": "text-danger", "explanation": "In Bootstrap 5.3's compiled CSS, .text-danger is defined after .text-primary (following the theme color order: primary, secondary, success, danger, …), so with equal specificity the later rule (.text-danger) wins."}

{"answer": 2, "explanation": "The class is in Domain but depends on Application (PlaceOrder) and Infrastructure (Db), both of which violate the rule that Domain may only depend on Domain."}

{"answer": 3, "explanation": "The class is in the Domain layer, which may only depend on Domain; its references to App\\Application\\PlaceOrder, App\\Infrastructure\\Db, and App\\Infrastructure\\Logger each constitute one violation."}

{"answer": "10,15", "explanation": "$a has amount 10, $c is a new Money object with amount 10+5=15, so the output is '10,15'."}

{"answer": 1, "explanation": "The remove() method throws a DomainException before unsetting the item because it's the only one, so the items array still contains one entry and count() returns 1."}

{"answer": "hi", "explanation": "The code instantiates class C, calls its hi() method which returns the string 'hi', and echoes it."}

{"answer": "yesno", "explanation": "Before property access the lazy ghost is uninitialized (prints 'yes'), and after accessing $o->v the ghost is initialized (prints 'no')."}

{"answer": "no", "explanation": "The Security Guard component (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so on Symfony 8.1 the class does not exist and class_exists() returns false."}

{"answer": "noyes", "explanation": "AnnotationClassLoader was removed in Symfony 7.0 (deprecated in 6.3), while AttributeClassLoader is its replacement that exists in 8.1."}