CIMA BA2 Exam Actual Questions
Fundamentals of Management Accounting (Page 43 )

• Network Security Groups (NSGs) control network traffic to and from Azure resources.
• By applying NSGs to the web tier and the database tier (subnets or NICs), you can:

• NSGs provide the necessary granularity (source/destination, port, protocol) to enforce the desired traffic patterns between tiers.
• For easier management you can use separate subnets for each tier or, optionally, use Application Security Groups to simplify rule management.

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.

• Correct answer: A — The degradation of a service.

• Why: A service request is a formal request from a user for something that is pre-approved and routine (e.g., provisioning a laptop, replacing a toner cartridge). Those are typical service request actions. The degradation of a service, however, is an incident: it describes a problem affecting service quality or availability and is handled by Incident Management (and possibly Problem Management), not as a standard service request.

• Quick note on the other options:

• Le rôle n’a pas de clés propres. Des identifiants temporaires (via STS) sont émis lorsque quelqu’un ou quelque chose « assume » le rôle.
• La trust policy déclare qui peut assumer le rôle (par ex. une instance EC2, un utilisateur IAM, ou un service comme Lambda).
• Une fois attaché à une ressource (par exemple comme un instance profile sur une EC2), l’application peut appeler les services AWS avec les permissions du rôle.

• Respect du principe du moindre privilège: on accorde uniquement ce qui est nécessaire.
• Pas de stockages de clés sur les instances; les credentials se renouvellent automatiquement.

• Rôles pour EC2, rôles pour Lambda, accès cross-compte, etc.

• Assign a Teams license to a user — Licenses are assigned through the Microsoft 365 admin center, Microsoft Entra ID, or PowerShell.
• Deploy the Teams client — The Teams admin center manages Teams policies and apps, but it is not the primary tool for deploying the desktop client.
• Prevent users from creating teams — Team creation depends on controlling the creation of Microsoft 365 groups, generally configured through Microsoft Entra ID and PowerShell rather than directly in the Teams admin center.

• The correct answer: C. Tokenization

• Why:

• Why the others are weaker:

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

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

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

Why B works

• AWS KMS keys are Regional resources. A normal customer managed key in Region A cannot be used directly in Region B.
• A customer managed multi-Region KMS key (MRK) has related key replicas in both Regions. The replicas share key material and key ID, although each has a Regional ARN.
• With client-side encryption, the application encrypts the data before storing it in S3. Cross-Region replication then copies already-encrypted objects, so S3 does not need to decrypt and re-encrypt them with a different Regional key.

Why the other choices are weaker

• A and C: SSE-S3 uses Amazon-managed S3 keys, not the required customer managed KMS key.
• D: SSE-KMS can work only if the solution creates and configures the appropriate KMS key or multi-Region key replica in each Region. As written, it says to create a customer managed KMS key in each Region, which implies separate keys—not the same KMS key. Replication also requires additional KMS permissions and destination encryption configuration.

• The app on EC2 connects to Aurora using DB credentials stored on the instance. Secrets Manager centralizes these credentials and can rotate them automatically, eliminating manual updates on each EC2 host.
• Automatic rotation reduces operational overhead and enhances security because credentials are rotated on a schedule without code changes.
• The app can retrieve the current secret at runtime (e.g., via the AWS SDK) and use it to authenticate to Aurora, avoiding reliance on locally stored files.

• B (Parameter Store) can store secrets but lacks seamless built-in rotation for database credentials like Secrets Manager; rotation often requires more custom work.
• C (S3) would require complex tooling to rotate and securely fetch credentials and still risks exposure if access policies aren’t perfect.
• D (Encrypted EBS volumes) would store credentials locally on each instance and does not automate rotation or centralized management.

• The correct option is A: Data architecture.

• Why: In the AWS CAF, the Platform perspective covers the technical foundation and architecture that enable cloud workloads to run reliably and efficiently. This includes how data is modeled, stored, and accessed across the enterprise—the core of data architecture.

