Salesforce ADX-201E Exam Actual Questions
Essentials for New Lightning Experience Administrators - Extended (Page 9 )

• A? ??? Aurora Replicas? ?? ??? ???? ?? ???, ?? ???? Network Load Balancer(NLB)? ??????. NLB? ?? 4 ?? ???? HTTP ??? ?? ???(Sticky sessions)? ????? ???? ????.
• ??? ?? ??????? ?? ?? ???? ??? ???? ?? ????? ????? ?? ?? ???(?? ?/??? ??)? ?????. ? ??? ALB?? ?? ????, NLB?? ???? ?????.
• ??? ??? ??? ??? ???? ?? ???? ???? HTTP ???? ??? ALB? ???? ???. A? ? ??? ??????.

• A — IDS attack signatures: An IDS generally detects suspicious network activity but does not necessarily scan uploaded PDF files or prevent them from being accepted.
• C — Load balancer: Distributes traffic among servers; it does not inspect files for malware.
• D — WAF command-injection blocking: A WAF can help block web attacks such as command injection, SQL injection, and cross-site scripting, but this option does not specifically address malicious PDF uploads.

• A. IDS attack signatures: An IDS primarily detects suspicious network activity and usually alerts rather than directly scanning and blocking uploaded files.
• C. Load balancer: Distributes traffic among servers but does not inspect files for malware.
• D. WAF: Protects web applications from attacks such as SQL injection, cross-site scripting, and some malicious requests. It is not primarily a PDF-malware scanning solution.

• Business
• People
• Governance
• Platform
• Security
• Operations

• Program and project management
• Risk management
• Cloud financial management
• Data governance
• Portfolio management

• Sustainability
• Performance efficiency
• Reliability

• App Tag: a label that reflects the app’s enterprise readiness based on its Cloud Confidence Index (CCI) rating. It lets you quickly group apps (e.g., Poor, Average, Good) for policy decisions.
• App Score: a numeric value representing the CCI score. It provides a precise threshold you can use to enforce policies (e.g., block apps with Score below 50).

• You can create policies that block or restrict apps with a Poor App Tag or with an App Score under a chosen threshold.
• These two aspects let you filter cloud apps by CCI ratings during policy evaluation.

• CCL isn’t described as a real-time policy facet in this scenario.
• GDPR Readiness is a separate consideration and not the two CCI aspects used for real-time protection policy in this context.

• Incidents & alerts — see how the phishing activity was detected, correlated, and investigated.
• Threat Explorer — search for the malicious messages, recipients, URLs, attachments, and campaign activity.
• Email and collaboration reports — assess how many users or messages were affected.
• Remediation details — verify whether messages were quarantined, removed, or otherwise contained.

• Microsoft 365 admin center — general tenant administration.
• Microsoft Entra admin center — identity and access management.
• Exchange admin center — mail-flow and Exchange configuration, rather than full phishing-incident investigation.

• Interactive development and exploration
• Small datasets
• Lightweight transformations or testing
• Avoiding the overhead and cost of multiple workers

• Automated reports: Jobs may benefit from job clusters or SQL warehouses.
• Working with SQL in Databricks SQL: Databricks SQL warehouses are the relevant compute option.
• Automatically scaling for larger data: A multi-node cluster with autoscaling is more suitable.
• Large amounts of data: Distributed worker nodes are generally needed.

• Statement 1: Admin1 must approve requests for the Agent ID Developer role — No

• Statement 2: Admin2 can approve requests for the AI Administrator role — No

• Statement 3: Admin3 can assign User1 a two-day active assignment for the Agent ID Developer role — Yes

• A: True. You can change the size of a Virtual Warehouse after creation (via UI or ALTER WAREHOUSE).

• B: True. A warehouse can be resized while it’s running; the resize will take effect without needing to stop queries.

• C: True. A warehouse can be configured to suspend after a period of inactivity (AUTO_SUSPEND).

• D: True. A warehouse can be configured to auto-resume when new queries are submitted (AUTO_RESUME).

• Cutover: The old system is replaced immediately. It may be fast, but any failure can cause significant disruption.
• Phased: The system is introduced in stages, which reduces implementation risk but may prolong the transition.
• Pilot: The system is first deployed to a limited group or location. This is useful for testing but does not necessarily minimize downtime for the entire organization.

