Huawei H13-723_V2.0 Exam Prep
HCIP-Big Data Developer V2.0 (Page 50 )

1. Write a structured log entry to CloudWatch Logs containing:

1. Create a CloudWatch Logs metric filter that:

text 
ApiRequests 
Operation=GetOrders 
ResponseCode=500 
Version=2.4.0

• B is incorrect: CloudWatch Logs Insights queries analyze logs but do not directly publish metrics in this manner.
• C is incorrect: ALB access logs do not contain arbitrary Lambda response metadata as custom fields.
• D is incorrect: X-Ray traces and insights are not the appropriate mechanism for creating these custom, dimensioned application metrics.

• Feedback form: Captures opinions, not necessarily actual behavior; users may not respond.
• Questionnaire: Relies on memory and subjective judgments about usefulness.
• Interviews: Can provide valuable qualitative insights, but a sample of users may not represent overall usage accurately.

• Product recall: Premature before confirming a violation or assessing risk.
• Notify the regulatory authority: May be required later, especially if the discrepancy affects safety or compliance, but first investigate and verify the facts.
• Inform production: Not the initial regulatory assessment step; production may become involved if a packaging or manufacturing error is identified.

• API tool matcher: runs a deterministic normalization command after the API tool returns.
• Write/Edit matcher: checks whether the target path begins with src/api/ and runs the linter.

json 
{ 
  "hooks": { 
    "PostToolUse": [ 
      { 
        "matcher": "api_tool", 
        "hooks": [ 
          { "type": "command", "command": "normalize-to-snake-case" } 
        ] 
      }, 
      { 
        "matcher": "Write|Edit", 
        "hooks": [ 
          { "type": "command", "command": "lint-if-under-src-api" } 
        ] 
      } 
    ] 
  } 
}

• Due diligence: Investigating and evaluating a third party before entering into or continuing a business relationship.
• Attestation: An independent party provides assurance about an organization’s claims or controls. A SOC 2 examination is an example of an attestation engagement, but the analyst requesting and reviewing the report is performing due diligence.
• Internal audit: Reviews the organization’s own internal controls.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.

• A — Improved management of storage space: Correct.

• B — Improved supplier relationships: Correct.

• C — Improved pricing decisions: Correct.

• D — Non-product-specific costs must be apportioned: Incorrect.

• E — Profitability of each customer group: Incorrect.

• The selling division receives a credit based on a favourable transfer price, often market price or full cost plus a profit margin.
• The receiving division is charged a lower amount, such as marginal cost or another agreed price.
• The difference is accounted for centrally by head office or a corporate adjustment.

• 10 minutes have elapsed, or
• 20 MB of accounting data has accumulated

• True positive: The scan reports a vulnerability that really exists.
• False positive: The scan reports a vulnerability that does not exist.
• True negative: The scan correctly reports no vulnerability.
• False negative: The scan fails to detect a vulnerability that is actually present.

• Run the backup with WITH CHECKSUM
• Store the backup on an SMB network share

sql 
BACKUP DATABASE DB1 
TO DISK = '\\FileServer\SqlBackups\DB1_full.bak' 
WITH CHECKSUM;

• DMS does not create the SQL Server backups for you.
• You must provide a valid full database backup.
• You must continue taking transaction log backups while the source database remains online.
• The full backup and subsequent log backups must be available in the SMB share that DMS can access.
• WITH CHECKSUM enables backup checksum validation, helping detect backup corruption.

• NTLM: Uses Windows challenge-response authentication and does not provide the normal web-based MFA redirect flow.
• Single Sign-On: Automatically reuses existing credentials; it is intended to avoid prompting, not to support an MFA workflow.
• Transparent: Intercepts the session without redirecting the user to a separate authentication page.

1. x = -100
2. -100 < x < 100
3. 100 = x < 1000
4. x = 1000