• Quick mapping for the other options:

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

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

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

• Correct answer: C: Amazon Comprehend.

• Why: The library wants to classify books based on their text content. This is an NLP (natural language processing) task. Amazon Comprehend is AWS’s managed NLP service that can perform content classification (including creating custom classifiers) and extract meaningful information from text. The other services are not focused on text classification:

• Quick note: In practice, you’d store the books in S3, extract text if needed (e.g., from PDFs with Textract), and then use Comprehend to classify the documents into topics or genres.

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

Simple explanation

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

• What the goal is: You want to add guest (external) users to your Azure AD tenant contoso.com, one entry per external user in a CSV.

• The proposed solution uses New-AzureADUser for each external user. Why this isn’t correct: New-AzureADUser creates a regular (internal) user in your directory. It does not create a guest/B2B user invite. So you’d end up with 500 ordinary accounts, not guest accounts with external access.

• The correct approach: Use New-AzureADMSInvitation for each external user. This invites the external user to your directory and creates a guest user (a B2B collaboration user) in your tenant. The invited user then accepts the invitation and gains access as a guest.

• Azure AD vs directory/tenant: Azure AD is the cloud identity service. A directory (also called a tenant) is your specific instance of that service (contoso.com in your scenario). The terms are often used interchangeably in exams.
• Guest user vs internal user: A guest user is external to your organization; an internal user is created directly in your directory as a normal employee/user account.
• B2B invitation: The process of inviting external users so they can collaborate in your resources; New-AzureADMSInvitation is designed for this.

• Correct choices: A and D.

• Why not B, C, or E?

• Answer: S3 Inventory report.

• Why: The S3 Inventory report provides a scheduled listing of objects within a bucket, including metadata about each object. When you configure it to include object tagging, you can see tags for each object, and the object keys (which reflect prefixes) and bucket scope are captured in the report. This makes it suitable for auditing and tracking “tags, buckets, and prefixes” across S3 objects.

• What the other options do (not suitable for this purpose):

• Tip: If you need tags in the report, enable the inventory option to include object tagging in the configuration.

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.

• prompt: the input or instruction given to the model
• completion: the desired response

json 
{"prompt":"Summarize this customer complaint.","completion":"The customer reports a delayed shipment."}

• B: A .txt file containing CSV-style lines is not automatically a valid fine-tuning dataset. The required structure and format must match the selected Bedrock model.
• C: Provisioned Throughput provides dedicated inference capacity; it does not fine-tune a model.
• D: Journals and textbooks might support domain adaptation or pretraining, but they do not provide the prompt-to-answer examples typically required for supervised fine-tuning.

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

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.

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

• Each statement is evaluated as True (Yes) or False (No) independently.
• Key Azure facts to recall:

• The first step in risk management is to understand objectives, constraints, and drivers from those who care about the project. This stakeholder engagement helps identify what could go wrong and what risks are most critical.
• Only after you’ve gathered input from stakeholders should you identify risks and document them in the risk register. Updating the risk register (option C) is important, but it comes after identifying and analyzing risks.
• Options B (ensure resources) and D (revise the risk management plan) are actions that may follow once risks are identified and understood; they’re not the initial step.

• Mapping:

• Why:

• Quick note: If you were to host a website on a VM, it would be IaaS; if you used a platform service instead of a VM, it would be PaaS. CaaS (containers) isn’t shown here.

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

• Alice is co-resident on the same physical host and exploits shared hardware (the processor cache) to infer secrets. This is the classic definition of a side-channel attack—information leakage through implementation details (like timing or cache behavior) rather than by breaking a protocol or injecting code.

• Observing cache timing or access patterns to deduce cryptographic keys or plaintext data from the victim VM.

• Man-in-the-cloud attack: targets cloud trust/auth, not local hardware sharing.
• SQL injection: exploits input to run SQL commands, not a VM/caching vector.
• Service hijacking: takes control of a service, not about covert data leakage via shared hardware.