• Why: After listing all resources, you need to assign who is responsible for each task. A RACI chart (Responsible, Accountable, Consulted, Informed) documents these roles for every activity.

• What RACI means:

• Why the others aren’t suitable here:

• Quick example: Task "Create user authentication module" — Responsible: Developer, Accountable: Tech Lead, Consulted: Security Architect, Informed: PM.

• Use a field on Account to show the aggregated yearly shipments (a Roll-Up Summary).
• A Master-Detail relationship between Shipment and Account is required for Roll-Up Summary to work (and to ensure access is governed by the parent Account).
• OWD and the relationship type determine what users can see. If you want to restrict shipment-level access while still showing a summary on Account, Private OWD on Shipment plus Master-Detail helps, because access to shipments is controlled by the Account record.

• A (Public OWD on Shipment with Process Builder and a Lookup to Account): Not ideal. Public access would expose shipments broadly, and a lookup cannot support a built-in roll-up summary.
• B (Private OWD on Shipment, Roll-Up Summary, Master-Detail to Account): Best answer. Private shipments, but because of Master-Detail, access and the roll-up are tied to the Account. The Account can show the yearly total via a Roll-Up Summary field.
• C (Controlled by Parent on Shipment, Trigger, Master-Detail): Master-Detail is correct, but using a trigger is unnecessary for a straightforward roll-up; roll-ups are the standard, maintainable solution.
• D (Private OWD on Shipment, Trigger, Lookup to Account): More complex and not as efficient; no automatic roll-up, and lookup breaks the ease of summarizing by Account.

• IaaS provides virtualized infrastructure, including VMs, disks, and networking. You manage the guest operating system and software installed on the VM.
• PaaS provides a managed platform for deploying applications without managing the underlying VMs or operating systems. Examples include Azure App Service and Azure Functions.

• Source: on-premises SQL Server Database1
• Destination: Fabric Warehouse Warehouse1
• Connectivity: on-premises data gateway

• Dataflow Gen1: Primarily for Power Query transformations and isn’t the best Fabric-native choice for this copy operation.
• KQL queryset: Queries data; it does not orchestrate copying from SQL Server.
• Notebook: Could perform custom code-based movement, but it is unnecessary and less direct than a pipeline.

• In the AWS shared responsibility model, AWS manages the security of the “infrastructure,” including the physical hardware and underlying virtualization.
• The customer is responsible for everything else in the cloud stack: the guest OS on EC2, the NoSQL database software running on it, data, patching the OS, and configuring access controls like security groups.
• So, for a self-managed NoSQL database on EC2, AWS would handle the physical hardware, while you would patch the guest OS and manage DB availability, backups, and security.

• Date: 2018-12-31
• Time: 08:59

• B: The original value contains the text at, so it cannot be converted directly to a date.
• A: The last characters contain the time, not the date.
• D: Extracting the first 11 characters can leave an unwanted space and does not properly separate the time component.

• Create Power Query parameters for the Azure SQL server/database—or at least the database name.
• Use the parameter in the PBIX connection.
• Publish the same PBIX separately to the relevant development, test, and production workspaces.
• Set each dataset’s parameter value in the Power BI service so it points to the corresponding Azure SQL database.

• Development dataset ? DevelopmentDB
• Test dataset ? TestDB
• Production dataset ? ProductionDB

• The same PBIX is used for every lifecycle stage.
• Each stage consumes data from its matching database.
• Deployment pipelines are not required.
• Azure SQL is a cloud source, so gateway administration is generally avoided.
• Only the parameter value differs between published datasets, reducing maintenance.

• Review the risk register.
• Use the previously defined risk response plan, such as assigning a backup resource, reprioritizing work, or using another qualified engineer.
• Implement the response promptly because the task is on the critical path.

• B: Revising the schedule without first applying the planned response may be premature.
• C: Excluding a required task could compromise the project’s objectives and requirements.
• D: Updating the risk and lessons learned records is appropriate, but it should happen after managing the immediate issue, not as the next primary action.

• L2TP uses UDP port 1701 for the L2TP control channel.
• The destination port is 1701; the source port is a dynamically chosen ephemeral port on the client (not 1701).
• Therefore the statement that both source and destination ports are 1710 is incorrect (and 1710 is not the standard L2TP port).