• -500 ? class 1
• 0 ? class 2
• 100 ? class 3
• 1000 ? class 4

• Remote and global work: Access is based on the approved device, not a specific office or geographic location.
• Seamless login: Users may not need to repeatedly enter credentials on a recognized device.
• Limited equipment: It uses devices employees already have rather than requiring separate hardware.

• Geotagging: Restricts access based on location and may prevent legitimate remote work.
• Smart cards: Require issuing and managing additional physical equipment.
• Time-based logins: Limit access by time and do not provide a seamless authentication experience.

• Virtual introductions: Team members share their role, experience, location, and working preferences.
• Online icebreakers: Short, informal activities such as “two truths and a lie.”
• Virtual coffee chats: Pair team members for informal, non-project conversations.
• Collaborative problem-solving: The team works together on an online puzzle or scenario.
• Retrospectives: The team discusses what went well, what did not, and how to improve.
• Working-agreement sessions: The team agrees on response times, meeting etiquette, communication channels, and handoffs.
• Recognition sessions: Members acknowledge one another’s contributions.
• Remote workshops: Teams jointly create plans, diagrams, or schedules using collaboration tools.

1. Start with the number of devices: 260 usable addresses.
2. Use the formula:

1. Test the host-bit values:

1. IPv4 has 32 total bits:

• /24: 254 usable — too small
• /23: 510 usable — sufficient
• /22: 1,022 usable — more waste
• /21: 2,046 usable — even more waste

• /27 (255.255.255.224)

• /26 (255.255.255.192)

• /25: Creates only 2 subnets, not 3
• /28: Provides only 14 usable hosts per subnet

• A user connects with their Google account.
• Google associates the user’s SSH key with that identity.
• IAM roles determine whether they can log in.
• Access can be tied to a specific employee for auditing.
• Removing the IAM role removes their login access.

• compute.osLogin: regular OS login access
• compute.osAdminLogin: OS login with administrative privileges, typically including sudo

text 
enable-oslogin=TRUE

• Root path cost
• Port priority
• Port ID

text 
interface GigabitEthernet0/1 
 spanning-tree vlan 10 port-priority 64

• Interface number: Helps form the port ID but is not normally configured as the preference value.
• VLAN priority: Not used to select a preferred forwarding interface.
• Hello time: Controls how often BPDUs are sent; it does not select a preferred port.

1. Create Workspace2 with Lakehouse2 — F
2. Migrate the Employee table to Lakehouse2 — E
3. Assign the data engineer the Contributor role for Workspace1 — D

Why

• Sharing Lakehouse1 would not provide the required isolation.
• Viewer access would not allow writing to Customer.
• Giving Contributor access to Workspace2 would expose the sensitive table.

• Job Links ? URL ID: Mainly summarizes link performance; it is not the easiest place to retrieve individual email addresses by alias.
• Tracking Overview ? Clicks: Provides aggregate click metrics, not a targeted list for one aliased link.
• Click Activity ? Link View: Focuses on link-level reporting, but the question’s intended workflow for locating clicks tied to a specific placement/alias is Email Overlay.

• A is correct: It establishes the revised dates and identifies the effect on the critical path.
• B is premature: Stakeholders should be informed after the impact has been assessed and the updated schedule is understood.
• C is not automatically appropriate: Fast-tracking may introduce additional risk and should be considered only after analyzing schedule options.
• D is premature: Adding resources may not resolve a dependency and could increase costs without addressing the actual constraint.

• Required response and resolution times
• Availability or uptime targets
• Performance standards
• Support obligations
• Remedies or penalties for failing to meet the terms

• SOW (Statement of Work): Defines the project’s scope, tasks, deliverables, and schedule.
• MOA (Memorandum of Agreement): Describes agreed responsibilities between parties, often for a specific activity.
• MOU (Memorandum of Understanding): Records a mutual understanding or intention, usually less formal than a contract.

