LPI 102-500 Exam Prep
LPIC-1 Exam 102, Part 2 of 2, version 5.0 (Page 14 )

• A private IP address on the virtual network
• An associated public IP address

• What the dataflow options mean:

• Why C fits best:

• Correct answer: Power BI dataset

• The scenario says the data model already contains several measures and you want to create a report from the existing data with minimal development. Reusing a published Power BI dataset lets you inherit the existing measures and data model, so you don’t have to recreate them.
• How to do it: In Power BI Desktop, use the connector Power BI datasets (Get Data > Power BI datasets) and connect to the existing dataset, then build visuals using the pre-defined measures.
• Why the other options are less suitable:

• Amazon S3 — Object storage, not a database.
• Amazon DynamoDB — Fully managed NoSQL key-value and document database.
• Amazon Redshift — Managed data warehouse designed for analytics, not primarily transactional MySQL workloads.

• A. Configure prompt modifications to enforce tone, disclaimers, and refusal behavior at the system level.

• D. Configure Power Platform DLP policies to restrict unauthorized data connectors.

• B: Manual topic-by-topic disclaimer edits are specifically discouraged.
• C: Channel settings do not replace agent-level Responsible AI controls.
• E: Publishing before enabling safety filters violates the stated deployment sequence. Responsible AI filters should be enabled before publication, not afterward.

• A. Tuning system software: This is a corrective action, not an analysis method. Tuning should be based on measured performance data.
• B. User dissatisfaction reports: Useful as an indicator, but subjective and insufficient for diagnosing the cause.
• D. Off-peak utilization and response time: This may hide problems occurring during peak periods. Performance analysis should cover representative or peak workloads.

• Correct choices: A and D.

• Why not B, C, or E?

• A) MTU mismatch: OSPF neighbors must exchange Hello packets with a compatible MTU. If MTUs differ, the neighbor conversation fails and the adjacency cannot become Full.

• B) Incorrect subnet mask: Routers must be in the same IP subnet on the connected link to form a neighbor relationship. A subnet mismatch prevents Hello packets from being considered valid on the same network.

• D) Area ID not the same: Neighbors must share the same Area ID. A mismatch stops adjacency from forming beyond the 2-Way state.

• E) Different metric set on each end of the link: Cost differences do not prevent OSPF adjacency; they affect routing decisions, not neighbor formation.
• F) Router ID not defined: OSPF can auto-choose a router ID; an undefined ID is not a prerequisite for adjacency to reach Full.

• A single Construction Job can use multiple Machinery records.
• A single Machinery record may be used on multiple Construction Jobs.
• This is a many-to-many relationship, which Salesforce models using a junction object.
• The junction object can contain fields such as:

• Master-detail to Machinery
• Master-detail to Construction Job
• Date and cost fields

• Regional leads — Customer Community Plus

• Capacity planners — External Identity

• Customer Community does not provide the enhanced reporting/dashboard access required by regional leads.
• An Identity license is generally for internal Salesforce identity use and does not fit the external capacity-planning users as well as External Identity.

• On-Demand: You pay by the hour with no long-term commitment. This is ideal for workloads that are infrequent or have highly variable usage. Since this job runs only 24 hours once per year, you pay only for those 24 hours, with no wasted upfront or long-term payments.
• Reserved Instances: Require a 1- or 3-year commitment and pay for capacity whether you use it or not. For a workload that runs just 24 hours a year, you’d be paying for most of the term unused, making it far less cost-efficient.
• Spot Instances: Can be interrupted whenever AWS needs capacity, which is unacceptable for an uninterruptible workload.
• Dedicated Instances: Generally more expensive and aimed at licensing or compliance requirements; not needed for this use case.

kusto 
Event 
| summarize make_set(EventID) by Computer

• summarize groups records.
• by Computer creates one result row per virtual machine.
• make_set(EventID) returns an array containing unique event IDs for that computer.

kusto 
| summarize make_list(EventID) by Computer

• Multi-factor authentication
• A secure password change for users whose credentials may be compromised

• Drops packets when traffic exceeds a certain bitrate: This describes traffic policing, not shaping.
• Fragments large packets and queues them: Shaping does not fragment packets as its primary congestion-control action.
• Drops packets randomly from lower-priority queues: Packet dropping may occur if a shaping queue becomes full, but it is not the defining behavior.