• Notice phrases like “shared hardware resources,” “co-resident,” or “cache”—these indicate a side-channel vector.

• The problem: Guest users can’t create posts in the Monthly Reports channel.
• The recommended fix (answer B): Modify the Guest access settings in the Teams admin center.

• Guest access settings control what guests are allowed to do across Teams (for example, posting, chat, and channel participation). If guests are restricted from posting, enabling the appropriate guest permissions will let them post in channels like Monthly Reports.
• The other options don’t directly change guest permissions in the way that affects posting:

• ProductSearchModel.getProductSearchHits() — option C
• ProductSearchHit.getRepresentedProducts() — option B

• ProductMgr.queryAllSiteProducts() (A) queries every product in the site, which is heavy and not scalable for large catalogs.
• Category.getProducts() (D) retrieves all products in a category; this can be slow for large categories.
• Using the search model and hits (B and C) leverages the search index, supports paging, and avoids scanning the entire catalog, making it more scalable.

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

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

• Correct answer: A. Inbound data transfer from the internet

• Why: AWS does not charge for data transferred into AWS from the internet. Inbound data transfer is free, regardless of the amount (in this case, 2 TB). The other options involve data leaving AWS or moving between AWS regions/AZs, which incur costs:

1. Define Power Platform DLP policies
2. Add custom prompt modifications
3. Conduct adversarial testing

1. DLP policies first

1. Prompt modifications second

1. Adversarial testing last

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

• Topic: Conditional Access (CA) policy and MFA for Azure management.
• Policy name: Policy1, created with the template “Require multifactor authentication for Azure management.”
• What the template does: It enforces MFA when signing in to manage Azure resources (Azure management) for the users included in the policy.
• Who is included: The question lists Admin1, Admin2, Admin3, and Admin4 as the admins in the tenant. The template’s default scope for this scenario is to apply to those admin accounts (i.e., all four admins unless you explicitly limit the scope).

• CA policy for “Azure management” targets admin sign-ins.
• If the policy includes Admin1–Admin4, all of them must use MFA on their next sign-in (choice D).

• Answer: No.

• Why:

• If you need such an assessment while controlling costs, you’d generally pursue a paid MCS engagement or another option outside of the basic Premier entitlement.

• Global Unicast: These are the IPv6 addresses that are globally routable on the Internet. They’re allocated by Regional Internet Registries (RIRs) and can be reached from anywhere with proper routing (similar to IPv4 public addresses). Example ranges include 2000::/3.

• Link-local: fe80::/10. Used only on the local link; not routable beyond the directly connected network.

• Unique Local Addresses (ULA): fc00::/7. Private addresses for internal use within an organization; not publicly routable on the Internet (like IPv4 private addresses).

• Multicast: ff00::/8. One-to-many addresses used for group communication, not unicast routing.

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

• MFA verifies a user’s identity using additional authentication factors, such as a phone prompt or security token.
• It helps prevent unauthorized access even if a password is compromised.
• It does not provide secure storage or encryption of credentials used during automated deployment.

• This is a lookup relationship. Salesforce does not cascade access from a child (Opportunity) to its parent (Account) via implicit sharing.
• To view the Account, the user must have explicit access to the Account (via its OWD/sharing, or object permissions).

• The user has Read/View (or higher) on Account via profile/permission set.
• Manual sharing or a sharing rule grants that Account to the user.
• The Account is exposed by a broader permission like View All/Modify All on Account.
• Role hierarchy with Grant Access Using Hierarchies could grant access to Accounts owned by others, if applicable.

• Increase/decrease the number of epochs: Changes how long training runs, but does not reuse a pre-trained model.
• Unsupervised learning: Trains from unlabeled data and does not specifically address adapting an existing model.

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

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

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

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

• Sustainability
• Performance efficiency
• Reliability

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

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