• The destination port should be 1701, not 1710.
• The source port should be an ephemeral port chosen by the client, not 1701.

• Voice devices ? VLAN 10
• Data devices ? VLAN 20
• SVI for VLAN 10 ? 192.168.10.1
• SVI for VLAN 20 ? 192.168.20.1

• A: Describes a physical trunk interface, not an SVI.
• B: An SVI can provide management access, but that is not its primary definition here.
• D: SVI does not compensate for insufficient physical ports; it is a logical interface.

• Pay-as-you-go in Azure is an operating expense (OPEX) model, not an “elastic” expenditure model.
• Elastic or scalable terms describe capacity planning, not the cost category. The cost should be treated as OPEX since you pay for usage each month.
• The parallel question (Question 12) shows the correct approach is using an operational expenditure model.

• In Microsoft Teams Phone System, a single Auto Attendant can handle multiple time-based greetings by using separate schedules for office hours, after hours, weekends, and holidays.
• You can configure one Auto Attendant with four distinct greetings mapped to:

• Open the Teams admin center > Voice > Auto attendants, edit or create an Auto Attendant.
• Under Time-based routing, define four rules:

• Create a Holiday schedule with the relevant dates (e.g., Easter, Christmas) and assign the Holiday greeting.
• Save the configuration.

• If your environment cannot separate weekend from after-hours within a single Auto Attendant, you might technically need more than one Auto Attendant.

• Correct options: C and D.

• The AWS Cloud Adoption Framework (CAF) security perspective focuses on capabilities to protect information and manage security risk.
• Observability (A) is primarily an operations/monitoring capability, not a core security capability under CAF.
• Incident and problem management (B) is IT service management/operations, not specifically a CAF security capability.
• Incident response (C) is a security-focused capability: detecting, containing, and recovering from security incidents.
• Infrastructure protection (D) involves applying security controls to protect the underlying infrastructure, which fits the security perspective.

• An IDS monitors network traffic for signs of attacks and raises alerts. It can be deployed out-of-band (via a SPAN/mirror port or a tap) so it analyzes traffic without being inline, meaning it doesn’t measurably affect latency.
• An IPS (intrusion prevention system) is inline and can block threats, but that processing can introduce some latency and potential throughput impact.
• A firewall also inspects traffic and can add latency, though usually modest with proper hardware, but its primary purpose isn’t continuous passive analysis.
• A load balancer distributes traffic and isn’t used for intrusion analysis.

• Developed and maintained independently
• Deployed without changing the entire application
• Scaled separately based on demand
• More resilient when another service has problems

• A: Functional testing is useful, but it is not the main practice described.
• B: Automation helps deployment, but the scenario focuses on architectural decomposition.
• C: Multiple locations improve availability, not application modularity.

• A (training data, hyperparameters, stakeholder feedback) focuses on training provenance; these details are important but are typically part of pre-deployment/training records, not the primary post-deployment documentation.
• B (encountered issues, monitoring process, risks) relates to governance and monitoring rather than the core documentation you’d publish about the deployed model itself.
• C (licensing information, the team, business goals) covers governance context but not the technical traceability and performance-based record needed for ongoing maintenance.

• Event | search "error"
• Event | where EventType == "error"
• search in (Event) "error"

• Answer: No (B)

• SaaS (Software as a Service) delivers applications over the internet; you don’t manage the underlying infrastructure or OS.
• Deploying Azure virtual machines requires provisioning and managing virtual machines, OS, updates, and networking—this is classic IaaS (Infrastructure as a Service).
• PaaS is for managed runtime environments (apps hosted on a platform), not for VM deployment.

• What it’s asking: In an ARM template, for an Availability Set, what value should you set for the property platformFaultDomainCount to maximize availability during fabric failures or maintenance?

• Key concept: Fault domains are groups of hardware that can fail independently. By spreading VMs across more fault domains, you reduce the risk that a single hardware fault takes out many VMs.

• Important detail: For managed Availability Sets, the number of fault domains you can use varies by region — typically 2 or 3.

