Huawei H14-231_V1.0 Exam Prep
HCIP-HarmonyOS Application Developer V1.0 (Page 46 )

• Microsoft 365 groups can contain users, but generally can’t contain other groups as members.
• Security groups can contain users and, where supported, other security groups.
• Distribution groups have different nesting restrictions and aren’t equivalent to security groups.
• Dynamic groups can’t be manually populated with members; their membership is calculated from rules.
• A group’s membership type (Assigned or Dynamic) and group type determine whether it can be added to another group.

• What wipe does: A factory reset that erases all data, apps, and settings and returns the device to the OOBE. It removes the device from management and resets identity.
• Why not for this scenario: The goal is to repurpose the same device to a new user with Autopilot. Autopilot Reset keeps the device’s Azure AD/Intune identity and re-provisions the device for the next user without a full wipe.
• What Autopilot Reset does: Removes user data and apps but preserves device identity and management connection, then reapplies the Autopilot provisioning for the next user.
• When you’d use wipe instead: If you’re selling or permanently discarding the device, or you truly want to scrub all traces and start fresh without re-enrolling.

• A. Number ? Decimal — Correct. Salesforce Number fields are represented in Apex as Decimal.
• D. Date/Time ? Datetime — This is correct conceptually, but “Dateline” is not an Apex type. If the option literally says “Dateline,” it is incorrect.
• E. Checkbox ? Boolean — Correct. A checkbox contains true or false.

• Number ? Integer — A Number field maps to Decimal, even when its scale is zero.
• Text Area ? List<String> — A text area maps to a single String, not a list.

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

• A — VARIANT "null" values are not the same as SQL NULL: Correct.

• B — Frequent, single-row DMLs: Incorrect.

• C — Validate data before loading into the target table: Correct.

• D — Use staging tables to manage MERGE statements: Correct.

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

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

cmd 
powershell.exe -ExecutionPolicy Bypass -File C:\Scripts\Configure-VM.ps1

• GPO logon script: Runs only when a user logs on, so configuration may be delayed and is user-dependent.
• GPO startup script: Can work, but requires the VMs to be domain-joined and introduces GPO dependency. It is not specifically tied to Windows deployment.
• Place scripts in a VHD: Merely makes the files available; it does not execute them.

• IPsec: Protects traffic at the network layer, commonly for VPNs; it is not WPA2’s authentication protocol.
• SSL: Protects specific application sessions and has largely been replaced by TLS.
• SSH: Secures remote command-line administration.

• As the project progresses, you gain information, refine requirements, and lock down baselines (scope, schedule, cost). This reduces overall risk and uncertainty because more is known and addressed.
• At the same time, changes become more costly over time. Later changes can affect already approved baselines, cause rework, impact the critical path, require more coordination, and incur penalties or delays, all of which raise the cost of making changes.

• In the source query: apply UPPER() or LOWER() to the column.
• In Power Query Editor: use Text.Upper or Text.Lower on the column, then load.

• This fixes the root cause when comparisons/joins depend on case.
• In DirectQuery, transformations are pushed to the source or query layer; ensure the transformation is supported by your data source/connector.
• After normalization, verify relationships and any downstream visuals that rely on that column.

• Geo-redundant storage (GRS) replicates data to a secondary Azure region, but the secondary copy is normally unavailable for read access.
• RA-GRS provides geo-replication and read-only access to the secondary region, satisfying all requirements.
• Zone-redundant storage (ZRS) replicates data across availability zones within the same Azure region, not separate geographic regions.
• Locally redundant storage (LRS) keeps copies within a single datacenter or region and does not provide geographic resiliency.

• Disabling GPS: Affects location services, not email connectivity.
• Configuring 4G usage only: Does not enable international data access and could prevent connectivity if 4G is unavailable.
• Connecting using a hotspot: Could provide data, but it is not the most direct solution and depends on another network or device.

• Context: You’ve enabled auditing in Dataverse and need to trim audit data to free storage. The question asks which deletion options you can use.

• What the options typically mean:

• About the provided answer (A, C, D): The list includes “by column,” which isn’t a typical or supported way to purge audit data. The more plausible trio is A (by record), B (date range), and C (by table older than date). If the exam expects A, C, D, that seems incorrect or mis-stated in the source.

• Practical takeaway: To reduce audit storage, use per-record deletions, per-table purge by date, and/or date-range deletions as supported by the environment’s audit management UI or admin docs.

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

• A vulnerability scanner automates discovery of known vulnerabilities and misconfigurations across systems. It can contribute to a supply-chain assessment.
• A penetration test actively attempts exploitation and is usually limited to an agreed scope.
• SCAP standardizes vulnerability and configuration assessment data; it is not the analysis itself.
• Illumination tool is not a commonly defined CompTIA Security+ term.

• OpenID Connect (OIDC) is an authentication layer built on OAuth 2.0.
• It returns an ID token, normally a JWT containing identity claims such as the user’s subject, name, email, or other permitted attributes.
• The wellness application can consume those claims without needing a separate user-information call.

• JWT Bearer Token Flow: intended for server-to-server authorization and does not primarily provide an end-user ID token.
• Web Server Flow: is an OAuth authorization-code flow. It can be used with OIDC in some implementations, but “Web Server Flow” alone does not specifically guarantee an ID token.
• User Agent Flow: describes an OAuth flow, not the identity protocol itself.

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

• Microsoft Teams: Connects to Teams-related data, but it isn’t the primary connector for the Power Apps data tables.
• Personal Analytics: Provides personal productivity insights, not application data.
• SQL Server database: Only applies if the app explicitly uses SQL Server as its data source.
• Dataflows: Used for preparing and centralizing data, not as the normal direct connection to a Power Apps app.

• Basic: Self-help only; no technical support or design assessment.
• Standard: Technical support, but not the full proactive architectural guidance required here.
• Professional Direct: Provides proactive guidance and architecture-related assistance.
• Premier: Also supports this, but is a more expensive, enterprise-level option.

• Key difference: DirectQuery leaves data in the on-prem SQL Server and queries it live. That means every visual request can trigger online processing on the source, which can be slower and adds load on the on-prem system. In contrast, Import loads data into the Power BI data model, so visuals render from the in-memory engine (faster).

• Why that helps with the requirements:

• Why not A or B: Both rely on live data via DirectQuery, which contradicts the goal to minimize online processing and visuals performance.

• Why not D: It uses Import, but refreshing hourly adds unnecessary processing and complexity when daily refresh already satisfies currency needs.

• Port 515: LPD/LPR line-printer service
• Port 631: IPP — Internet Printing Protocol
• Port 9100: JetDirect/RAW printing, commonly used by network printers

• Linux machine: Linux could run these services, but the three printer-specific ports strongly indicate a printer.
• Router: Routers may use Telnet and HTTP, but normally would not expose ports 515, 631, and 9100 together.
• Windows machine: Windows can share printers, but this particular service combination is more characteristic of a network printer’s embedded operating system.

• A separate scope using a /32 subnet: A /32 identifies one host, but it is not a practical DHCP scope for this purpose.
• A static IP within the DHCP range: This can cause an IP address conflict if DHCP assigns that address to another device.
• SLAAC: Used for automatic IPv6 address configuration, not for assigning a predictable IPv4 address through DHCP.

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

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

• cloud applications only
• all Web traffic including cloud applications

• Cloud applications only: Only traffic to cloud apps is steered to Netskope for inspection/enforcement; other traffic bypasses.
• All Web traffic including cloud applications: All web-bound traffic, including cloud app traffic, is steered to Netskope.

• Browser isolation, Web traffic only, or a vague “traffic only” option are not the standard two steering modes.
• These two configurations let you decide what traffic Netskope analyzes in real time and what is bypassed.

• The “Answer(s)” field lists B and C (likely incorrect). The explanatory text correctly describes cloud applications only and all Web traffic including cloud applications as the two configurations.