• Instant messaging/chat: Can be abused to send malicious links or attachments, but is not the answer most directly associated with high-risk file sharing.
• E-mail: A common malware delivery method, but the question emphasizes an application type known for direct file exchange.
• End-to-end applications: This describes communication protection or architecture, not a specific malware distribution risk.

• Streams — track change data for tables or views.
• External tables — reference data stored in an external cloud storage location.

• Role — account-level security object.
• Warehouse — account-level compute resource.
• User — account-level security object.
• Share — account-level object used to share data.

• Storage usage of files stored in Microsoft Teams: SharePoint site usage report

• Number of active users per team: Microsoft Teams usage report

1. SharePoint site usage report
2. Microsoft Teams usage report

• A. Remove rows where Sales[Status] is Canceled

• E. Remove Sales[Canceled Date]

• B: Removing Sales_Date would remove information users need—the date portion.
• C: Changing Delivery_Time to Integer could alter its meaning or precision and is not necessarily safe.
• D: Splitting the date/time column creates additional columns rather than simply removing unnecessary data.

• An Adj-SID does not necessarily need manual configuration.
• It can often be dynamically allocated by the router, although manual configuration may also be possible.
• The adjacency information is advertised through the IGP, such as IS-IS or OSPF.

• It is identified by an Adj-SID.
• It represents a particular adjacency of a node.
• Its meaning is generally local to the advertising node; unlike a Node-SID, it is not a globally reusable instruction across the network.

• Bronze: Raw ingested data
• Silver: Cleaned, validated, and transformed data
• Gold: Business-level data for analytics, dashboards, and reporting

• VPC: A logically isolated virtual network within a cloud provider; it describes network design, not the user-access model.
• NFV: Runs network services as software instead of on dedicated hardware.
• SaaS: Delivers software over the internet. Although the application may be delivered as SaaS, the question emphasizes its availability to multiple user groups, which points to multitenancy.

• STIX: A standardized format for exchanging cyber-threat intelligence.
• OVAL: A language and framework for describing and assessing system vulnerabilities and configuration issues.
• Threat intelligence feed: Provides current indicators or threat information, but is not specifically a reference for common application exploitation techniques.
• CVE: A catalog of publicly disclosed vulnerabilities, identified by unique CVE numbers.

• On-premises resources, such as an existing database
• Cloud resources, such as Azure services or virtual machines
• Connectivity that allows the application to use both environments

• Public cloud: resources are entirely provided through a public cloud provider.
• Private cloud: resources are dedicated to one organization, typically on-premises or privately hosted.

• A — Use getRecordTypeInfosByDeveloperName()

apex 
  Id rtId = Schema.SObjectType.Account 
      .getRecordTypeInfosByDeveloperName() 
      .get('Business_Account') 
      .getRecordTypeId();

• C — Query the RecordType object

apex 
  RecordType rt = [ 
      SELECT Id 
      FROM RecordType 
      WHERE SObjectType = 'Account' 
      AND Name = 'Business Account' 
      LIMIT 1 
  ];

• B: An outbound SOAP call is unnecessary and inefficient.
• D: Hardcoding an ID is not dynamic, and IDs can differ between orgs.

1. System prompts can authorize users — No

1. System prompts can reduce TPM consumption — Yes, with qualification

1. System prompts guide generative AI behavior — Yes

• SQL injection: Manipulates database queries through application input.
• XML external entities (XXE): Abuses XML parsers to access files, internal systems, or other resources.
• Cross-Site Request Forgery (CSRF): Tricks an already authenticated user’s browser into sending an unwanted request. It generally does not steal session cookies.

• Sustainability
• Performance efficiency
• Reliability

• A — If there is no demand, there should be no production.

• B — Not all sales equal profit.

• C — Stocking up on inventory is bad for business.

• D — All costs, except materials, are considered fixed.

• E — Departments should operate at full capacity regardless of bottlenecks.

