-administrator-needs-to-revoke-a-token-but-wants-to-keep-a-dc0lb","questionText":"An administrator needs to revoke a token but wants to keep all child tokens that were created using this token as the parent. Which revocation operation should be used?","explanation":"Orphan token revocation is the correct operation because it revokes the parent token while preserving all child tokens that were created using it. This is achieved by removing the parent token's accessor and its associated policies, but leaving the child tokens' hierarchy intact so they continue to function independently. In Vault, this is done via the `vault token revoke -orphan` command or the corresponding API endpoint.","domainId":"5f8c426a-c15a-4919-a3a5-861ba6d98dc4","difficulty":"easy","questionType":"multiple_choice","pbqConfig":null,"exhibitText":null,"options":[{"id":"a1952ea3-9947-4d6c-8db0-2c7201bb4d34","label":null,"text":"Orphan token revocation","isCorrect":true},{"id":"d9cdc04a-1cd8-4693-9753-c7e8b30059ec","label":null,"text":"Immediate token revocation","isCorrect":false},{"id":"549e8220-72dc-48ea-bc9e-29c4acc00af1","label":null,"text":"Sudo token revocation","isCorrect":false},{"id":"2c129e31-ab56-43af-a09f-b1b0ac9edfe8","label":null,"text":"Self token revocation","isCorrect":false}],"domainName":"Assess Vault tokens","domainSlug":"vault-tokens"},{"id":"20b551d6-85f5-4b00-a901-cd7ef9a52a39","slug":"which-two-commands-can-be-used-to-manually-revoke-leases-c-yh9ps","questionText":"Which two commands can be used to manually revoke leases? (Choose two.)","explanation":"Option C, `vault lease revoke `, is correct because it directly revokes a single lease by its lease ID, immediately invalidating the associated secret and removing it from Vault's lease tracking. Option E, `vault lease revoke -prefix `, is correct because the `-prefix` flag revokes all leases whose IDs begin with the given prefix, enabling bulk revocation of leases under a path or hierarchy. Option A, `vault secrets disable `, is not a lease-revocation command; it disables a secrets engine at the given path, which revokes leases as a side effect but is not the manual lease-revocation operation asked for. Option B, `vault token revoke `, revokes a token and its child tokens, not leases directly. Option D, `vault lease renew `, extends a lease's TTL rather than revoking it.","domainId":"5776f619-2000-44af-86a7-916a40371830","difficulty":"medium","questionType":"multi_select","pbqConfig":null,"exhibitText":null,"options":[{"id":"db2ad684-6ed4-4e0c-ba34-f336161a70f1","label":null,"text":"vault secrets disable ","isCorrect":false},{"id":"79329b61-de5b-49b8-ab39-37971c8d631f","label":null,"text":"vault token revoke ","isCorrect":false},{"id":"44bc8610-5de1-46a5-9fe6-69a90b316a0f","label":null,"text":"vault lease revoke ","isCorrect":true},{"id":"080e8a2c-1133-49e8-b4ff-c656f1a2c78f","label":null,"text":"vault lease renew ","isCorrect":false},{"id":"03885689-e22c-48af-bc7e-f69bc8239c7d","label":null,"text":"vault lease revoke -prefix ","isCorrect":true}],"domainName":"Manage Vault leases","domainSlug":"vault-leases"},{"id":"026f8f9a-3d15-4fd5-9e17-174a7e29876a","slug":"a-small-startup-wants-to-run-vault-in-a-development-environm-a4mkh","questionText":"A small startup wants to run Vault in a development environment with minimal operational overhead. They need to store secrets in memory only, without any persistence. Which storage backend should they choose?","explanation":"The in-memory storage backend stores all data in RAM with no persistence to disk, making it ideal for development environments where secrets must be lost on restart and operational overhead must be minimized. It requires no configuration, no external dependencies, and no data management, perfectly matching the requirement for minimal overhead and memory-only storage.","domainId":"6d89e6db-fb1e-426e-9c2e-544677dad89c","difficulty":"easy","questionType":"multiple_choice","pbqConfig":null,"exhibitText":null,"options":[{"id":"6044466b-4325-496