Microsoft AZ-500 Practice Test 89
Question 880
An organization has rotation requirements but relies on operators manually copying keys from a spreadsheet. A review identifies this consequence: Rotating a key without checking version-pinned consumers may interrupt encryption-dependent workloads. What is the BEST controlled recovery once this failure is recognized?
- The controlled remediation is to assume a new key version is automatically used by every explicitly version-pinned client.
- The controlled remediation is to delete all old key versions before confirming dependent data can be decrypted.
- The controlled remediation is to share private key material in email to coordinate rotation.
- The controlled remediation is to apply approved rotation and validate service continuity and rollback controls.
Explanation
Correct Answer
D:Managed key rotation can generate new key versions but clients and services must handle the intended version behavior. Test using these records: Key rotation policy, current key versions, expiry, dependent resource key URI and operation logs.
Incorrect Answers
A:Assume a new key version is automatically used by every explicitly version-pinned client. This would not reliably restore the intended security boundary. Rotating a key without checking version-pinned consumers may interrupt encryption-dependent workloads. The appropriate controlled recovery is: Apply approved rotation and validate service continuity and rollback controls.
B:Delete all old key versions before confirming dependent data can be decrypted. This would not reliably restore the intended security boundary. Rotating a key without checking version-pinned consumers may interrupt encryption-dependent workloads. The appropriate controlled recovery is: Apply approved rotation and validate service continuity and rollback controls.
C:Share private key material in email to coordinate rotation. This would not reliably restore the intended security boundary. Rotating a key without checking version-pinned consumers may interrupt encryption-dependent workloads. The appropriate controlled recovery is: Apply approved rotation and validate service continuity and rollback controls.
Question 881
A TLS certificate renewal process confuses a certificate object with the secret holding its exportable representation. What is the BEST supported implementation or corrective action?
- Use the correct Key Vault key, secret or certificate object and enforce its intended lifecycle and operations.
- Treat an arbitrary secret string as proof of a managed X.509 certificate lifecycle.
- Grant every application secret-get rights to read a private signing key.
- Assume certificate renewal automatically rotates all unrelated encryption keys.
Explanation
Correct Answer
A:Confirm the change against these records: Object type, supported cryptographic operation, certificate policy, access scope and renewal event. This directly addresses Key Vault secret certificate and key lifecycle.
Incorrect Answers
B:Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. Treat an arbitrary secret string as proof of a managed X.509 certificate lifecycle.
C:Grant every application secret-get rights to read a private signing key. The proposed change targets the wrong mechanism or lacks essential validation. Key Vault keys, secrets and certificates support different management and cryptographic usage patterns. Relevant evidence is object type, supported cryptographic operation, certificate policy, access scope and renewal event.
D:Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. The intended action is: Use the correct Key Vault key, secret or certificate object and enforce its intended lifecycle and operations.
Question 882
A TLS certificate renewal process confuses a certificate object with the secret holding its exportable representation. Which evidence BEST verifies the intended technical behavior?
- A connected agent indicator without a matching data collection rule or event record.
- An incident title without its actual source telemetry and detection results.
- A planned Azure Policy assignment without evaluated compliance or deployment evidence.
- Object type, supported cryptographic operation, certificate policy, access scope and renewal event.
Explanation
Correct Answer
D:These records test the actual Key Vault secret certificate and key lifecycle behavior rather than an unrelated dashboard state. Key Vault keys, secrets and certificates support different management and cryptographic usage patterns.
Incorrect Answers
A:On its own, that evidence does not prove the specified security control works. The more relevant observations are: Object type, supported cryptographic operation, certificate policy, access scope and renewal event.
B:On its own, that evidence does not prove the specified security control works. Key Vault keys, secrets and certificates support different management and cryptographic usage patterns.
C:On its own, that evidence does not prove the specified security control works. In the given case, a TLS certificate renewal process confuses a certificate object with the secret holding its exportable representation.
Question 883
A TLS certificate renewal process confuses a certificate object with the secret holding its exportable representation. Which principle BEST explains why the recommended solution is appropriate?
- Turning off an alert source is equivalent to remediating the underlying threat.
- Key Vault keys, secrets and certificates support different management and cryptographic usage patterns.
- Assigning a policy automatically remediates all existing resources under every effect.
- A subscribed cloud asset automatically sends all possible security logs to Microsoft Sentinel.
Explanation
Correct Answer
B:Confirmation depends on Object type, supported cryptographic operation, certificate policy, access scope and renewal event. This principle supports the security response: Use the correct Key Vault key, secret or certificate object and enforce its intended lifecycle and operations.
Incorrect Answers
A:Turning off an alert source is equivalent to remediating the underlying threat. This is an incorrect assumption for Key Vault secret certificate and key lifecycle. The relevant security behavior is: Key Vault keys, secrets and certificates support different management and cryptographic usage patterns. Check evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
C:Assigning a policy automatically remediates all existing resources under every effect. This is an incorrect assumption for Key Vault secret certificate and key lifecycle. The relevant security behavior is: Key Vault keys, secrets and certificates support different management and cryptographic usage patterns. Check evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
D:A subscribed cloud asset automatically sends all possible security logs to Microsoft Sentinel. This is an incorrect assumption for Key Vault secret certificate and key lifecycle. The relevant security behavior is: Key Vault keys, secrets and certificates support different management and cryptographic usage patterns. Check evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
Question 884
A TLS certificate renewal process confuses a certificate object with the secret holding its exportable representation. Suppose the operator instead follows this unsafe shortcut: Treat an arbitrary secret string as proof of a managed X.509 certificate lifecycle. What is the MOST significant failure introduced by that shortcut?
- Running a scoped compliance assessment automatically deletes protected resources.
- Maintaining the required incident log is itself the unauthorized API request.
- Storing sensitive signing material as a broadly readable secret can violate nonexportability goals.
- A successful remediation test was the original reason the plan was disabled.
Explanation
Correct Answer
C:The suitable control is: Use the correct Key Vault key, secret or certificate object and enforce its intended lifecycle and operations. This is a material consequence of the incorrect shortcut.
Incorrect Answers
A:Running a scoped compliance assessment automatically deletes protected resources. This does not explain the real Key Vault secret certificate and key lifecycle weakness after the shortcut. The material failure is: Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. Inspect evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
B:Maintaining the required incident log is itself the unauthorized API request. This does not explain the real Key Vault secret certificate and key lifecycle weakness after the shortcut. The material failure is: Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. Inspect evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
D:A successful remediation test was the original reason the plan was disabled. This does not explain the real Key Vault secret certificate and key lifecycle weakness after the shortcut. The material failure is: Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. Inspect evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
Question 885
A TLS certificate renewal process confuses a certificate object with the secret holding its exportable representation. A review identifies this consequence: Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. What is the BEST controlled recovery once this failure is recognized?
- Grant every application secret-get rights to read a private signing key.
- Migrate to the appropriate object and verify only authorized sign, decrypt or secret-read behavior.
- Assume certificate renewal automatically rotates all unrelated encryption keys.
- Treat an arbitrary secret string as proof of a managed X.509 certificate lifecycle.
Explanation
Correct Answer
B:Test using these records: Object type, supported cryptographic operation, certificate policy, access scope and renewal event. This addresses the observed security problem while providing a verifiable outcome.
Incorrect Answers
A:Grant every application secret-get rights to read a private signing key. This would not reliably restore the intended security boundary. Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. The appropriate controlled recovery is: Migrate to the appropriate object and verify only authorized sign, decrypt or secret-read behavior.
C:Assume certificate renewal automatically rotates all unrelated encryption keys. This would not reliably restore the intended security boundary. Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. The appropriate controlled recovery is: Migrate to the appropriate object and verify only authorized sign, decrypt or secret-read behavior.
D:Treat an arbitrary secret string as proof of a managed X.509 certificate lifecycle. This would not reliably restore the intended security boundary. Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. The appropriate controlled recovery is: Migrate to the appropriate object and verify only authorized sign, decrypt or secret-read behavior.
Question 886
An Azure workload needs a nonexportable signing key but a team stores the key bytes as an ordinary application secret. Which configuration decision MOST directly resolves the issue?
- For this Azure workload, the team should grant every application secret-get rights to read a private signing key.
- For this Azure workload, the team should assume certificate renewal automatically rotates all unrelated encryption keys.
- For this Azure workload, the team should use the correct Key Vault key, secret or certificate object and enforce its intended lifecycle and operations.
- For this Azure workload, the team should treat an arbitrary secret string as proof of a managed X.509 certificate lifecycle.
Explanation
Correct Answer
C:Confirm the change against these records: Object type, supported cryptographic operation, certificate policy, access scope and renewal event. Key Vault keys, secrets and certificates support different management and cryptographic usage patterns.
Incorrect Answers
A:Grant every application secret-get rights to read a private signing key. The proposed change targets the wrong mechanism or lacks essential validation. Key Vault keys, secrets and certificates support different management and cryptographic usage patterns. Relevant evidence is object type, supported cryptographic operation, certificate policy, access scope and renewal event.
B:Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. In the given case, an Azure workload needs a nonexportable signing key but a team stores the key bytes as an ordinary application secret.
D:In the given case, an Azure workload needs a nonexportable signing key but a team stores the key bytes as an ordinary application secret.
Question 887
An Azure workload needs a nonexportable signing key but a team stores the key bytes as an ordinary application secret. What evidence most directly confirms the intended security behavior?
- In this security review, examine an inventory item list from a different subscription or connected cloud account.
- In this security review, examine a connected agent indicator without a matching data collection rule or event record.
- In this security review, examine object type, supported cryptographic operation, certificate policy, access scope and renewal event.
- In this security review, examine an incident title without its actual source telemetry and detection results.
Explanation
Correct Answer
C:These records test the actual Key Vault secret certificate and key lifecycle behavior rather than an unrelated dashboard state. The intended action is: Use the correct Key Vault key, secret or certificate object and enforce its intended lifecycle and operations.
Incorrect Answers
A:On its own, that evidence does not prove the specified security control works. In the given case, an Azure workload needs a nonexportable signing key but a team stores the key bytes as an ordinary application secret.
B:The more relevant observations are: Object type, supported cryptographic operation, certificate policy, access scope and renewal event.
D:Key Vault keys, secrets and certificates support different management and cryptographic usage patterns.
Question 888
An Azure workload needs a nonexportable signing key but a team stores the key bytes as an ordinary application secret. Which security principle best explains the intended decision?
- The applicable security principle is that Key Vault keys, secrets and certificates support different management and cryptographic usage patterns.
- The applicable security principle is that a subscribed cloud asset automatically sends all possible security logs to Microsoft Sentinel.
- The applicable security principle is that turning off an alert source is equivalent to remediating the underlying threat.
- The applicable security principle is that a published security standard alone grants managed identities permission to change resources.
Explanation
Correct Answer
A:Confirmation depends on Object type, supported cryptographic operation, certificate policy, access scope and renewal event.
Incorrect Answers
B:A subscribed cloud asset automatically sends all possible security logs to Microsoft Sentinel. This is an incorrect assumption for Key Vault secret certificate and key lifecycle. The relevant security behavior is: Key Vault keys, secrets and certificates support different management and cryptographic usage patterns. Check evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
C:Turning off an alert source is equivalent to remediating the underlying threat. This is an incorrect assumption for Key Vault secret certificate and key lifecycle. The relevant security behavior is: Key Vault keys, secrets and certificates support different management and cryptographic usage patterns. Check evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
D:A published security standard alone grants managed identities permission to change resources. This is an incorrect assumption for Key Vault secret certificate and key lifecycle. The relevant security behavior is: Key Vault keys, secrets and certificates support different management and cryptographic usage patterns. Check evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
Question 889
An Azure workload needs a nonexportable signing key but a team stores the key bytes as an ordinary application secret. Suppose the operator instead follows this unsafe shortcut: Treat an arbitrary secret string as proof of a managed X.509 certificate lifecycle. Which resulting risk or fault should the reviewer identify?
- The resulting security weakness is that a successful remediation test was the original reason the plan was disabled.
- The resulting security weakness is that documenting an approved policy assignment is the cause of its earlier absence.
- The resulting security weakness is that maintaining the required incident log is itself the unauthorized API request.
- The resulting security weakness is that storing sensitive signing material as a broadly readable secret can violate nonexportability goals.
Explanation
Correct Answer
D:The suitable control is: Use the correct Key Vault key, secret or certificate object and enforce its intended lifecycle and operations. Key Vault keys, secrets and certificates support different management and cryptographic usage patterns.
Incorrect Answers
A:A successful remediation test was the original reason the plan was disabled. This does not explain the real Key Vault secret certificate and key lifecycle weakness after the shortcut. The material failure is: Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. Inspect evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
B:Documenting an approved policy assignment is the cause of its earlier absence. This does not explain the real Key Vault secret certificate and key lifecycle weakness after the shortcut. The material failure is: Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. Inspect evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
C:Maintaining the required incident log is itself the unauthorized API request. This does not explain the real Key Vault secret certificate and key lifecycle weakness after the shortcut. The material failure is: Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. Inspect evidence such as object type, supported cryptographic operation, certificate policy, access scope and renewal event.
Question 890
An Azure workload needs a nonexportable signing key but a team stores the key bytes as an ordinary application secret. A review identifies this consequence: Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. Which remediation most directly restores the intended behavior?
- The controlled remediation is to assume certificate renewal automatically rotates all unrelated encryption keys.
- The controlled remediation is to migrate to the appropriate object and verify only authorized sign, decrypt or secret-read behavior.
- The controlled remediation is to treat an arbitrary secret string as proof of a managed X.509 certificate lifecycle.
- The controlled remediation is to grant every application secret-get rights to read a private signing key.
Explanation
Correct Answer
B:Test using these records: Object type, supported cryptographic operation, certificate policy, access scope and renewal event. Key Vault keys, secrets and certificates support different management and cryptographic usage patterns.
Incorrect Answers
A:Assume certificate renewal automatically rotates all unrelated encryption keys. This would not reliably restore the intended security boundary. Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. The appropriate controlled recovery is: Migrate to the appropriate object and verify only authorized sign, decrypt or secret-read behavior.
C:Treat an arbitrary secret string as proof of a managed X.509 certificate lifecycle. This would not reliably restore the intended security boundary. Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. The appropriate controlled recovery is: Migrate to the appropriate object and verify only authorized sign, decrypt or secret-read behavior.
D:Grant every application secret-get rights to read a private signing key. This would not reliably restore the intended security boundary. Storing sensitive signing material as a broadly readable secret can violate nonexportability goals. The appropriate controlled recovery is: Migrate to the appropriate object and verify only authorized sign, decrypt or secret-read behavior.