• Shaping: buffers and delays excess traffic.
• Policing: drops or marks traffic that exceeds the configured rate.

• vSmart controls the overlay control plane. It uses OMP to exchange routing information, distribute policies, and determine how WAN Edge devices reach one another.
• vManage is the centralized management and configuration platform.
• vBond is the orchestrator. It helps devices authenticate, discover controllers, and traverse NAT during onboarding.
• APIC-EM is not the SD-WAN control-plane component described here.

• Correct answer: D) Amazon Aurora Serverless

• Aurora Serverless is serverless, so compute capacity scales automatically and can pause during idle periods. This minimizes ongoing administration and you pay only for actual usage, which is ideal for infrequent workloads.
• PostgreSQL on EC2 requires full OS and DB administration.
• RDS for PostgreSQL is managed but still involves provisioning capacity and some maintenance tasks.
• Aurora PostgreSQL (non-Serverless) is managed but requires you to manage capacity, though with some automation; it’s not as hands-off as Serverless for intermittent usage.

• Import mode loads the data into the Power BI model. Visuals query the in-memory model, which generally provides faster calculation and rendering than DirectQuery.
• Import mode also minimizes online processing because report interactions do not send queries back to the dataflow or SQL Server.
• A daily refresh can load data through the previous day, satisfying the freshness requirement without unnecessary hourly processing.

• DirectQuery keeps querying the data source or dataflow during report use, increasing online processing and potentially slowing visuals.
• Adding a gateway enables connectivity for on-premises sources, but it does not remove the performance disadvantages of DirectQuery.
• An hourly Power Automate refresh is unnecessary when the requirement is only data through the previous day and creates additional processing overhead.

• The diagnostic output shows that the protocol is TCP (proto=6) and the session state is 2.
• In FortiGate’s session output, state=2 maps to SYN_SENT. This means the TCP SYN has been sent but the handshake hasn’t completed yet.
• Therefore, the session is not ESTABLISHED, FIN/ACK-related states, or other states; it’s in SYN_SENT.

• Permanent table (E): Correct. A dropped permanent table can be restored with UNDROP TABLE during its Time Travel retention period. Permanent tables also have Fail-safe protection.
• Transient table: It can also generally be restored during its shorter Time Travel period, although it has no Fail-safe. Therefore, excluding it makes the question questionable.
• Temporary table: Usually cannot be recovered after it is dropped; its lifecycle is limited to the session.
• Materialized view (D): The answer key treats it as recoverable, but recovery behavior depends on the specific Snowflake object/version capabilities. It should not be confused with an ordinary view.

• Create and manage catalogs of approved IT services
• Govern and publish infrastructure-as-code (IaC) templates, commonly AWS CloudFormation templates
• Control which users can deploy specific products and configurations
• Apply versioning, permissions, and deployment constraints

• AWS Resource Explorer: Searches and discovers AWS resources; it does not govern IaC templates.
• AWS Organizations: Manages multiple AWS accounts, policies, and consolidated billing.
• AWS Systems Manager: Helps operate and manage deployed resources, such as patching and automation, but is not primarily a catalog for governed IaC products.

• 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.

• Secure: uses encryption, such as HTTPS or SFTP.
• Cross-platform: supported by many languages and operating systems.
• Internet-friendly: designed to communicate across networks, usually using standard Internet protocols.

• JSON/REST over HTTPS — widely supported, secure, and Internet-friendly.
• SOAP over HTTPS — also secure and highly cross-platform, though more heavyweight.
• XML over SFTP — secure file-based exchange, but it is not an API-style interface.

• Amazon DynamoDB — Managed NoSQL database, not PostgreSQL.
• Amazon Athena — Serverless service for querying data in S3; intended for analytics, not OLTP.
• Amazon EMR — Managed cluster platform for big-data frameworks such as Hadoop and Spark.

Simple explanation

• The Azure VPN gateway to connect to
• Authentication settings
• Routes for networks that the client can access

• Goal: serving a static website globally with minimal latency.
• Why C works: CloudFront is a Content Delivery Network (CDN) that caches content at many edge locations around the world. When users request the site, CloudFront serves cached copies from the nearest edge location, greatly reducing latency. It also reduces load on your EC2 origin by handling many requests at the edge.
• Why the other options aren’t as good:

• The correct AAA mapping (per Cisco objectives) is:

• Why the given options aren’t fully correct:

