AICPA CPA-Business Exam Prep
CPA Business Environment and Concepts (Page 7 )

• Recovery procedures actually work
• Recovery time and recovery point objectives can be met
• Staff understand their responsibilities
• Contact details, dependencies, and technical configurations are accurate
• Gaps or conflicts exist in the plan

• Not version-controlled: Creates a risk of using an outdated copy, but the plan might still be effective.
• Contact information needs updating: This is a specific weakness that can be corrected, often identified during testing.
• Not approved by senior management: Approval is important for authority and resource commitment, but an untested plan presents the most direct risk that recovery will fail when needed.

• IaaS: You manage the virtual machine’s operating system, configuration, applications, and data. Azure manages the physical infrastructure and virtualization platform.
• PaaS: You deploy applications without managing the underlying operating system or servers.
• SaaS: You consume a complete application managed by the provider, such as Microsoft 365.

• Product Owner: May attend, but is not required unless also working as a Developer.
• Scrum Master: May attend to help facilitate or coach, but is not required.
• Developers: Must participate because the event is specifically for them.

• What it says: you can add a cost when you adjust inventory, and that cost is posted automatically to a specific GL account.
• Reality: yes, you can adjust both quantity and value via an inventory adjustment journal. The cost on the journal line affects the inventory value.

• The general ledger postings are not arbitrary. the actual accounts used are determined by your item posting group and the system’s posting definitions. In practice, the adjustment debits/credits the appropriate inventory-related accounts (e.g., Inventory asset and a related offset such as an adjustment or COGS account) based on configuration.
• So, the cost change does not go to a single “manual” GL account you pick per line unless your posting setup maps to that account.

• The concept is true (you can adjust cost and have GL impact), but the claim that it posts to a single, specific GL account is oversimplified—the accounts come from your posting configuration.

• Correct answer: S3 Versioning

• Why the other options aren’t suitable for this protection:

• Quick tip: For enhanced protection, enable Versioning (and consider related features like Object Lock for write-once scenarios in specific compliance cases).

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

• Answer: No

• Why: Using several Azure AD directories (tenants) would create separate identity stores for each division, which significantly increases administrative overhead. You’d need cross-tenant access management, separate governance, and duplicated admin efforts, which goes against the goal of minimizing administrative work.

• How to meet the goal instead:

• The correct answer is A: CCTV recordings are not regularly reviewed.

• CCTV is a monitoring/control mechanism. If recordings aren’t reviewed, security events (break-ins, policy violations, equipment tampering) can go undetected and unaddressed.
• Regular review is essential for deterrence, incident response, and forensic evidence. Without it, the entire CCTV control provides little value.

• B (records deleted after one year) affects forensic availability, but it’s a data-retention issue rather than the ongoing effectiveness of the surveillance program.
• C (footage not recorded 24x7) creates gaps in coverage, which is a concern, but regular review of available footage still supports detection; 24x7 coverage is a separate policy/perimeter issue.
• D (cameras not in break rooms) is more about privacy and space planning than core data-center security monitoring.

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

• Multiple nodes: Data is replicated several times in the primary region.
• Separate geography: A copy is asynchronously replicated to a secondary Azure region.
• Readable secondary: RA-GRS provides read-only access to the secondary replica, even when the primary region is available.

• GRS: Replicates to another region but the secondary copy isn’t normally readable.
• ZRS: Replicates across availability zones in the same region, not a separate geographic region.
• LRS: Keeps replicas within a single datacenter or region and provides no geographic redundancy.

• Create a record-triggered Flow on Opportunity.
• Run it when the record is created or updated.
• Add entry criteria such as Probability > 50%.
• Use Create Records to create the related Sales Demo Request, populating its Opportunity lookup.

• Apex Trigger: Possible, but unnecessary custom code for a straightforward automation requirement.
• Workflow Rule: Cannot create a related custom record.
• Process Builder: Could create a record, but Flow is Salesforce’s preferred and more capable declarative automation tool.

• TCP is connection-oriented. It establishes a connection before data transfer using a three-way handshake (SYN, SYN-ACK, ACK), enabling reliable delivery, ordering, and flow control.

• UDP is connectionless. It sends datagrams without a prior connection and provides no guarantee of delivery, order, or protection against duplicates; any reliability is up to the application.

• B incorrectly states UDP uses acknowledgment packets; UDP has no built-in ACKs.
• C wrongly claims UDP provides reliable transfer and that TCP is connectionless.
• D misstates framing bits; neither protocol uses the listed TCP/UDP handshake bits in frames.

