Question 450A public HTTPS service is expiring because each administrator maintains a separate spreadsheet of TLS certificate dates. Which technical distinction is decisive in this case? Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. Central certificate storage and lifecycle metadata enable controlled tracking of expirations and replacement. Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. Key Vault separates secret storage and access authorization from application code and deployment artifacts. ExplanationCorrect Answer B:Central certificate storage and lifecycle metadata enable controlled tracking of expirations and replacement. This is the principle behind: Use Azure Key Vault certificate management and configured notification or renewal workflows where supported. The evidence to inspect is: Inspect the certificate expiration event and confirm the service is updated with a valid replacement. Other Answers A:Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. By contrast, central certificate storage and lifecycle metadata enable controlled tracking of expirations and replacement. C:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. By contrast, central certificate storage and lifecycle metadata enable controlled tracking of expirations and replacement. D:Key Vault separates secret storage and access authorization from application code and deployment artifacts. In the stated system, central certificate storage and lifecycle metadata enable controlled tracking of expirations and replacement.
Question 451A public HTTPS service is expiring because each administrator maintains a separate spreadsheet of TLS certificate dates. Which observation best validates the chosen approach? Rotate the test secret and confirm the application retrieves the authorized version without a code change. Inspect the certificate expiration event and confirm the service is updated with a valid replacement. Delete a controlled test secret and verify restoration while an unauthorized purge cannot bypass policy. Verify a reader retrieves the approved secret and receives a denial when attempting to delete one. ExplanationCorrect Answer B:Inspect the certificate expiration event and confirm the service is updated with a valid replacement. This test checks the expected result of: Use Azure Key Vault certificate management and configured notification or renewal workflows where supported. It matters because: Central certificate storage and lifecycle metadata enable controlled tracking of expirations and replacement. Other Answers A:Key Vault separates secret storage and access authorization from application code and deployment artifacts. A more meaningful verification is to inspect the certificate expiration event and confirm the service is updated with a valid replacement. C:Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. The failure is checked more directly by a test to inspect the certificate expiration event and confirm the service is updated with a valid replacement. D:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. Proving this correction calls for a check to inspect the certificate expiration event and confirm the service is updated with a valid replacement.
Question 452A public HTTPS service is expiring because each administrator maintains a separate spreadsheet of TLS certificate dates. Which governance action most directly addresses the recurring risk? Use managed identities and secret-rotation procedures for application credentials. Review Key Vault access scopes and privilege changes during identity recertification. Assign ownership and monitoring to every production certificate backed by Key Vault. Require vault recovery settings and retention compliance checks during provisioning. ExplanationCorrect Answer C:Assign ownership and monitoring to every production certificate backed by Key Vault. Maintaining this control reduces recurrence because: Central certificate storage and lifecycle metadata enable controlled tracking of expirations and replacement. The immediate response remains: Use Azure Key Vault certificate management and configured notification or renewal workflows where supported. Other Answers A:Key Vault separates secret storage and access authorization from application code and deployment artifacts. The stronger recurring control is to assign ownership and monitoring to every production certificate backed by Key Vault. B:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. The lasting safeguard is to assign ownership and monitoring to every production certificate backed by Key Vault. D:Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. A more direct preventive measure is to assign ownership and monitoring to every production certificate backed by Key Vault.
Question 453A finance application can read a secret from Key Vault but a help desk role can also delete all vault objects through an overly broad data-plane grant. Which action most directly resolves the security or identity requirement? Narrow the inbound NSG rules to permitted sources, ports, and priorities for that subnet or interface. Enable the appropriate Key Vault soft-delete and purge-protection safeguards for required recovery objectives. Store the secret in Azure Key Vault and use an authorized application identity to retrieve its current value. Apply least-privilege Key Vault data access with the appropriate RBAC roles or supported permissions model. ExplanationCorrect Answer D:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. To confirm, verify a reader retrieves the approved secret and receives a denial when attempting to delete one. Other Answers A:NSGs apply stateful network access filtering independently of directory privileges on a resource. The corrective action for this requirement is to apply least-privilege Key Vault data access with the appropriate RBAC roles or supported permissions model. B:Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. A more relevant action is to apply least-privilege Key Vault data access with the appropriate RBAC roles or supported permissions model. C:Key Vault separates secret storage and access authorization from application code and deployment artifacts. This failure calls for a decision to apply least-privilege Key Vault data access with the appropriate RBAC roles or supported permissions model.
Question 454A finance application can read a secret from Key Vault but a help desk role can also delete all vault objects through an overly broad data-plane grant. Which technical distinction is decisive in this case? Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. NSGs apply stateful network access filtering independently of directory privileges on a resource. Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. Key Vault separates secret storage and access authorization from application code and deployment artifacts. ExplanationCorrect Answer C:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. This is the principle behind: Apply least-privilege Key Vault data access with the appropriate RBAC roles or supported permissions model. The evidence to inspect is: Verify a reader retrieves the approved secret and receives a denial when attempting to delete one. Other Answers A:Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. By contrast, permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. B:NSGs apply stateful network access filtering independently of directory privileges on a resource. In the stated system, permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. D:Key Vault separates secret storage and access authorization from application code and deployment artifacts. In the stated system, permissions to retrieve secrets and permissions to administer or delete vault objects can be separated.
Question 455A finance application can read a secret from Key Vault but a help desk role can also delete all vault objects through an overly broad data-plane grant. Which observation best validates the chosen approach? Delete a controlled test secret and verify restoration while an unauthorized purge cannot bypass policy. Rotate the test secret and confirm the application retrieves the authorized version without a code change. Verify a reader retrieves the approved secret and receives a denial when attempting to delete one. From permitted and unpermitted test clients, compare effective NSG rules and actual connection results. ExplanationCorrect Answer C:Verify a reader retrieves the approved secret and receives a denial when attempting to delete one. This test checks the expected result of: Apply least-privilege Key Vault data access with the appropriate RBAC roles or supported permissions model. It matters because: Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. Other Answers A:Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. Proving this correction calls for a check to verify a reader retrieves the approved secret and receives a denial when attempting to delete one. B:Key Vault separates secret storage and access authorization from application code and deployment artifacts. The relevant acceptance check is to verify a reader retrieves the approved secret and receives a denial when attempting to delete one. D:NSGs apply stateful network access filtering independently of directory privileges on a resource. A more meaningful verification is to verify a reader retrieves the approved secret and receives a denial when attempting to delete one.
Question 456A finance application can read a secret from Key Vault but a help desk role can also delete all vault objects through an overly broad data-plane grant. Which governance action most directly addresses the recurring risk? Review Key Vault access scopes and privilege changes during identity recertification. Use managed identities and secret-rotation procedures for application credentials. Require vault recovery settings and retention compliance checks during provisioning. Regularly audit broad allow rules and rule priorities against the approved network inventory. ExplanationCorrect Answer A:Review Key Vault access scopes and privilege changes during identity recertification. Maintaining this control reduces recurrence because: Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. The immediate response remains: Apply least-privilege Key Vault data access with the appropriate RBAC roles or supported permissions model. Other Answers B:Key Vault separates secret storage and access authorization from application code and deployment artifacts. A more direct preventive measure is to review Key Vault access scopes and privilege changes during identity recertification. C:Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. The stronger recurring control is to review Key Vault access scopes and privilege changes during identity recertification. D:NSGs apply stateful network access filtering independently of directory privileges on a resource. Reducing this risk requires a practice to review Key Vault access scopes and privilege changes during identity recertification.
Question 457A development vault is reachable from arbitrary networks despite storing sensitive production integration secrets. Which action most directly resolves the security or identity requirement? Configure a supported Azure Private Endpoint and corresponding private DNS resolution plus resource access restrictions. Configure supported virtual network peering and authorize only the required cross-network connections. Configure supported Key Vault network restrictions or private connectivity in addition to identity access controls. Apply least-privilege Key Vault data access with the appropriate RBAC roles or supported permissions model. ExplanationCorrect Answer C:Network access rules constrain the path to a vault while authorization still governs what an identity can do. To confirm, attempt retrieval from an unapproved network and an authorized private path with appropriately scoped identities. Other Answers A:Private Link exposes a service through a private IP in a virtual network, unlike mere encryption of public traffic. The required change instead is to configure supported Key Vault network restrictions or private connectivity in addition to identity access controls. B:VNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. The required change instead is to configure supported Key Vault network restrictions or private connectivity in addition to identity access controls. D:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. A more relevant action is to configure supported Key Vault network restrictions or private connectivity in addition to identity access controls.
Question 458A development vault is reachable from arbitrary networks despite storing sensitive production integration secrets. Which technical distinction is decisive in this case? Private Link exposes a service through a private IP in a virtual network, unlike mere encryption of public traffic. VNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. Network access rules constrain the path to a vault while authorization still governs what an identity can do. Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. ExplanationCorrect Answer C:Network access rules constrain the path to a vault while authorization still governs what an identity can do. This is the principle behind: Configure supported Key Vault network restrictions or private connectivity in addition to identity access controls. The evidence to inspect is: Attempt retrieval from an unapproved network and an authorized private path with appropriately scoped identities. Other Answers A:Private Link exposes a service through a private IP in a virtual network, unlike mere encryption of public traffic. By contrast, network access rules constrain the path to a vault while authorization still governs what an identity can do. B:VNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. By contrast, network access rules constrain the path to a vault while authorization still governs what an identity can do. D:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. In the stated system, network access rules constrain the path to a vault while authorization still governs what an identity can do.
Question 459A development vault is reachable from arbitrary networks despite storing sensitive production integration secrets. Which observation best validates the chosen approach? Verify a reader retrieves the approved secret and receives a denial when attempting to delete one. Attempt retrieval from an unapproved network and an authorized private path with appropriately scoped identities. Resolve the storage name from an approved client and verify it reaches the private endpoint while unwanted public access is denied. Test traffic between approved private addresses and verify the expected routes and access rules. ExplanationCorrect Answer B:Attempt retrieval from an unapproved network and an authorized private path with appropriately scoped identities. This test checks the expected result of: Configure supported Key Vault network restrictions or private connectivity in addition to identity access controls. It matters because: Network access rules constrain the path to a vault while authorization still governs what an identity can do. Other Answers A:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. Proving this correction calls for a check to attempt retrieval from an unapproved network and an authorized private path with appropriately scoped identities. C:Private Link exposes a service through a private IP in a virtual network, unlike mere encryption of public traffic. The failure is checked more directly by a test to attempt retrieval from an unapproved network and an authorized private path with appropriately scoped identities. D:VNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. The failure is checked more directly by a test to attempt retrieval from an unapproved network and an authorized private path with appropriately scoped identities.
Question 460A development vault is reachable from arbitrary networks despite storing sensitive production integration secrets. Which governance action most directly addresses the recurring risk? Maintain private DNS and endpoint approval tests across network changes. Document peering relationships, address-space conflicts, and reciprocal approvals before deployment. Review Key Vault access scopes and privilege changes during identity recertification. Test network ACL and private endpoint settings whenever vault connectivity changes. ExplanationCorrect Answer D:Test network ACL and private endpoint settings whenever vault connectivity changes. Maintaining this control reduces recurrence because: Network access rules constrain the path to a vault while authorization still governs what an identity can do. The immediate response remains: Configure supported Key Vault network restrictions or private connectivity in addition to identity access controls. Other Answers A:Private Link exposes a service through a private IP in a virtual network, unlike mere encryption of public traffic. The lasting safeguard is to test network ACL and private endpoint settings whenever vault connectivity changes. B:VNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. The lasting safeguard is to test network ACL and private endpoint settings whenever vault connectivity changes. C:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. The stronger recurring control is to test network ACL and private endpoint settings whenever vault connectivity changes.