• Quick takeaway: when you configure AAA, you should conceptually map them as:

• Example commands (to reinforce concepts):

• 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).

• A. A virtual network gateway
• D. A virtual network

• Azure virtual machines must be connected to an Azure virtual network (VNet). The VNet provides private IP addressing and network connectivity for the VMs.
• A virtual network gateway enables communication between the Azure VNet and the on-premises network, typically through a site-to-site VPN or ExpressRoute connection.

• Load balancer: Distributes traffic among Azure VMs; it does not connect Azure to an on-premises network.
• Application gateway: Provides web-application load balancing and Layer 7 routing; it is not the normal resource for on-premises connectivity.
• Gateway subnet: A gateway subnet is required inside the VNet when deploying a virtual network gateway, but the question’s intended two primary resources are the VNet and virtual network gateway.

1. Determine which host was infected first—the originating host.
2. Decide whether each other host is clean or infected based on communication and event logs.

• Compare timestamps and find the earliest suspicious event.
• Look for the host that initiated the malicious connection, file transfer, exploit, or command—not merely a host that later received traffic.
• Follow the timeline through the firewall:

• A host is likely infected if it both receives suspicious activity and then initiates related malicious traffic.
• A host may be clean if the firewall blocked the connection and there is no evidence of execution or follow-on communication.

• The 99.99% availability SLA for VMs is achieved when you run VMs across two or more Availability Zones.
• Two VMs in a single Availability Zone do not meet the 99.99% target (their SLA is lower, e.g., around 99.95% or less depending on configuration).

• Deploy at least two VMs across two different Availability Zones (one VM in each zone, or both in two zones with a load balancer).
• This provides the required zone redundancy and the 99.99% SLA.

1. Download the updated VPN client configuration package from the Azure VPN gateway.
2. Remove or update the existing VPN client configuration on the Windows 10 workstation.
3. Install the new package and reconnect.

1. Modify the database subnet NACL inbound rules to allow traffic from the new web subnet’s CIDR block on the MySQL port (3306).
2. Modify the database subnet NACL outbound rules to allow return traffic to the new web subnet’s CIDR block on the required ephemeral port range.

• Answer: Data enhancement.

• Why: Augmenting gold-layer tables with an additional dataset is enriching or enhancing the existing data to support the ad-hoc analysis. The other options don’t capture the idea of adding external data to improve the dataset (ad-hoc improvements = tweaks, last-mile dashboarding = building dashboards, last-mile ETL = ETL steps at the end of the pipeline). In practice, this is often also called data enrichment.

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

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

• Sustainability
• Performance efficiency
• Reliability

• The explanation states that Traffic Analytics can be enabled by a user with one of these subscription-level roles:

• Question 34 — Network Contributor: Yes
• Question 35 — Owner: Yes
• Question 36 — Reader: Yes, according to the stated explanation and documentation

• Filtering or reshaping columns
• Joining with an analysis-specific dataset
• Creating calculated fields
• Applying business logic for a particular project

• Data blending: Combining different data sources, not specifically the final processing step.
• Data enhancement: A broad term for enriching data.
• Data testing: Checking data quality or pipeline correctness.
• Last-mile ETL: The precise term for additional transformations performed after the main pipeline, often directly before analytics or reporting.

• Sales Processes define the set of Opportunity stages for a given workflow.
• Record Types let you have different data models (different fields and picklist values) on the same object.
• Page Layouts control which fields are shown/required for each record type.

• Create three Sales Processes so each team can use its own stages.
• Create three Record Types so each team has its own fields and picklist values.
• Create three Page Layouts so each record type shows the appropriate fields.

• Import — Loads data into Power BI. It requires a refresh, so it may not reflect changes within two minutes unless refresh is configured appropriately.
• Live connection — Connects to an existing Power BI semantic model or Analysis Services model; it is not the normal choice for connecting directly to an Azure SQL database.

• The inference container image or built-in algorithm
• The location of model artifacts in Amazon S3
• IAM permissions through the execution role
• Optional environment variables and networking settings

1. Create AWS::SageMaker::Model
2. Create an AWS::SageMaker::EndpointConfig that references the model
3. Create AWS::SageMaker::Endpoint that references the endpoint configuration

• AWS::SageMaker::Endpoint hosts a model but does not define the model itself.
• AWS::SageMaker::NotebookInstance provides a development environment.
• AWS::SageMaker::Pipeline orchestrates ML workflow steps.