• S3 Lifecycle rules automate actions such as transitioning objects to different storage classes or deleting old objects.
• S3 bucket policies control access permissions; they do not preserve earlier object versions.
• S3 server-side encryption protects data confidentiality by encrypting objects at rest, but it does not prevent deletion or overwriting.

• Accidental deletion or overwriting ? S3 Versioning
• Unauthorized access ? bucket policies and IAM
• Data encryption ? server-side encryption

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

• Admin access to the deployment pipeline (B) – lets the developers use the pipeline and deploy content.
• Contributor access to the Development and Test workspaces (E) – required to deploy items into those workspaces.
• Viewer access to the Production workspace (D) – lets them view Production content without allowing deployment or modification.

• Contributor access to Production (F), because that could allow changes or deployment there.
• Viewer access to Development/Test (C), because Viewer is insufficient for deployment.
• Build permission to Production semantic models (A), because building reports on a semantic model is not required merely to view Production items.

• runParallel is defined as async, so it returns a Promise.
• To use the result, you attach a then handler (or use await inside another async function).

• A: “Async runParallel() .then(data);” is invalid. “async” is a keyword for function declarations, not something you put in front of a call, and you’d need a function as the then-argument.
• B: “runParallel().done(function(data){return data;});” .done is not standard in native Promises (it exists in some libraries). Without a compatible library, this won’t work.
• C: “runParallel().then(data);” is invalid because then expects a function as its argument; data is not a function.
• D: “runParallel().then(function(data){ return data; });” is valid (or equivalently, runParallel().then(data => data);).

• The robust, standard option is D.
• B could work only with a library that provides .done; otherwise it’s not reliable.

• A) configure matching hold and delay timers

• B) configure matching key-strings

• C) configure matching priority values

• D) configure unique virtual IP addresses

• Startup scripts run at computer startup, before any user logs on, making them ideal for machine-wide configuration on each new VM.
• They execute under the Local System account, which is appropriate for initial setup tasks.
• Linking a GPO to the OU ensures every new VM in that domain automatically receives the configuration—great for scalability.

• A) SetupComplete.cmd runs only once, right after Windows Setup, not on every boot, so it isn’t ideal for provisioning multiple VMs consistently.
• B) Logon scripts run per user, not per machine, so they aren’t reliable for initial VM configuration before a user signs in.
• D) Placing scripts in a VHD doesn’t automatically execute them.

• Azure Cosmos DB is a globally distributed NoSQL database service. It stores and retrieves application data, but it does not provide the tools needed to build, test, and deploy predictive analytics models.
• Azure Machine Learning—including the historical Azure Machine Learning Studio—is designed for the machine-learning lifecycle:

kusto 
Event | where EventType == "error"

• == is the KQL equality operator.
• -eq is a PowerShell operator, not KQL.
• is is not the correct equality operator in this context.

text 
Event | where EventType –eq "error"

• Event | search "error" — valid, broad search.
• search in (Event) "error" — valid, broad search.
• Event | where EventType == "error" — valid, targeted filter.

• Data lakes: scalable, low-cost storage for structured, semi-structured, and unstructured data.
• Data warehouses: reliable SQL analytics, governance, and performance features.

• Data lake: Primarily provides flexible, scalable storage but may lack warehouse-style reliability and governance.
• Data warehouse: Strong for structured analytics but less flexible for raw and unstructured data.
• All of these: The individual lake and warehouse do not, by themselves, unify the siloed architecture.

• Why: ADS is designed to collect information about on-premises environments to plan migrations. It inventories details like hostname, IP address, MAC address, OS, hardware, and installed software, plus dependency mappings. This data helps you understand your current environment before moving to AWS.

• How it differs from the other options:

• Practical use: Install the ADS agent on on-prem hosts to collect data, then view the inventory in Migration Hub to inform migration planning and sequencing.

• The target API uses HTTPS, so Mule must validate the server’s TLS certificate.
• The TLS configuration is set to None, meaning no custom truststore is configured.
• Mule therefore uses the JRE’s default truststore to determine whether the target certificate is trusted.
• If the issuing CA certificate is in that truststore, the TLS handshake can succeed.
• If it is absent—or the certificate is otherwise invalid—the request fails with a TLS/handshake error.