• What to choose: Set platformFaultDomainCount to the maximum supported in your region. In most regions this is 3, which gives you the best resilience. If your region only supports 2, you’d use 2.

• Answer: 3 (Max Value). In ARM template syntax, this would appear as "platformFaultDomainCount": 3 (within the Availability Set resource).

Why

cmd 
PowerShell.exe -ExecutionPolicy Bypass -File C:\Scripts\ConfigureVM.ps1

Why the other options are less suitable

• GPO logon script: Runs only when a user logs on and may not run during initial VM provisioning.
• GPO startup script: Can work, but requires the VM to be joined to the domain and the policy to be applied. It is also normally evaluated at each startup.
• Place scripts in a VHD: Merely placing scripts on a disk does not cause them to execute.

• The requirement: the support plan must allow opening new support requests (technical support incidents).
• Azure’s Basic plan does not include technical support incidents—only billing/subscription support and access to community support.
• Therefore, you must choose a paid plan to open new technical support requests: Developer, Standard, Professional Direct, or Premier.

• Enable the owner dimension
• Allocate a standard costing inventory model

• Owner dimension (B): This dimension Lets you track who owns the stock. By enabling the owner dimension, items can be configured as either company owned or consignment (vendor-owned) when you create or edit items. Without enabling this dimension, you can’t designate ownership per item.
• Standard costing inventory model (D): Selecting a costing model determines how item costs are calculated and posted. Standard costing provides a fixed cost per unit, which is commonly used for agreed pricing scenarios like consignment arrangements for easier accounting and valuation. It helps ensure consistent cost treatment across transactions for items that can be owned by the company or on consignment.

• Batch dimension (A): Batch tracking is unrelated to ownership and isn’t required to support company-owned vs. consignment configurations.
• Moving average costing (C): This is an alternative costing method. It’s not required to enable ownership config, and the exam’s expected choice focuses on standard costing for this scenario.

• Answer: D