• Planning – identifying the need, objectives, scope and resources.
• Analysis – understanding business requirements and current problems.
• Design/development – determining how the system will work.
• Implementation – installing the system and putting it into operation.

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

• Amazon Cognito is designed for customer-facing apps to handle user sign-up, sign-in, and access control, and it can federate identities from social providers (Facebook, Google, etc.) or enterprise IdPs via SAML/OpenID Connect.
• You can configure a Cognito User Pool and connect social identity providers, then use tokens (JWT) to authorize backend API calls.

• AWS Directory Service is for connecting your AWS apps to an existing directory (like Active Directory) for enterprise users, not social login for customer apps.
• AWS IAM is for managing access to AWS resources, not end-user authentication for your website.
• AWS IAM Identity Center (AWS SSO) provides SSO for AWS accounts and enterprise apps, not typical social logins for consumer-facing websites.

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

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

• Ethical red-teaming is adversarial testing aimed at uncovering weaknesses and potential exploits in an AI system before deployment.
• A (improving accuracy) is not the primary?? of red-teaming.
• B (simulate model risk scenarios) is related but narrower; red-teaming centers on finding vulnerabilities and risk exposure, not just simulating risks.
• D (ensure compliance) is not the main goal of red-teaming.

• You normally do not create a new sensitive information type for credit card numbers. Microsoft Purview already provides a built-in Credit Card Number sensitive information type.
• The required sequence should generally be:

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

powershell 
Get-AzureVM -ServiceName <service-name> -Name <vm-name> | 
  Set-AzureStaticVNetIP -IPAddress <private-ip> | 
  Update-AzureVM

• New-AzureRMVMConfig configures VM settings but does not itself assign the static IP.
• Set-AzureSubnet is not the appropriate cmdlet for assigning a VM’s private IP.
• The Azure portal option mentioned in the question was not the intended method for this older deployment model.
• Changing settings in Windows Network and Sharing Center is incorrect because Azure assigns the IP through the VM’s virtual network interface; manually configuring it inside the guest can cause conflicts.

• Why Ishikawa:

• Why not the others:

• VPC: A logically isolated virtual network in a cloud environment; it describes networking, not shared application access.
• NFV: Replaces dedicated network appliances with virtualized network functions.
• SaaS: A cloud service model in which users consume an application without managing its infrastructure. It could describe how the application is delivered, but the question emphasizes serving multiple user groups, which points to multitenancy.

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

• Drop violating frames
• Log or alert on the violation
• Shut down or restrict the port

• Load balancer: Distributes application traffic; it does not control switch MAC learning.
• IPS: May detect some network attacks but is not the primary control for switch MAC-table exhaustion.
• NGFW: Protects traffic crossing network boundaries, while MAC flooding occurs at the switching/LAN layer.

• Why: Table.Profile returns a per-column profile that includes statistics such as count, null count, distinct count, and standard deviation. It also provides min/max and average where applicable, which matches the requested metrics (Count, Average, Null count, Distinct count, Standard deviation).
• Syntax: Table.Profile(table as table, optional additionalAggregates as nullable list) as table
• How it helps: After running Table.Profile on your table, you can extract the per-column stats you need and display them in your semantic model or report.

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

• An Anypoint VPC provides private network connectivity for CloudHub applications.
• An IPsec VPN tunnel or AWS Direct Connect connects that VPC to the customer’s on-premises network without exposing the database to the public internet.
• The VPC and on-premises firewalls must allow the required traffic, routes, and ports.

• Static IP addresses only identify the application’s outbound traffic; they do not create a private network path to the database.
• A Dedicated Load Balancer does not replace the required network connection to the on-premises environment. It is also unnecessary merely to reach individual databases.
• Moving sensitive databases to a DMZ is not the intended architecture and could reduce their protection.

• Failed login attempts
• The account being targeted
• The source user or system
• Time and frequency of attempts

• Two-factor authentication: Helps prevent unauthorized access, but does not primarily detect the employee’s attempts.
• Firewall: Controls network traffic; it generally does not monitor individual login attempts.
• Intrusion prevention system (IPS): Can detect certain network attacks, but this scenario is best addressed through authentication and audit logging.

• The AWS Support Concierge is a specialized team within Enterprise Support whose primary role is handling billing and account questions and helping with account setup and getting started.
• They are not the source for architecture guidance or development assistance; those services are provided by Technical Account Managers (TAMs) or Solutions Architects as part of Enterprise Support.
• For technical support cases, customers typically interact with AWS Support engineers or the TAMs, not the Concierge. The Concierge may route or coordinate related requests, but they don’t provide the technical resolution.

• What Concierge does: billing and account inquiries, onboarding help, coordination with AWS support.
• What Concierge does not do: provide architecture/design guidance or in-depth technical support case resolutions.

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