• A Layer 2 switch checks the destination MAC address in its MAC address table (CAM table).
• If the destination MAC is unknown, the switch cannot select a specific outgoing port.
• It therefore performs unknown-unicast flooding, sending the frame out every other port in that VLAN.
• The frame is not sent back through the port where it arrived.

• Answer: False. Agents and managers CAN create knowledge articles from Community questions.

• Why: In ServiceNow, a Community question can be converted into a Knowledge article using the Create Knowledge (or Convert to Knowledge) action. This allows what customers asked to become a reusable article for others.

• How it works (high level):

• Permissions: This ability depends on having the right roles/permissions (e.g., agents or knowledge managers). If you don’t see the option, check your role assignments or the knowledge-management configuration.

• Quick take: If a question in Community is valuable for others, a trained agent can turn it into a Knowledge article, making it available for self-service.

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

Flat organisation

• Few levels of management
• A wide span of control—managers supervise many employees
• Shorter communication channels
• More employee autonomy and quicker decisions
• Fewer formal promotion levels

Tall organisation

• Many levels of management
• A narrow span of control—managers supervise relatively few employees
• A clear hierarchy and reporting structure
• More formal supervision and communication channels
• More obvious promotion and career stages

• User1 can sign in because the account is cloud-only. It does not depend on the on-premises domain.
• User3 can sign in because the account uses Password Hash Synchronization (PHS). Azure AD has a synchronized password hash and can validate the sign-in even when connectivity to on-premises Active Directory is unavailable.
• User2 cannot sign in because the account relies on Pass-through Authentication (PTA). PTA sends the authentication request to an on-premises PTA agent, which must contact a domain controller. With the internet connection from on-premises lost, that validation cannot occur.

• Basic: billing/subscription support only; no technical support requests can be opened.
• Developer, Standard, Professional Direct, and Premier: include technical support and allow opening new support requests.

• If option A corresponds to “Developer, Standard, Professional Direct, Premier,” that is the correct choice.
• If the option text is really “Premier only,” that would be incorrect per current Azure docs.

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

• Modelo de embeddings de texto: trabalha principalmente com texto, não sendo adequado para imagens.
• Modelo generativo multimodal: pode interpretar ou gerar conteúdo de vários tipos, mas não é a opção específica para busca por similaridade.
• Modelo de geração de imagens: cria imagens a partir de entradas, não realiza busca multimodal.

• Separate accounts/domains create a strong administrative boundary between non-production and production.
• Separate projects provide distinct IAM boundaries, billing, quotas, service accounts, and resources.
• Developers can receive permissions in the development project without automatically gaining access to production.
• Production administrators can be restricted from development resources, supporting separation of duties and least privilege.

• A: Creates excessive project fragmentation without being required by the stated requirement.
• C: Keeps development and production under one account and does not clearly separate administrative duties.
• D: Uses one account and only two projects; it provides some project isolation but weaker organizational separation.

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

• Honeypots: Decoy systems or services designed to attract attackers. Legitimate users should not access them, so activity on a honeypot is a strong indicator of unauthorized activity. Security teams can also observe attacker behavior.

• DNS sinkhole: Redirects requests for known malicious domains to a controlled internal server or blocks them. If an infected workstation attempts to contact command-and-control infrastructure, the sinkhole records the request and helps identify the compromised device.

• Tokenization: Protects sensitive data by replacing it with tokens.
• CI/CD: Automates software development and deployment.
• Threat modeling: Identifies potential risks before or during system design.
• Data obfuscation: Makes data harder to understand, but does not detect intruders.

• ?????? CPU
• ?????????????????
• ??????????????????????????
• ???????????? throughput
• ??????????????????????????????

• A ??????? system software ????????????????????????????????? ??????????????????????????????????
• B ?????????????????????????? ????????????????????????? ?????????????????????????????
• D ????????????????????????? ?????????????? ?????????????????????????????????????????