Question 671 of 997
Implement Azure securitymediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to rotate the secret immediately after disabling it. Disabling a secret in Azure Key Vault prevents new retrieval requests, but it does not invalidate copies already cached by applications; those cached secrets remain usable until the cache expires or is manually refreshed. Rotating the secret changes its value, so any application attempting to use the old cached copy will fail authentication against the vault, effectively invalidating cached copies on demand. On the AZ-204 exam, this scenario tests your understanding that disabling and rotating are complementary actions—disabling blocks new access, while rotation forces cached credentials to become obsolete. A common trap is assuming disabling alone is sufficient, but the exam emphasizes that cached copies persist until the secret’s value changes. Memory tip: “Disable to stop new, rotate to kill the old.”

AZ-204 Implement Azure security Practice Question

This AZ-204 practice question tests your understanding of implement azure security. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Your company stores secrets in Azure Key Vault. You need to ensure that when a secret is disabled, it does not become accessible to applications that already have a cached copy. Which additional step must you take?

Question 1mediummultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Rotate the secret immediately

When a secret is disabled in Azure Key Vault, the vault itself will reject new access requests, but applications that have already retrieved and cached the secret can continue using it until the cache expires or is refreshed. To immediately invalidate the cached copy, you must rotate the secret (change its value) so that any subsequent attempt to use the old cached value fails because it no longer matches the secret stored in Key Vault. Disabling alone does not force applications to re-authenticate or re-fetch; rotation ensures the cached value becomes obsolete.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Rotate the secret immediately

    Why this is correct

    Rotating changes the secret value, thus invalidating any cached copies held by applications.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Delete the secret

    Why it's wrong here

    Deleting the secret will cause new requests to fail, but cached copies remain valid until they expire or are refreshed.

  • Enable soft-delete and purge protection

    Why it's wrong here

    Soft-delete and purge protection prevent permanent deletion but do not invalidate cached secret values.

  • Use Key Vault access policies to deny access

    Why it's wrong here

    Access policies control who can read the secret; they do not affect cached values already held by applications.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume disabling a secret immediately revokes all access, but they overlook the fact that applications may hold a cached copy that remains valid until the cache expires or the secret is rotated.

Detailed technical explanation

How to think about this question

Under the hood, Azure Key Vault does not push cache invalidation events to clients; it relies on the client’s cache TTL (typically 5 minutes for the REST API, but configurable). Rotating the secret changes its value in the vault, so any cached copy becomes stale—applications must fetch the new version to succeed. In practice, many organizations combine rotation with a versioned secret URI (e.g., `https://myvault.vault.azure.net/secrets/mysecret/version`) to force clients to always retrieve the latest version, but rotation is the explicit action that breaks the cached value.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related AZ-204 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-204 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-204 question test?

Implement Azure security — This question tests Implement Azure security — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Rotate the secret immediately — When a secret is disabled in Azure Key Vault, the vault itself will reject new access requests, but applications that have already retrieved and cached the secret can continue using it until the cache expires or is refreshed. To immediately invalidate the cached copy, you must rotate the secret (change its value) so that any subsequent attempt to use the old cached value fails because it no longer matches the secret stored in Key Vault. Disabling alone does not force applications to re-authenticate or re-fetch; rotation ensures the cached value becomes obsolete.

What should I do if I get this AZ-204 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.