• Authenticating websites with TLS/HTTPS
• Enabling certificate-based VPN authentication
• Signing or encrypting email
• Supporting device or user authentication

• VLAN tagging: Uses network-frame tags, such as 802.1Q; it does not rely on X.509 certificates.
• LDAP: May integrate with PKI in some environments, but X.509 certificates are not most commonly associated with LDAP itself.
• MFA: Certificates can be one authentication factor, but X.509 is fundamentally a PKI technology.

• Step 1: From Power BI Desktop, select Get Data, choose Folder, enter the folder path, and click OK, then choose Transform data to open Power Query Editor.

• Step 2: In Power Query Editor, expand the Attributes column.

• Step 3: From the Power Query Editor, select the Content column and use Home > Combine Files (aka “Combine binaries”) to consolidate the files.

• Automation handles repetitive tasks, and orchestration coordinates responses across tools (SIEM, SOAR, EDR, etc.).
• This allows the security team to process more events with the same number of people, improving throughput and response times.
• Analysts can focus on more complex tasks like investigation and threat hunting instead of manual triage.

• It increases complexity: automation can reduce complexity when well-implemented; complexity is not the main intended benefit.
• It removes technical debt: automation/OR focuses on current incident response efficiency, not primarily on architectural debt.
• It adds additional guard rails: governance is important but not the core value of automation/orchestration within a SIEM.

• Coordinate and manage the assessment team
• Assign assessment activities
• Direct interviews, examinations, and tests
• Ensure the assessment follows the CAP

• Answer key: Lead Assessor — likely wrong
• CAP-based answer: C3PAO

• Leadership and stakeholder commitment
• Business capability and skills
• Organizational culture
• Availability of resources
• Ability to manage and sustain change
• Impact of the proposed transformation

• How ready the organization is
• Which areas require urgent attention
• How difficult each issue may be to resolve
• Risks that could affect implementation

• A: Places the assessment in Phase B and refers vaguely to creating views; this is not the prescribed technique.
• B: An Implementation Factor Assessment and Deduction Matrix is not the primary TOGAF technique described for business transformation readiness.
• D: A Business Scenario helps identify requirements and stakeholder concerns, but it is not the main technique for assessing organizational readiness.

Simple explanation

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

• Reusing features across different models and teams
• Consistent feature definitions
• Managing feature versions and metadata
• Using features for both training and inference

• SageMaker Data Wrangler: Prepares and transforms data; it is not primarily a shared feature repository.
• SageMaker Clarify: Helps detect bias and explain model predictions.
• SageMaker Model Cards: Documents models, including intended use, risks, and evaluation results.

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

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.

• Uses on-premises data or resources
• Runs components in the cloud
• Can scale across multiple cloud environments when demand increases

• Public cloud: Resources are hosted entirely by a cloud provider.
• Private cloud: Resources are dedicated to one organization, usually in its own environment.
• Hybrid: Combines on-premises and cloud resources.

• VMs without NGT: Not clearly a migration blocker on its own; NGT (Nutanix Guest Tools) status isn’t the typical gating factor for live migration during maintenance.
• VMs marked as an Agent: Not a standard, widely-known migration blocker; agents aren’t the typical reason a VM can’t be migrated.
• Memory Overcommitted VMs: While memory pressure can affect placement, memory overcommitment isn’t a fundamental reason a VM would be labeled non-migratable during maintenance.
• VMs with attached Volume Groups: This is the strongest candidate. A Volume Group is a set of volumes bound to a VM; moving the VM would entail relocating and reattaching those volumes, which can complicate or block live migration during maintenance.

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

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.

• Custom domains
• 10 GB storage per web app
• Each app runs on dedicated compute
• Load balancing between instances is included
• Costs minimized

• Answer: A (Standard)

• Why:

• Note: In App Service, multiple apps in the same plan share compute resources. If you truly need isolation per app, you’d typically use separate App Service Plans, which increases cost beyond a single Standard plan.

• If the account name includes the parsed search string, show the element; otherwise hide it.
• In CSS, to show an element you can set display to a visible value (commonly 'block' for block-level elements), and to hide you set display to 'none'.

• The ternary should map true to a visible display value and false to 'none'.
• Therefore the placeholder should be replaced with 'block' : 'none' (so the code becomes: accountName.includes(parsedSearchString) ? 'block' : 'none').

• There are several typos in the snippet (e.g., quesrySelectorAll, toLOwerCase, Style.display). In a working version you’d also fix those to document.querySelectorAll, account.innerHTML.toLowerCase(), and account.style.display.