• Accept: Acknowledge the risk and take no additional action.
• Transfer: Shift the risk or its financial impact to another party, such as through insurance or outsourcing.
• Mitigate: Reduce the likelihood or impact of the risk, such as by implementing security controls.
• Avoid: Eliminate the activity or exposure that creates the risk.

• Vulnerability scanner: Identifies technical weaknesses in systems, applications, or devices.
• Penetration test: Simulates attacks to determine whether vulnerabilities can be exploited.
• SCAP (Security Content Automation Protocol): Uses standardized formats and protocols for automated vulnerability, configuration, and compliance checks.
• Illumination tool: Maps and analyzes broader supply-chain exposure and third-party risk.

• Microsoft Purview portal: Create and manage sensitivity labels and configure support for sensitivity labels used with Office files in SharePoint and OneDrive.
• SharePoint admin center: Primarily manages SharePoint settings. Older guidance and PowerShell procedures used SharePoint tenant configuration, which can make this question confusing.
• IRM: Concerns Information Rights Management and is a separate protection mechanism; it should not be used to identify the portal for configuring Microsoft Purview sensitivity labels.

• Assign endpoints to a group based on the result of one policy.
• Use that group as the scope of another policy.
• This effectively passes the endpoints from one policy’s processing flow to another.

• To identify the number of errors: select Column quality. It shows the percentage and count of Valid, Error, and Empty values for each column.
• To resolve errors: use the appropriate error transformation:

• B — Both inner and outer classes can be declared as with sharing.

• C — Inner classes do not inherit sharing settings from the container class.

apex 
public with sharing class OuterClass { 
    public with sharing class InnerClass { 
        // Explicitly uses sharing rules 
    } 
}

• Disable high concurrency: This changes session-sharing behavior but does not provide dedicated compute or true workload separation.
• Modify the number of executors: Adjusts resources within a Spark job; it does not isolate bronze and silver processes.
• Set the default environment: Controls libraries and runtime configuration, not compute isolation.

• A is incorrect: Flow Debugger is for debugging Salesforce Flows, not Trust Layer masking.
• B is incomplete/misleading: Requesting audit data may be part of reviewing the results, but collection and storage must first be enabled.
• C is correct: It describes the initial validation step.

CIMA P3 topics

• IT governance and systems strategy
• Systems development and implementation
• Change and project governance
• Strategic and business risk

• A — Plan for new systems: The committee should help identify and prioritise systems requirements and ensure planned systems support organisational needs.
• D — Consider competitive issues: New information systems may affect Y’s competitive position, service quality and efficiency. These strategic implications should be considered.
• E — Ensure the system meets company goals: This is a key governance responsibility. The committee should ensure the project remains aligned with Y’s objectives and delivers business value.

• B — Develop new systems: Detailed system development should be performed by IT specialists and project teams, not the steering committee.
• C — Manage the project: The project manager should handle day-to-day project management. The steering committee should provide oversight, challenge and key decisions, rather than manage daily activities.

• Injection
• Broken access control
• Authentication failures
• Security misconfiguration
• Cross-site scripting

• STIX: A standardized language and format for exchanging threat intelligence.
• OVAL: Used to describe and assess system vulnerabilities and configuration issues.
• Threat intelligence feed: Provides current indicators and intelligence about threats, but not necessarily a structured overview of common application exploitation methods.
• CVE: A catalog of individually identified, publicly disclosed vulnerabilities.

• Explain questions from the exam page
• Check whether the stated answer is technically correct
• Compare answer choices and eliminate distractors
• Clarify Azure AI concepts and terminology
• Point out when an answer key appears unreliable or when an image is missing

• Two-part tariff pricing: $10 per unit
• Dual pricing: $20 per unit

Two-part tariff pricing

Dual pricing

• Division X, the seller, is credited with the market price: \(\$20\)
• Division Y, the buyer, is charged the marginal cost: \(\$10\)