• Detect risky sign-ins from unfamiliar or unidentified IP addresses
• Evaluate user or sign-in risk
• Automatically require a password change because of a risky sign-in

• User risk policy: Can require a user to securely change their password when the account may be compromised.
• Sign-in risk policy: Can require MFA or block access based on the risk of a particular sign-in.

1. Ingestion Lambda receives requests from API Gateway and places messages in an SQS queue.
2. Processing Lambda is triggered by the queue and loads records into Aurora PostgreSQL.

• Decoupling: API request handling is separated from database loading.
• Buffering: SQS absorbs bursts when incoming traffic exceeds the database’s processing capacity.
• Controlled concurrency: Configure the SQS-triggered Lambda’s concurrency and batch size to avoid overwhelming Aurora or exhausting database connections.
• Automatic retries: Messages that fail processing can return to the queue and be retried. A dead-letter queue can capture persistent failures.
• Lower operational effort: The solution remains serverless and avoids managing EC2 servers or Kubernetes clusters.

• A: EC2 and Tomcat add server-management overhead.
• B: DynamoDB/DAX would require changing the database model and does not solve the Aurora ingestion design.
• C: SNS is useful for notifications and fanout, but SQS is better for durable buffering and backpressure in this producer-consumer workflow.

• Correct answer: B — From the code repository, modify Startup.cs (in ASP.NET Core you configure the Application Insights SDK in code, not with ApplicationInsights.config).

• Why the other options aren’t correct:

• How to implement fixed-rate sampling (ASP.NET Core):

var builder = WebApplication.CreateBuilder(args); 


    builder.Services.Configure<TelemetryConfiguration>(telemetryConfiguration => 
    { 
        var builder = telemetryConfiguration.DefaultTelemetrySink.TelemetryProcessorChainBuilder; 
        double fixedSamplingPercentage = 10; // 10% sampling 
        builder.UseSampling(fixedSamplingPercentage); 
    }); 


    builder.Services.AddApplicationInsightsTelemetry(new ApplicationInsightsServiceOptions 
    { 
        EnableAdaptiveSampling = false 
    }); 


    var app = builder.Build();

• Two VMs
• Distributed across two separate availability zones

• C — Schema.describeSObjects(new String[]{myObject})[0].fields.getMap()

• D — Schema.getGlobalDescribe().get(myObject).getDescribe().fields.getMap()

• A: sObjectType is not used this way, and fieldSet() is not the appropriate method for retrieving all fields.
• B: mySObject.myObject is not valid dynamic Apex syntax.

• Who performed the action
• What action occurred
• When it occurred
• Where it originated
• Whether it succeeded or failed

• Investigating suspicious activity: Important, but investigation depends on having adequate audit data first.
• Storage allocation: Necessary for retention, but storage does not help if the records lack meaningful details.
• Actions after audit failure: Part of operational planning, not the primary assessment of the application’s audit capability.

• Assign users or their team an appropriate security role.
• Ensure the role has the required table privileges, such as read, create, write, and append.
• Share the app with that security role in the app designer.

• Dynamics administration center: Used for environment and service administration, not routine app access configuration.
• Manage Roles: Not the specific Dataverse area used to define app and data permissions.
• Security Roles: Define what users can access and which operations they can perform.

• Options:

• Answer: The correct choice is A (800-61r3).

• NIST SP 800-61 Rev. 3 is the dedicated guide for incident handling/response and reflects the latest guidance on the incident response lifecycle (preparation, detection/analysis, containment, eradication, recovery, post-incident activity).
• 800-61r2 is an older revision of the same incident response guide.
• 800-53 covers security and privacy controls, not a specific incident response standard.
• 800-171 focuses on protecting CUI in non-federal systems and networks, not incident response guidance.

• 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.

• Version control provides a single source of truth for metadata changes and tracks every modification.
• It supports branching and merging, so each feature can be developed in isolation and later merged without overwriting others.
• It allows diffs and conflict resolution, making it easier to manage dependencies across features and ensure a stable release.

• Setup Audit Trail: only logs who/change when something happened; it doesn’t prevent overwriting or manage cross-feature dependencies.
• Change Sets: used to deploy changes between orgs, not to coordinate parallel development or prevent conflicts across ongoing sprints.