You save $69.98
AZ-305 Premium Bundle
- Premium File 382 Questions & Answers
- Last Update: Nov 20, 2026
- Training Course 87 Lectures
- Study Guide 933 Pages
You save $69.98
For the RBAC custom role requirement, the proposed architecture uses: Create a least-privilege custom Azure RBAC role and assign it at minimal scope. Why does that design fit?
Custom role actions can grant specific management operations without broad Contributor rights. It is material here because a service team needs a narrow set of resource restart and read operations absent from built-in roles.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. That statement describes Management group hierarchy, while the question asks how RBAC custom role works: Custom role actions can grant specific management operations without broad Contributor rights.
Azure Policy can deny targeted resource types without revoking all contributor operations. Custom role actions can grant specific management operations without broad Contributor rights.
Policy deny or audit effects can enforce required metadata at supported resource scopes. It belongs to Required tag policy. The stated architecture instead relies on: Custom role actions can grant specific management operations without broad Contributor rights.
The team has justified its Azure Data Explorer telemetry design with: Consider Azure Data Explorer with appropriate ingestion, partitioning and KQL queries. Which statement accurately describes why the approach works?
Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL. It is material here because a security team needs interactive time-series queries across petabytes of ingested machine events.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL.
Stream Analytics supports SQL-like processing over streaming sources with time windows. Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL.
Mapping data flows transform data on managed Spark compute from graphical mappings. That statement describes ADF mapping data flow, while the question asks how Azure Data Explorer telemetry works: Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL.
Architecture review: App Service isolation and Dedicated host. Requirement A: A regulated web application needs private dedicated hosting and stricter network isolation. Requirement B: A regulated app requires a physically dedicated server host for VM placement and host-level isolation. Which complete two-part proposal satisfies both constraints?
For requirement A, ASE provides dedicated App Service hosting in a customer virtual-network environment. For requirement B, dedicated Host provides physical host isolation with separate placement and pricing controls. Verify both independently: The app operates in the required isolated hosting boundary and passes private connectivity tests; The deployed VMs are listed on the reserved dedicated host.
The option covers one requirement but substitutes Azure HPC design for Dedicated host. The missing acceptance result is: The deployed VMs are listed on the reserved dedicated host.
Dedicated Host provides physical host isolation with separate placement and pricing controls. The other proposed action (use Durable Functions orchestration with proper idempotent activity design) does not implement the first control. ASE provides dedicated App Service hosting in a customer virtual-network environment.
This combines Azure Functions durable workflow and Azure HPC design, which do not satisfy the distinct requirements for App Service isolation and Dedicated host.
A self-managed PostgreSQL database needs transfer to Azure's managed PostgreSQL service. Which Azure architecture would most directly achieve the required result: The database app passes read/write tests against the target flexible server?
PostgreSQL migration requires extension, version and connectivity compatibility checks. The selected architecture is choose a supported PostgreSQL Flexible Server migration tool and cutover process; confirm the result by checking that the database app passes read/write tests against the target flexible server.
Replatforming changes hosting characteristics while preserving most app behavior. It does not solve the specified PostgreSQL migration condition.
Object count alone cannot establish content integrity or ACL preservation. Its design target is Storage migration validation. The stated requirement instead concerns: A self-managed PostgreSQL database needs transfer to Azure's managed PostgreSQL service.
Target compatibility determines whether code changes or a different managed target are required. The current need is: A self-managed PostgreSQL database needs transfer to Azure's managed PostgreSQL service.
Before approving Quotas and limits, the reviewer assesses this requirement: A proposed subscription hosts many public IPs and compute cores beyond regional quota. Which of the reported outcomes is decisive?
Azure service quotas are often scoped by subscription and region and can constrain deployability. Confirm using the measurable result: A capacity forecast and quota decision support the planned deployment without surprise allocation errors.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The Role assignment scope test checks the engineer can change the assigned network group but not another group's resources; the relevant outcome is A capacity forecast and quota decision support the planned deployment without surprise allocation errors.
Infrastructure as code declares desired resources and allows review and repeat deployment. The offered observation would demonstrate Standardized IaC: The same versioned module deploys matching compliant resources across test environments. The current validation is different: A capacity forecast and quota decision support the planned deployment without surprise allocation errors.
Consistent metadata simplifies inventory grouping and cost ownership without changing resources' technical capabilities. Those observations validate Resource naming governance. They do not establish the required Quotas and limits result: A capacity forecast and quota decision support the planned deployment without surprise allocation errors.
The Automated diagnostics policy review proposes: Use Azure Policy deployIfNotExists with remediation identity for supported diagnostic settings. Which Azure behavior is the technical justification for this decision?
DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. It is material here because new storage accounts across many subscriptions often appear with no diagnostic configuration.
Action groups define notifications and automated responses and can be reused by alert rules. DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. That statement describes Dynamic baseline alerts, while the question asks how Automated diagnostics policy works: DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions.
Architecture rationale review—Identity lifecycle audits: Run Microsoft Entra access reviews with suitable reviewers and removal actions. Which explanation accurately distinguishes this capability?
Access reviews periodically recertify assigned access and can remove access for denied reviews. It is material here because managers need quarterly evidence that external guest access to privileged applications is still justified.
PIM can time-bound eligible role activation with approvals MFA and justification. Access reviews periodically recertify assigned access and can remove access for denied reviews.
Management locks guard against accidental resource deletes and operate separately from authorization roles. That statement describes Resource lock constraints, while the question asks how Identity lifecycle audits works: Access reviews periodically recertify assigned access and can remove access for denied reviews.
Delegated permissions represent what an application can do on behalf of an authenticated user. Access reviews periodically recertify assigned access and can remove access for denied reviews.
For the Required tag policy requirement, the proposed architecture uses: Use an Azure Policy require-tag rule at the appropriate scope. Why does that design fit?
Policy deny or audit effects can enforce required metadata at supported resource scopes. It is material here because cost reporting is missing the billing cost center tag on newly created resources.
Infrastructure as code declares desired resources and allows review and repeat deployment. It belongs to Standardized IaC. The stated architecture instead relies on: Policy deny or audit effects can enforce required metadata at supported resource scopes.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. That statement describes Defender compliance, while the question asks how Required tag policy works: Policy deny or audit effects can enforce required metadata at supported resource scopes.
Azure service quotas are often scoped by subscription and region and can constrain deployability. Policy deny or audit effects can enforce required metadata at supported resource scopes.
A solution must address both Site-to-site VPN and Private endpoint. First requirement: A small branch needs encrypted connectivity to a VNet over its existing internet link. Second requirement: A storage service must have an address in a VNet and reject access from the public internet. Select TWO recommendations that meet these independent needs.
For the Site-to-site VPN half of this two-part design, VPN Gateway can establish encrypted IPsec tunnels over public networks. Verify: Encrypted traffic reaches the approved private Azure subnet from the branch. The other half concerns Private endpoint.
For the Private endpoint half of this design, private endpoints attach supported PaaS access to a private IP and require DNS resolution. Check: The data source resolves to a VNet private address and public access is denied. The other half concerns Site-to-site VPN.
Private DNS zone links determine name resolution for VNets that consume private endpoints. Its own validation would be: A lookup from the spoke resolves the service FQDN to the intended private IP. The current paired requirement is Site-to-site VPN and Private endpoint.
VNet peering alone is not transitive and forwarding needs explicit architecture. The corresponding task is Peering nontransitivity: Spoke A peers with the hub and spoke B peers with the same hub but cannot communicate directly. It is not one of the two requested controls (Site-to-site VPN and Private endpoint).
Private endpoints provide a private inbound path for supported App Service access. Its own validation would be: Corporate users connect using private DNS and public clients are rejected. The current paired requirement is Site-to-site VPN and Private endpoint.
The acceptance criterion for Key Vault secrets comes from this issue: A service depends on a vendor API password that rotates frequently. Which measured outcome is the strongest proof?
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. Confirm using the measurable result: The service uses the new secret version without an embedded password in deployment artifacts.
Key Vault RBAC data permissions differ from vault resource-management permissions. The offered observation would demonstrate Vault RBAC least privilege: The user retrieves authorized secret values but cannot alter vault access configuration. The current validation is different: The service uses the new secret version without an embedded password in deployment artifacts.
A user-assigned identity has a lifecycle separate from each consuming Azure resource. Those observations validate Shared workload identity. They do not establish the required Key Vault secrets result: The service uses the new secret version without an embedded password in deployment artifacts.
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. The Vault network boundary test checks a workload resolves the private vault endpoint and a public-network test cannot use the forbidden path; the relevant outcome is The service uses the new secret version without an embedded password in deployment artifacts.
To validate the SQL offline migration deployment, reviewers revisit this operational need: A small SQL database can tolerate a planned maintenance outage for cutover. What result confirms it was met?
Offline migration can simplify cutover when application downtime is acceptable. Confirm using the measurable result: The migrated database passes consistency checks before reopening writes.
Replatforming changes hosting characteristics while preserving most app behavior. Those observations validate Replatform database. They do not establish the required SQL offline migration result: The migrated database passes consistency checks before reopening writes.
Rebuild replaces the application rather than merely moving its binaries. The distinguishing check is: The migrated database passes consistency checks before reopening writes.
Hidden dependencies can break after migration even when VM replication succeeds. The offered observation would demonstrate Application dependency mapping: A test workload executes its dependent calls from the planned Azure subnet. The current validation is different: The migrated database passes consistency checks before reopening writes.
Please check your mailbox for a message from support@examlabs.com and follow the directions.