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
Managers need quarterly evidence that external guest access to privileged applications is still justified. An engineer must deliver the following acceptance evidence: A rejected guest review removes the corresponding app assignment after the review closes. What design choice is defensible?
Access reviews periodically recertify assigned access and can remove access for denied reviews. The selected architecture is run Microsoft Entra access reviews with suitable reviewers and removal actions; confirm the result by checking that a rejected guest review removes the corresponding app assignment after the review closes.
Delegated permissions represent what an application can do on behalf of an authenticated user. Its design target is App registration API scopes. The stated requirement instead concerns: 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. The relevant requirement is: Managers need quarterly evidence that external guest access to privileged applications is still justified.
Management locks guard against accidental resource deletes and operate separately from authorization roles. It does not solve the specified Identity lifecycle audits condition.
The acceptance criterion for Private endpoint comes from this issue: A storage service must have an address in a VNet and reject access from the public internet. Which measured outcome is the strongest proof?
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. Confirm using the measurable result: The data source resolves to a VNet private address and public access is denied.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. The offered observation would demonstrate Service endpoint: The approved subnet accesses storage and unauthorized internet clients are blocked. The current validation is different: The data source resolves to a VNet private address and public access is denied.
Network Watcher diagnostic tools identify effective network behavior and filtering decisions. The distinguishing check is: The data source resolves to a VNet private address and public access is denied.
VNet peering alone is not transitive and forwarding needs explicit architecture. The Peering nontransitivity test checks permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails; the relevant outcome is The data source resolves to a VNet private address and public access is denied.
The team has justified its Cosmos partition key design with: Choose a high-cardinality partition key aligned with dominant access queries. Which statement accurately describes why the approach works?
Partition key distribution governs data/throughput placement and query efficiency. It is material here because a Cosmos container uses a low-cardinality partition key and has hot-partition throttling.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. Partition key distribution governs data/throughput placement and query efficiency.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. That statement describes Azure managed disks, while the question asks how Cosmos partition key works: Partition key distribution governs data/throughput placement and query efficiency.
Session consistency offers read-your-writes within a session without strong global consistency. Partition key distribution governs data/throughput placement and query efficiency.
A team must restrict a VM subnet to TCP 443 from a management prefix without deploying a full firewall. A deployment must satisfy this operational criterion: The approved source reaches TCP 443 and another source is denied. Which plan is appropriate?
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. The selected architecture is apply NSG rules at an appropriate subnet or NIC scope; confirm the result by checking that the approved source reaches TCP 443 and another source is denied.
Azure Firewall provides managed stateful filtering with network/application rule models. That is useful for Azure Firewall rules (A central security team needs network and application filtering across multiple spokes). It does not meet the current NSG subnet filtering requirement: A team must restrict a VM subnet to TCP 443 from a management prefix without deploying a full firewall.
Private DNS zone links determine name resolution for VNets that consume private endpoints. Its design target is DNS private zones. The stated requirement instead concerns: A team must restrict a VM subnet to TCP 443 from a management prefix without deploying a full firewall.
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. It does not solve the specified NSG subnet filtering condition.
Architecture review: Security-event streaming and Control-plane audit. Requirement A: The SOC streams resource events into an external SIEM and needs independent replay and consumer handling. Requirement B: A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs. Which complete two-part proposal satisfies both constraints?
For requirement A, Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. For requirement B, the Activity Log records Azure Resource Manager control-plane events independent of guest agents. Verify both independently: A test operation appears in the Event Hub stream and can be read by the SIEM consumer; A denied deployment and a successful resource deletion appear with caller and operation name.
The mismatched half is Log anomaly alert; Control-plane audit instead needs: Route Azure Activity Log to a central Log Analytics workspace through diagnostic settings.
The first step implements Cross-subscription workspace instead of Security-event streaming. The necessary change is to route supported platform diagnostic events to an Event Hubs namespace.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. The Activity Log records Azure Resource Manager control-plane events independent of guest agents. The proposed steps (send supported resource logs from each subscription into a centralized Log Analytics workspace; create a scheduled log-search alert that evaluates a KQL query and threshold) address other capabilities instead of this required pair.
A large enterprise data warehouse requires predictable reserved compute for repeatable analytic SQL workloads. Identify the most suitable implementation for an outcome where the fact-table join finishes within measured performance goals under the planned workload.
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. The selected architecture is evaluate a dedicated SQL pool with appropriate distributions and workload management; confirm the result by checking that the fact-table join finishes within measured performance goals under the planned workload.
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. It does not solve the specified Synapse dedicated SQL condition.
A stored watermark limits reads to changes after the last successful processed interval. The current need is: A large enterprise data warehouse requires predictable reserved compute for repeatable analytic SQL workloads.
Partner event integration routes supported third-party event types without custom polling. That is useful for Event Grid partner events (An external SaaS integration publishes events that several Azure business systems must consume with filtered routing). It does not meet the current Synapse dedicated SQL requirement: A large enterprise data warehouse requires predictable reserved compute for repeatable analytic SQL workloads.
Architecture review: SQL Hyperscale growth and Azure SQL Database single database. Requirement A: One operational SQL database must scale beyond the capacity limits of ordinary General Purpose storage tiers. Requirement B: A SaaS app runs a standalone transactional SQL Server-compatible database and must avoid managing operating systems. Which complete two-part proposal satisfies both constraints?
For requirement A, hyperscale decouples storage scale from compute and supports large database sizes. For requirement B, Azure SQL Database offers fully managed relational database operations with automated backups. Verify both independently: A growth test reaches the required storage target with the expected compute and backup architecture; The application connects through its supported driver without patching database VMs.
The option covers one requirement but substitutes SQL geo-replication reporting for SQL Hyperscale growth. The missing acceptance result is: A growth test reaches the required storage target with the expected compute and backup architecture.
One action is correct. The other targets SQL migration assessment, leaving Azure SQL Database single database unsolved. Its necessary action is: Select Azure SQL Database for the managed individual database.
This combines SQL geo-replication reporting and SQL migration assessment, which do not satisfy the distinct requirements for SQL Hyperscale growth and Azure SQL Database single database.
During technical sign-off for Immutable evidence archive, the architect selects: Send the appropriate diagnostic logs to a storage account with configured immutable retention policies. Which underlying behavior should be documented?
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. It is material here because auditors require tamper-resistant retention of exported logs that are rarely queried.
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. It belongs to Managed Prometheus. The stated architecture instead relies on: Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search.
Entra diagnostic export makes identity sign-in events available for central retention and KQL correlation. That statement describes Identity-signin monitoring, while the question asks how Immutable evidence archive works: Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search.
The Synthetic uptime review proposes: Configure Application Insights availability tests at suitable geographic test locations. Which Azure behavior is the technical justification for this decision?
Synthetic tests independently probe URL availability and latency even when no real customer transaction occurs. It is material here because a public site sometimes fails before user telemetry is received and operations need outside-in availability tests.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. That statement describes AKS container diagnosis, while the question asks how Synthetic uptime works: Synthetic tests independently probe URL availability and latency even when no real customer transaction occurs.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. Synthetic tests independently probe URL availability and latency even when no real customer transaction occurs.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. Synthetic tests independently probe URL availability and latency even when no real customer transaction occurs.
For CDN static content, operations are closing a change that addressed: Marketing assets should be delivered from regional edge nodes instead of a central origin. Which post-change signal belongs in the acceptance record?
Edge content distribution can cache static resources near users. Confirm using the measurable result: Measured image latency decreases after the edge cache warms.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. Those observations validate Web PubSub real time. They do not establish the required CDN static content result: Measured image latency decreases after the edge cache warms.
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. The distinguishing check is: Measured image latency decreases after the edge cache warms.
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. The Durable Functions orchestration test checks restarting a worker does not restart already completed business steps; the relevant outcome is Measured image latency decreases after the edge cache warms.
For SQL failover groups HA, operations are closing a change that addressed: The database service must recover a read/write endpoint when the primary Azure region fails. Which post-change signal belongs in the acceptance record?
Failover-group listeners abstract the primary location during regional failover. Confirm using the measurable result: The app reconnects after an orchestrated failover without endpoint edits.
Zone redundancy spreads eligible database availability replicas across zones. Those observations validate Azure SQL zone redundancy. They do not establish the required SQL failover groups HA result: The app reconnects after an orchestrated failover without endpoint edits.
A zone-separated standby supports automated failover where offered. The distinguishing check is: The app reconnects after an orchestrated failover without endpoint edits.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. The Cosmos multi-write availability test checks after one region becomes unavailable another authorized region continues to accept writes; the relevant outcome is The app reconnects after an orchestrated failover without endpoint edits.
Please check your mailbox for a message from support@examlabs.com and follow the directions.