• The strongest security comes from enforcing access at the storage layer. An IAM policy scoped to the Cognito identity prefix restricts each user to their own S3 prefix (folder), so users can only access their own files regardless of client or server code.
• This per-user isolation reduces risk of cross-user data access and is more robust than UI validation or Lambda/API validation alone.
• Implementation note: attach a policy to the Cognito identity role that allows actions on arn:aws:s3:::your-bucket/${cognito-identity.amazonaws.com:sub}/* (per-user prefix). Ensure TLS in transit and enable at-rest encryption (SSE-S3 or SSE-KMS). Use multipart upload for large files up to 300 MB.

• Correct answer: only new data added to the eventhouse (option E).
• Why: When you enable OneLake availability for the eventhouse, OneLake starts syncing data going forward. It does not automatically backfill or copy over data that already exists in the eventhouse before the enablement.
• What that means in practice: Any data added to the eventhouse after you enable OneLake will appear in OneLake (and be visible from OneLake file explorer). Pre-existing data in the eventhouse stays there unless you perform a separate backfill/copy operation outside the standard OneLake enablement.
• How to verify: add a small new dataset to the eventhouse after enabling OneLake availability, then check OneLake to confirm the new dataset appears.

• Correct answer: C. AWS CloudFormation

• Why: CloudFormation lets you define infrastructure as code via templates (JSON or YAML). You can create a single template that describes multiple AWS resources and reuse it to deploy consistent stacks across environments. Templates can be parameterized and stored for repeated deployments. Other options (Marketplace, AMI, OpsWorks) don’t provide reusable deployment templates in the same way.

• Help the team identify the causes of delays.
• Encourage continuous improvement through retrospectives.
• Support the team in changing its process, tools, or collaboration methods.
• Help remove impediments that the team cannot resolve independently.

• A: An impediment log may help, but simply maintaining it does not ensure the impediments are resolved.
• B: Directing the team to solutions conflicts with agile self-management.
• C: Adding impediments to the product backlog could delay their resolution and treats them like product features.

• Self-signed certificate: Causes a certificate warning, not incorrect IP resolution.
• Nameserver record: A DNS record problem would typically affect multiple users, not just one.
• IP helper: Relays DHCP or other broadcast traffic between networks; it does not control website name resolution.

• The Well-Architected Framework has five pillars: Operational Excellence, Security, Reliability, Performance Efficiency, and Cost Optimization.
• Operational Excellence: how you run and improve your systems—monitoring, incident response, and evolving processes.
• Reliability: the ability of a workload to recover from failures, maintain uptime, and scale as demand changes.

• Availability (A) is not a pillar name; it’s an outcome that relates to Reliability.
• Scalability (C) isn’t a pillar name; scalability touches on Performance Efficiency.
• Responsive design (D) is not a pillar in the Well-Architected Framework.

• Security Development Operations (SDO): a security-focused take on DevOps, integrating security into the development pipeline.
• Service Data Object (SDO): a data representation used in some middleware or enterprise apps.
• Software-Defined Overlay (SDO): a networking overlay concept.
• Secure Data Object: a generic data-security term.

• The policy is confidential, and the requester is no longer authorized merely because they used to work for the organization.
• The security professional should not disclose it by email or display it on a device without authorization.
• Using official channels allows the organization’s owner or information custodian to verify:

• The correct setting to configure is the Enrollment Status Page (ESP) profile.
• Why: ESP tracks the enrollment progress and logs during Autopilot provisioning. You can enable log collection within the ESP policy so that, if ESP times out, the user can collect and share the logs with support.
• Optional enhancement: In the ESP policy (or the Autopilot diagnostics settings), you can enable:

• Automatic enrollment settings: control how devices auto-enroll, not log collection.
• Windows Autopilot deployment profile: controls deployment steps but not ESP log collection.
• Device configuration profile: applies settings but doesn’t provide ESP log collection mechanics.

• Progress iteratively with feedback focuses on making improvements in manageable steps and learning from feedback.
• Optimize and automate focuses on maximizing value from resources and automating suitable activities.
• Start where you are focuses on assessing the current situation and reusing what already exists.

• Elicited and documented customer requirements
• Converted them into clear, measurable specifications
• Validated the requirements with the customer
• Used them as the basis for design, quality checks, and acceptance

• A: Requirements should reflect the customer’s needs—not the supplier’s standards.
• B: Iteration review planning does not replace proper requirements collection.
• D: A retrospective occurs after work is completed and is mainly for process improvement, not initial requirements definition.

• Active vs passive: Active assessment involves actively scanning targets by sending probes/packets to identify hosts, services, and vulnerabilities. Passive assessment observes traffic without probing.
• External vs internal: External assessment is about testing from outside the network perimeter; the scenario doesn’t specify external vantage, only that tools are identifying hosts/services across the enterprise network.

• SageMaker endpoint: Not required because the model is being used through Amazon Bedrock.
• SageMaker Model Registry: Used for managing SageMaker models, not for making a Bedrock custom model available.
• Grant access in Amazon Bedrock: IAM permissions may still be needed, but granting access alone does not provide the required inference capacity.

• View/inspect configuration: Possible.
• Modify the installed application or its S-Controls: Typically restricted in a test-drive org.

• Why: A multi-modal embedding model maps both text and images into a shared vector space, enabling cross-modal similarity and retrieval (e.g., find images matching a text query or text matching an image).

• What it does: Enables efficient similarity search using a vector database or nearest-neighbor indexing.

• Why the other options aren’t suitable:

• Quick implementation note: you’d typically pair the embeddings with a vector store (e.g., ANN index) and possibly fine-tune on domain data for better alignment across modalities.

• IaaS: You deploy and manage virtual machines, operating systems, disks, and networking. Azure manages the physical datacenter and host infrastructure.
• PaaS: Azure manages the operating system and runtime so you can focus on deploying applications, such as with Azure App Service or Azure Functions.
• SaaS: You consume a complete, provider-managed application.

1. Remote access to a Windows PC
2. Full chat and optional game-console functions

• Windows Remote Desktop (RDP) uses TCP 3389. The router needs a port-forwarding rule that sends incoming traffic on that port to the Windows PC’s internal IP address.
• The game console should connect through the wireless AP. Using WPA2-PSK provides the required wireless security while allowing normal online, chat, and optional services.
• The firewall should separate the internal network from the screened subnet. Its screened-subnet-side address is shown as 10.100.0.1.
• Devices must be placed in the correct network locations: the PC behind the router, the console on the wireless AP, and the firewall between the appropriate network segments.